GAS: Handling option parsing for ARM co-processor extensions

[Phil Blundell]

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.