https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122275
--- Comment #7 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to LIU Hao from comment #6) > (In reply to H.J. Lu from comment #5) > > How do I reproduce it? > > Actually I changed the default value of `-masm=`: > > ``` > diff --git a/gcc/config/i386/i386.opt b/gcc/config/i386/i386.opt > index 401acb201078..68400ab1be9d 100644 > --- a/gcc/config/i386/i386.opt > +++ b/gcc/config/i386/i386.opt > @@ -263,7 +263,7 @@ Target RejectNegative Negative(march=) Joined > Var(ix86_arch_string) > Generate code for given CPU. > > masm= > -Target RejectNegative Joined Enum(asm_dialect) Var(ix86_asm_dialect) > Init(ASM_ATT) > +Target RejectNegative Joined Enum(asm_dialect) Var(ix86_asm_dialect) > Init(ASM_INTEL) > Use given assembler dialect. > > Enum > > ``` > > Then this can be reproduced on i686-w64-mingw32, which I suspect is the only > affected target. How does the modified GCC work with https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53929 > (a few months ago I tried building GCC on x86_64-linux-gnu, but some headers > contain asm stmts that have no alternative templates for Intel syntax, so > building GCC turned out to be impractical out there.) So building GCC with -masm=intel doesn't work even if this bug is fixed.
