Thanks, I have already replied - would of saved you the typing trouble. As I
pointed out, the lack of register prefixes (which would screen AT&T at me), was
what really confused me.
> On Dec 14, 2018, at 4:09 PM, Ian Denhardt wrote:
>
> If you pass `-M intel` to objdump it will display intel s
The tools all emit AT&T/amd syntax by default and you can use -M intel to get
the intel format.
The confusing thing is that they don’t use the ‘register prefixes’, so it looks
like intel but it is backwards.
Oh well.
> On Dec 14, 2018, at 3:41 PM, robert engels wrote:
>
> In the go assembly
If you pass `-M intel` to objdump it will display intel syntax.
Quoting robert engels (2018-12-14 16:41:39)
>but the operands are backwards according to MOVQ on Intel, it
>should be
>dst,src
>SO, I'm thinking "intermediate code", so different syntax. Fine, but
>then when I use
In the go assembly docs, for example:
64-bit Intel 386 (a.k.a. amd64)
The two architectures behave largely the same at the assembler level. Assembly
code to access the m and gpointers on the 64-bit version is the same as on the
32-bit 386, except it uses MOVQ rather than MOVL:
get_tls(CX)
MOVQ
