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: Neil Booth <neil at daikokuya dot co dot uk>
To: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
Cc: 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 12:00:59 +0900
Subject: Re: How is lang.opt processed?
References: <20050306024542.GA97148@troutmask.apl.washington.edu> <4230B7D9.4010901@specifixinc.com> <18783164.1110566386214.JavaMail.root@dtm1eusosrv72.dtm.ops.eu.uu.net> <4231F1AE.7030206@moene.indiv.nluug.nl> <20050312020422.GO897@duron.akihabara.co.uk> <20050312023955.GA78078@troutmask.apl.washington.edu>

Steve Kargl wrote:-

> Yeah, tell us something we did not know!  The problem, until
> Jim explained option handling, is *why* these were not passed
> to gfortran.  Finding the info is/was non-obvious.  What is
> even more appalling is that there is no way to inhibit the
> swallowing of the options.

Ah, OK.  I assumed that since you referred to lang.opt (the title
of this whole thread) you were looking in the front ends.  The
driver and lang.opt are completely separate; the driver runs in
the fabulous world of specs, which as you've noticed suck.  They're
reasonably well documented in gcc.c though.  Changing how they work
will give you more than a headache.

Neil.

References:
- How is lang.opt processed?
  - From: Steve Kargl
- Re: How is lang.opt processed?
  - From: James E Wilson
- Re: How is lang.opt processed?
  - From: Toon Moene
- Re: How is lang.opt processed?
  - From: Neil Booth
- 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]