This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/71216] [4.9/5/6/7 Regression] Incorrect PPC assembly due to inserted .machine pseudo-op
- From: "segher at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 22 Dec 2016 19:15:28 +0000
- Subject: [Bug target/71216] [4.9/5/6/7 Regression] Incorrect PPC assembly due to inserted .machine pseudo-op
- Auto-submitted: auto-generated
- References: <bug-71216-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71216
--- Comment #10 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Rin Okuyama from comment #9)
> > > However, I have a question on this fix. How about the case where
> > > "-Wa,-mXXX" option is given without "-mcpu=YYY" option specified?
> >
> > That might or might not work; the user had better know what he is
> > doing if he uses an assembler option.
>
> Hmm, I understand. Is this documented explicitly anywhere?
Not in so many words I think, no.
> > GCC does not support -me500, right. You need to configure your compiler
> > for a powerpc-*-eabispe* target as far as I know (I'm no expert on this).
>
> We use -Wa,-me500 option to compile kernel on some machines. As they
> share userland with other machines, we cannot configure GCC for a
> powerpc-*-eabispe* target. Instead, I found a workaround to specify
> -mcpu=powerpc option. It passes -mppc option to assembler, but as it
> is preceding to -me500, the latter is prior to the former.
Maybe you could use -mcpu=e500mc or similar? Or, GCC should probably
have a -mcpu=e500 option, but someone has to write the code for it.