blocks|key|2511280|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2511281|您可以将输出重定向到如下文件：|ordered-list-item|2511282|2511283|转至工具compile+-S+file.go+>+file.s|2511284|2511285|您可以使用-N禁用优化：|2511286|2511287|go工具编译-S+-N+file.go|2511288|或者，您可以使用gccgo：|2511289|gccgo+-S+-O0+-masm=intel+test.go|code-block|syntax|javascript|2511290|这将生成test.s。您可以使用-O0/1/2/3来查看不同的优化。|2511291|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|X|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|Y|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|Z|7|@]|8|@]|9|$]]|$1|E|3|F|4|5|6|10|7|@]|8|@]|9|$]]|$1|G|3|-4|4|5|6|11|7|@]|8|@]|9|$]]|$1|H|3|I|4|C|6|12|7|@]|8|@]|9|$]]|$1|J|3|-4|4|5|6|13|7|@]|8|@]|9|$]]|$1|K|3|L|4|5|6|14|7|@]|8|@]|9|$]]|$1|M|3|N|4|5|6|15|7|@]|8|@]|9|$]]|$1|O|3|P|4|Q|6|16|7|@]|8|@]|9|$R|S]]|$1|T|3|U|4|5|6|17|7|@]|8|@]|9|$]]|$1|V|3|-4|4|5|6|18|7|@]|8|@]|9|$]]]|W|$]]

<ol>
<li>You can redirect the output to a file like this:
<pre><code> go tool compile -S file.go &gt; file.s
</code></pre>
</li>
<li>You can disable the optimization with -N:
<pre><code> go tool compile -S -N file.go
</code></pre>
</li>
</ol>
Alternatively, you can use gccgo:
<pre><code>gccgo -S -O0 -masm=intel test.go
</code></pre>
which will generate test.s. You can play with the -O0/1/2/3 to see the different optimizations.

blocks|key|2511309|text|我不推荐使用-S的输出，因为Go链接器可能会很大程度上改变写入目标代码的内容。它确实让你对正在发生的事情有了一些了解。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2511310|go汇编程序的输出也是相当不标准的。|2511311|当我想这样做的时候，我总是使用objdump，它会给你一个很好的标准汇编程序输出。|2511312|例如x86+/+amd64|2511313|objdump+-d+executable+>+disassembly|code-block|syntax|javascript|2511314|而对于ARM+(获得与Go使用的相同的寄存器名称)|2511315|objdump+-M+reg-names-raw+-d+executable+>+disassembly|2511316|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Objdump^0|6|2|0|0|F|7|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|16|8|@]|D|@$9|17|A|18|1|19]]|E|$]]|$1|J|3|K|5|6|7|1A|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|1B|8|@]|D|@]|E|$O|P]]|$1|Q|3|R|5|6|7|1C|8|@]|D|@]|E|$]]|$1|S|3|T|5|N|7|1D|8|@]|D|@]|E|$O|P]]|$1|U|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]]]

I don't recommend using the output of <code>-S</code> as the Go linker can change what gets written to the object code quite a lot. It does give you some idea as to what is going on.

The go assembler output is rather non-standard too.

When I want to do this I always use <a href="http://en.wikipedia.org/wiki/Objdump">objdump</a> which will give you a nice standard assembler output.

Eg for x86 / amd64

<pre><code>objdump -d executable &gt; disassembly
</code></pre>

And for ARM (to get the register names to be the same as Go uses)

<pre><code>objdump -M reg-names-raw -d executable &gt; disassembly
</code></pre>

blocks|key|2721693|text|对生成的可执行文件运行go+tool+objdump。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2721694|要将输出限制为感兴趣的函数，请使用其-s选项。|2721695|entityMap^0|B|F|0|I|2|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

Run <code>go tool objdump</code> on the resulting executable file.

To restrict the output to interesting functions, use its <code>-s</code> option.

blocks|key|2511525|text|要将输出转储到文件，请执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2511526|go+tool+objdump+EXECUTABLE_FILE+>+ASSEMBLY_FILE|code-block|syntax|javascript|2511527|如果您想包含Go源代码(假设您有一个有效的golang设置，并且您自己构建了可执行文件)：|2511528|go+tool+objdump+-S+EXECUTABLE_FILE|2511529|为了使输出更容易查看，我使用了一个small+hacky+wrapper，它产生以下内容(简而言之，它对指令进行着色，改变跳转的控制流-blue，绿色表示调用/返回，红色表示陷阱，紫色表示填充-并在无条件控制流跳转后添加新行)：|offset|length|2511530|​|2511531|📷|atomic|2511532|2511533|如果您使用上面的包装器，您可能希望在通过管道连接到less时使用-R开关(或者通过将其添加到环境中，例如在.bashrc：export+LESS="$LESS+-R"中)：|style|CODE|2511534|go-objdump+EXECUTABLE_FILE+%7C+less+-R|2511535|或者，有一种godbolt.org可能具有最易读的输出，允许您在编译器(gc、gccgo)和版本之间非常容易地进行切换。|2511536|entityMap|0|LINK|mutability|MUTABLE|url|https://gist.github.com/CAFxX/332b425634f12ccbb7a1eef074da19bf|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/7e0f11723f978fd0cea2d23a49324b03.png|imageAlt|2|https://godbolt.org/^0|0|0|0|0|H|J|0|0|0|0|1|1|0|0|P|4|W|2|1H|7|1P|M|0|0|6|B|2|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1J|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1K|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|1L|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|1M|8|@]|9|@$M|1N|N|1O|1|1P]]|A|$]]|$1|O|3|P|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1R|8|@]|9|@$M|1S|N|1T|1|1U]]|A|$]]|$1|T|3|P|5|6|7|1V|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1W|8|@$M|1X|N|1Y|W|X]|$M|1Z|N|20|W|X]|$M|21|N|22|W|X]|$M|23|N|24|W|X]]|9|@]|A|$]]|$1|Y|3|Z|5|D|7|25|8|@]|9|@]|A|$E|F]]|$1|10|3|11|5|6|7|26|8|@]|9|@$M|27|N|28|1|29]]|A|$]]|$1|12|3|-4|5|6|7|2A|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]|1A|$5|1B|16|1C|A|$1D|1E|1F|-4]]|1G|$5|15|16|17|A|$18|1H]]]]

To dump the output to file:

<pre><code>go tool objdump EXECUTABLE_FILE &gt; ASSEMBLY_FILE
</code></pre>

If you want to include the source Go code (assuming you have a working golang setup, and you built the executable yourself):

<pre><code>go tool objdump -S EXECUTABLE_FILE
</code></pre>

To make the output even easier to look at I use a <a href="https://gist.github.com/CAFxX/332b425634f12ccbb7a1eef074da19bf" rel="noreferrer">small hacky wrapper</a> that produces the following (in a nutshell, it colorizes instructions that alter the control flow -blue for jumps, green for call/return, red for traps, violet for padding- and adds new lines after unconditional control flow jumps):

<a href="https://i.stack.imgur.com/iwXU0.png" rel="noreferrer"><img src="https://i.stack.imgur.com/iwXU0.png" alt="example output of go-objdump wrapper"></a>

If you use the wrapper above you will likely want to use the <code>-R</code> switch when piping to <code>less</code> (or by adding it to the environment, e.g. in <code>.bashrc</code>: <code>export LESS="$LESS -R"</code>):

<pre><code>go-objdump EXECUTABLE_FILE | less -R
</code></pre>

Alternatively, there is <a href="https://godbolt.org/" rel="noreferrer">godbolt.org</a> that has probably the most readable output and allows you to switch between compilers (gc, gccgo) and versions very easily.

blocks|key|40833|text|我对其他答案有问题，因为程序集提供的信息比我想要的要多得多，但仍然没有足够的细节。让我解释一下:它为go内部导入的所有库提供了程序集，并且没有提供代码所在的行(我的代码都在文件的底部)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|40834|以下是我从官方文档中发现的：|40835|$+GOOS=linux+GOARCH=amd64+go+tool+compile+-S+x.go++++++++#+or:+go+build+-gcflags+-S+x.go|offset|length|style|CODE|40836|文件：|40837|package+main

func+main()+{
++++println(3)
}|code-block|syntax|javascript|40838|产生：|40839|---+prog+list+"main"+---
0000+(x.go:3)+TEXT++++main%2B0(SB),$8-0
0001+(x.go:3)+FUNCDATA+$0,gcargs·0%2B0(SB)
0002+(x.go:3)+FUNCDATA+$1,gclocals·0%2B0(SB)
0003+(x.go:4)+MOVQ++++$3,(SP)
0004+(x.go:4)+PCDATA++$0,$8
0005+(x.go:4)+CALL++++,runtime.printint%2B0(SB)
0006+(x.go:4)+PCDATA++$0,$-1
0007+(x.go:4)+PCDATA++$0,$0
0008+(x.go:4)+CALL++++,runtime.printnl%2B0(SB)
0009+(x.go:4)+PCDATA++$0,$-1
0010+(x.go:5)+RET+++++,|40840|所以我所做的基本上是：|40841|go+tool+compile+-S+hello.go+>+hello.s|40842|它得到了我想要的结果！|40843|entityMap^0|0|0|0|2G|0|0|0|0|0|0|0|11|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|14|8|@$F|15|G|16|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|18|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|T|5|N|7|1A|8|@]|9|@]|A|$O|P]]|$1|U|3|V|5|6|7|1B|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1C|8|@$F|1D|G|1E|H|I]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1F|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|11|$]]

I had problems with the other answers as the assembly produced provided much more information than I wanted and still not enough details. Let me explain: it provided the assembly for all libraries imported by go internally and did not provide the lines of where my code was (my code was all at the bottom of the file)

Here is what I found from the official docs:

<code>$ GOOS=linux GOARCH=amd64 go tool compile -S x.go # or: go build -gcflags -S x.go</code>

File:

<pre><code>package main

func main() {
 println(3)
}
</code></pre>

Produces:

<pre><code>--- prog list "main" ---
0000 (x.go:3) TEXT main+0(SB),$8-0
0001 (x.go:3) FUNCDATA $0,gcargs·0+0(SB)
0002 (x.go:3) FUNCDATA $1,gclocals·0+0(SB)
0003 (x.go:4) MOVQ $3,(SP)
0004 (x.go:4) PCDATA $0,$8
0005 (x.go:4) CALL ,runtime.printint+0(SB)
0006 (x.go:4) PCDATA $0,$-1
0007 (x.go:4) PCDATA $0,$0
0008 (x.go:4) CALL ,runtime.printnl+0(SB)
0009 (x.go:4) PCDATA $0,$-1
0010 (x.go:5) RET ,
</code></pre>

So what I did was basically:

<code>go tool compile -S hello.go &gt; hello.s</code>

and it got the result I wanted!

blocks|key|40932|text|我发现对于使用XCode开发工具的Mac用户来说，最简单的方法就是使用otool。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|40933|$+otool+-tV+<executable>|code-block|syntax|javascript|40934|Source|40935|entityMap|0|LINK|mutability|MUTABLE|url|https://superuser.com/a/206552^0|Z|5|0|0|0|6|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

The easiest way i found around for Mac users with XCode dev tools is with <code>otool</code>
<pre><code>$ otool -tV &lt;executable&gt;
</code></pre>
<a href="https://superuser.com/a/206552">Source</a>

I'm interested in examining the x86 assembly output of the standard Go compiler to see if my code is really being converted into reasonably efficient assembly code; hopefully, by profiling and examining the assembly output, I could get a clue as to where/how I should rewrite my Go code for maximum performance. But when I examine the code using the -S flag, Go spits out a mess! I'd like two things:

<ol>
<li>Is there a way to make the Go compiler dump the assembly output into a file, not just print it out on Terminal?</li>
<li>Also, is there a way to make the Go compiler separate out the assembly code into separate functions, with labels? I know some functions may be inlined and hence not appear in the assembly code. What I'm seeing know is just a homogenous blob of assembly which is almost impossible to understand. </li>
</ol>

Easy to read Golang assembly output?

编译器

我对检查标准Go编译器的x86汇编输出很感兴趣，以查看我的代码是否真的被转换为相当有效的汇编代码；希望通过分析和检查汇编输出，我可以获得关于我应该在哪里/如何重写Go代码以获得最大性能的线索。但是当我使用-S标志检查代码时，Go显示出一片混乱！我想要两样东西：有没有办法让Go编译器把汇编输出转储到一个文件中，而不仅仅是在Terminal?Also，上打印出来?有没有办法让Go编译器把汇编代码分成带

问容易阅读Golang汇编输出？
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问容易阅读Golang汇编输出？EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问容易阅读Golang汇编输出？
EN