This is the mail archive of the gcc-patches@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]

Re: Selecting the correct default ABI for the iWMMXt processor

From: Nick Clifton <nickc at redhat dot com>
To: "Richard Earnshaw (Lists)" <Richard dot Earnshaw at arm dot com>
Cc: Ian Lance Taylor <ian at wasabisystems dot com>, gcc-patches at gcc dot gnu dot org
Date: Fri, 16 Apr 2004 15:50:07 +0100
Subject: Re: Selecting the correct default ABI for the iWMMXt processor
References: <407D7459.9050308@redhat.com> <m34qrmjq57.fsf@gossamer.airs.com> <407FB9BC.1000006@redhat.com> <1082113431.5664.14.camel@pc960.cambridge.arm.com> <407FC199.6090808@redhat.com> <1082122210.5664.31.camel@pc960.cambridge.arm.com>

Hi Richard,

I see - very well I shall revert my patch and fix the XScale makefile fragments so that they do not attempt to build iWMMXt multlibs. Once we have the ABI support problem resolved they can be re-enabled.

You could add a -mabi=iwmmxt and -mcpu=iwmmxt multilib variants and then add ignores for the variants that aren't legal.

Which would be almost all of them :-) OK - I will give it a go.

Cheers
 Nick

References:
- Selecting the correct default ABI for the iWMMXt processor
  - From: Nick Clifton
- Re: Selecting the correct default ABI for the iWMMXt processor
  - From: Ian Lance Taylor
- Re: Selecting the correct default ABI for the iWMMXt processor
  - From: Nick Clifton
- Re: Selecting the correct default ABI for the iWMMXt processor
  - From: Richard Earnshaw (Lists)
- Re: Selecting the correct default ABI for the iWMMXt processor
  - From: Nick Clifton
- Re: Selecting the correct default ABI for the iWMMXt processor
  - From: Richard Earnshaw (Lists)

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]