This is the mail archive of the gcc@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: How is lang.opt processed?

From: Mike Stump <mrs at apple dot com>
To: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
Cc: Neil Booth <neil at daikokuya dot co dot uk>, Toon Moene <toon at moene dot indiv dot nluug dot nl>, James E Wilson <wilson at specifixinc dot com>, gcc at gcc dot gnu dot org
Date: Sat, 12 Mar 2005 10:08:18 -0800
Subject: Re: How is lang.opt processed?

On Friday, March 11, 2005, at 06:39 PM, Steve Kargl wrote:

What is even more appalling is that there is no way to inhibit the
swallowing of the options.

Sure there is, it is just a matter of code. Check out --classpath and option_map for example in gcc.c. Sure seems like it isn't harder than adding one line per option. Would be even better if these were done by a lang fragment that then combined to form this table, but, you get the idea.

Follow-Ups:
- Re: How is lang.opt processed?
  - From: Steve Kargl

References:
- Re: How is lang.opt processed?
  - From: Steve Kargl

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