This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/5372] [powerpc-*-eabi] -mno-eabi not working
- From: "msebor at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 27 Jan 2016 18:06:21 +0000
- Subject: [Bug target/5372] [powerpc-*-eabi] -mno-eabi not working
- Auto-submitted: auto-generated
- References: <bug-5372-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=5372
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2004-01-02 06:15:10 |2016-1-27
CC| |msebor at gcc dot gnu.org
Known to fail| |3.0.3, 4.8.3, 4.9.3, 5.3.0,
| |6.0
--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> ---
Reconfirmed with 6.0. The manual says:
Selecting -mno-eabi means that the stack is aligned to a 16-byte boundary, no
EABI initialization function is called from main, and the -msdata option only
uses r13 to point to a single small data area.
The following test case shows that a call to __eabi is emitted despite the
-mno-eabi option:
$ echo "int main (void) { return 0; }" |
/build/sysroot/powerpc-eabispe/bin/powerpc-eabispe-gcc -c -mno-eabi -nostdlib
-o a.o -xc - && objdump -t a.o | grep '*UND\*'
00000000 *UND* 00000000 __eabi
I don't know enough about the EABI to tell for sure whether the problem is in
the manual or if GCC is wrong for calling __eabi even with the option.