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: Richard Earnshaw <rearnsha at arm dot com>
- To: Lars Brinkhoff <lars dot spam at nocrew dot org>
- Cc: Richard dot Earnshaw at arm dot com, binutils at sources dot redhat dot com
- Date: Tue, 15 Jan 2002 11:48:10 +0000
- Subject: Re: GAS: Handling option parsing for ARM co-processor extensions
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> Richard Earnshaw <rearnsha@arm.com> writes:
> > I've been thinking a bit about how we should handle the option parsing for
> > various ARM co-processor extensions. Currently we have the highly bogus
> > situation where -marm9e is used to mean "add the Cirrus Maverick
> > instructions": it's bogus because arm9e is a real cpu variant from ARM.
> >
> > One way I can think of doing this is to allow syntax along the following
> > lines
> >
> > -marmX+ext1+...
>
> Why not
>
> -marmX -mext1
>
> or similar? This is the approach I've used for PDP-11:
>
> http://pdp11.nocrew.org/binutils/as-opt.html
>
I'd thought about that, but it is harder to specify what is supposed to
work with what. Plus you have to read all the options before you can work
out if you have a valid specification. The syntax I proposed keeps all
the variant information together in one flag.
R.