4 ms·
No, it is not an IR code such as in Java or .Net. At compile time it is translated into opcodes for the corresponding architecture that you are compiling for.
by fwessels 9y ago
No, it is not an IR code such as in Java or .Net.
At compile time it is translated into opcodes for the corresponding architecture that you are compiling for.
- chrisseaton 9y agoI disagree. I think saying that it's the lowered intermediate representation in the Go compiler pipeline is a really good description. It's equivalent to the LIR in Java's C2 compiler. I'm not sure what the equivalent is in .net. Fundamentally, it's a representation and it's intermediate isn't it?
- uluyol 9y agoNo, not really. Go's assembly might be considered somewhat higher level than regular assembly code, but it's certainly architecture specific. The examples highlighted use x86 SIMD instructions unavailable on other architectures. Freedoms taken by the go assemblers also seem to be decreasing as the compiler becomes smarter. E.g. instruction reordering is no longer performed (https://github.com/golang/go/issues/15837 https://github.com/golang/go/issues/15837). You can read about the assemblers here: https://golang.org/doc/asm https://golang.org/doc/asm
- chrisseaton 9y agoYes I know it's architecture specific. Many lowered IRs are. The equivalent I gave, Java's C2 IR, is also architecture specific, which is why I used it.