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 18:20:53 +0000 (GMT)
- Subject: Re: iWMMXt/Linux EABI toolchain
--- Daniel Jacobowitz <email@example.com> wrote:
> On Wed, Mar 01, 2006 at 05:43:53PM +0000, Steven Newbury wrote:
> > My reason for using the xscale-* triplets was because of the warning below
> > gcc/config/arm/t-xscale-elf:
> > # 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
> > 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
> > non iWMMXt targets. Perhaps I'd be better off using iwmmxt-*?
> The comment does not apply to an EABI toolchain, which you are
> building. And comments about multilibs don't apply to anything
> using --with-cpu; if you're doing that you ought to be using
> --disable-multilib anyway.
OK, thank-you. I'll target "arm-iwmmxt-linux-gnueabi" with --with-cpu= etc and
--disable-multilib. The vendor string is for my build scripts and also will
help differentiate the toolchain, is that valid?
To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com