This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 02/14/2012 06:51 PM, Ian Lance Taylor wrote:[...]Sebastian Huber<sebastian.huber@embedded-brains.de> writes:
On 02/14/2012 04:05 PM, Ian Lance Taylor wrote:Sebastian Huber<sebastian.huber@embedded-brains.de> writes:
That's what Sebastian is trying to do.I would recommend that RTEMS change to the ARM EABI if possible. That is the current standard ABI on ARM platforms.
It's true that the ARM EABI is different from the previous ABIs in some respect. I believe that would mean using ARM_ABI_AAPCS.
However, if you want to retain GNU/Linux compatibility, then using ARM_ABI_AAPCS_LINUX is likely to be correct.So you would recommend RTEMS to throw away ARM_ABI_AAPCS and to use ARM_ABI_AAPCS_LINUX, which as far as I see is a Linux-specific/proprietaty deviation from EABI?
To me, this seems "hacking" - I am actually leaning towards considering the issues Sebastian mentions to be portability bugs in the non-GCC components he faces this issue with.
But I am not an ARM expert.Neither am I.
-- Sebastian Huber, embedded brains GmbH
Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany Phone : +49 89 18 90 80 79-6 Fax : +49 89 18 90 80 79-9 E-Mail : sebastian.huber@embedded-brains.de PGP : Public key available on request.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |