This is the mail archive of the
mailing list for the GCC project.
Re: iWMMXt/Linux EABI toolchain
- From: Steven Newbury <s_j_newbury at yahoo dot co dot uk>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 1 Mar 2006 17:43:53 +0000 (GMT)
- Subject: Re: iWMMXt/Linux EABI toolchain
--- Daniel Jacobowitz <email@example.com> wrote:
> On Wed, Mar 01, 2006 at 05:15:07AM +0000, Steven Newbury wrote:
> > I have managed to build with arm-iwmmxt-linux-gnu, where iwmmxt as the
> > string is picked up by my ebuild scripts to pass the iwmmxt target flags.
> > Given my objective, am I wrong to try to make a tool chain that targets
> > xscale-iwmmxt-linux-gnueabi specifically or do you just consider it
> > effort?
> I don't think there's any point to the xscale-* triplets nowadays.
My reason for using the xscale-* triplets was because of the warning below from
# The iWMMXt multilibs are suppressed for now because gcc only
# supports generating them with the IWMMXT or AAPCS ABIs, neither of
# which is the default. Until GCC can generate code for an iWMMXt
# which will work with the default ABI it is not possible to safely
# generate these multilibs.
Since I'm not going to be using the default ABI I thought I would be better off
adding a specific target since my aim is to produce a complete Linux
environment for general use rather than a stand-alone project. That way I
could enable the iWMMXt multilibs without worrying about incompatibility with
non iWMMXt targets. Perhaps I'd be better off using iwmmxt-*?
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com