This is the mail archive of the
mailing list for the GCC project.
Re: Add Android related compilation options and multilib options
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: Chris Lattner <clattner at apple dot com>
- Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, Mark Mitchell <mark at codesourcery dot com>, Ian Lance Taylor <iant at google dot com>, Richard Guenther <richard dot guenther at gmail dot com>, Jing Yu <jingyu at google dot com>, gcc-patches at gcc dot gnu dot org, "Doug Kwan (???)" <dougkwan at google dot com>, nickc at redhat dot com, richard dot earnshaw at arm dot com, paul at codesourcery dot com
- Date: Thu, 18 Jun 2009 11:10:02 +0100
- Subject: Re: Add Android related compilation options and multilib options
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <4A380ABC.firstname.lastname@example.org> <B9ACF3EF-4C6A-47F8-A649-E9A585491872@apple.com> <4A381CE1.email@example.com> <Pine.LNX.firstname.lastname@example.org> <DA398CC8-3BCA-4381-A729-39E7E6047174@apple.com> <Pine.LNX.email@example.com> <75469222-8980-43DF-82B3-4DE99EE32EA8@apple.com>
Chris Lattner wrote:
> It's worth pointing out that LLVM does a bit of canonicalization of
> target triples internally to collapse actually identical triples into a
> canonical form (e.g. ix86-* -> i386-*).
It's worth pointing out that GCC generates very different code when
configured for i386-foo-bar as compared to when you configure it for
i686-foo-bar; those cpu types are not canonically the same, despite all
indicating the same backend.
> It sounds like there are many possible areas for improvement. In any
> case, I will butt out and let you guys figure out how to solve this
> issue with Android. I am very happy to admit that I have no idea how
> your toolchain should work.
I would just like to add that throughout this thread I have been unable to
read the word "-mandroid" without falling off my chair laughing. I think
that's a good reason for making it a command-line option :)