This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug inline-asm/51863] invlpg with -masm=intel generates memory operand size error in assembly stage
- From: "pinskia at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 15 Jan 2012 10:08:04 +0000
- Subject: [Bug inline-asm/51863] invlpg with -masm=intel generates memory operand size error in assembly stage
- Auto-submitted: auto-generated
- References: <bug-51863-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51863
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-01-15 10:08:04 UTC ---
(In reply to comment #3)
> > What GCC is doing is correct in that it outputs the byte/word/dword
> > correctly for -masm=intel.
> But why for -masm=intel and not for -masm=att (the default)?
Because that is how the constraint works. In intel style, size prefix is part
of the memory and not the instruction. That is mov with the size being in the
operand vs mov[lwqb] which says the size.