This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: GAS: Handling option parsing for ARM co-processor extensions
- From: Phil Blundell <pb at nexus dot co dot uk>
- To: Richard dot Earnshaw at arm dot com
- Cc: binutils at sources dot redhat dot com
- Date: 15 Jan 2002 12:25:23 +0000
- Subject: Re: GAS: Handling option parsing for ARM co-processor extensions
- References: <200201151212.MAA14894@cam-mail2.cambridge.arm.com>
On Tue, 2002-01-15 at 12:12, Richard Earnshaw wrote:
> Well, not really, since AFAICT from the Cirrus web pages, Maverick is just
> a co-processor extension on a CPU. There's nothing much to tie it to a
> particular processor, so using -mmaverick to imply a particular CPU looses
> flexibility.
Um, yeah, I didn't make that very clear. I meant that you would end up
with "-marmv4 -mmaverick" or something like that, along the lines of the
"-marmv3 -mfpa10" that we have now. XScale was a dumb thing to pick as
an example.
> Incidentally, I'm a bit concerned about -mxscale as a processor. From the
> documents I've read XScale seems to be more of a specification for an
> architecture than a single implementation.
Yes, I think that's right. I'm not sure that the distinction is
particularly important right now, though.
p.