This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PCH] driver, documentation
- From: Stan Shebs <shebs at apple dot com>
- To: Mike Stump <mrs at apple dot com>
- Cc: Geoffrey Keating <geoffk at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Date: Mon, 19 Aug 2002 10:58:58 -0700
- Subject: Re: [PCH] driver, documentation
- References: <FEF7DCAA-B398-11D6-943C-000393941EE6@apple.com>
Mike Stump wrote:
I was wondering about flags like -fvolatile, -O2, -O0, -g and
-ffast-math? -UMACRO? Do they rule out pch? Should they?
I am thinking about C++ where it is possible to have significant
portions of code for an application in header files.
Ideally, you'd keep around tree rather than RTL, so most backend flags
shouldn't matter. The most problematic backend flags are the ones that
define cpp macros, so that would include -On because of __OPTIMIZE__
(I think we get this one wrong now). It would be useful to have some
way of knowing or indicating flags that don't affect a precomp, because
it's too restrictive otherwise - consider a -Wxxx passed only to some
files in a project.
Stan