<p>I recently posted a question on stack overflow, but haven't gotten an answer.</p>
<p>The question is, given a simple Go program like this:</p>
<pre><code>package main
func add(a, b int) int {
return a + b
}
func main () {
add(1,2)
}
</code></pre>
<p>How would I translate it to assembly using the command line tools?</p>
<p>So far, I found two possible commands. Namely:</p>
<pre><code>go tool compile -S file.go > file.S
</code></pre>
<p>And</p>
<pre><code>go tool objdump executable > disassembly
</code></pre>
<p>But both of them produce different outputs so I'm not sure If I'm doing this right.</p>
<p>Is there a better way to do this?</p>
<p>EDIT:</p>
<p>I found this command on the Go website which prints out assembly when compiling (for the same architecture):</p>
<pre><code>go build -gcflags -S file.go
</code></pre>
<p>This seems to do the trick.</p>
<hr/>**评论：**<br/><br/>Shepsauce: <pre><p>My understanding of why the outputs are different would be:
1. The compile -S will show you the assembly of that particular file all by itself.
2. The objdump tool shows references to the line numbers of the original code for what is executing.
3. You have to create an object file for objdump to work on, and that has everything you've imported linked into the file, so the total assembly should be longer.</p></pre>Ptcdln: <pre><p>Thanks, it does seem like using the <code>objdump</code> command on an executable prints out everything that was compiled. Including the built-in functions and libraries used.</p></pre>
