This is the mail archive of the
mailing list for the GCC project.
Re: Add Android related compilation options and multilib options
Chris Lattner wrote:
> That said, if it were my choice, I'd strongly prefer making android it's
> own target triple. If you want to make GCC more dynamic, make it work
> with multiple target triples first.
I disagree. Working with multiple target triplets is a fine thing, but
not inventing triplets you don't need is another. The idea that the
compiler has to know what the target RTOS is, rather than just the
target CPU, is largely unique to GCC -- and this is not a feature. (I
distinguish between an RTOS and GNU/Linux, purposefully; it's much
harder to build a compiler that works with both FreeRTOS and GNU/Linux
than one which works with all of FreeRTOS and ThreadX, say.)
AFAICT, Android is ARM EABI, with some of the defaults changed. If so,
it doesn't need a different triplet any more than a ARM compiler that
defaults to ARMv5T rather than ARMv6 does.
(650) 331-3385 x713