From: "Ollie Wild" <aaw@google.com>
To: "Mark Mitchell" <mark@codesourcery.com>
Cc: "Ian Lance Taylor" <iant@google.com>,
gnu@the-meissners.org, wilson@specifixinc.com,
tromey@redhat.com, gcc-patches@gcc.gnu.org
Subject: Re: PATCH PING: distcc and ccache speedup: adds directives-only preprocessing
Date: Thu, 26 Jul 2007 22:10:00 -0000 [thread overview]
Message-ID: <65dd6fd50707261433m1889e854web6ae02db161edf@mail.gmail.com> (raw)
In-Reply-To: <46A80DEE.9060908@codesourcery.com>
Thanks for championing this, Ian. It'll be good to finally get it in.
On 7/25/07, Mark Mitchell <mark@codesourcery.com> wrote:
> This patch is OK, with one caveat: I think the documentation could be
> better.
Agreed. The documentation below is (hopefully) more readable. Take a
look, and if everyone approves, I'll go ahead and submit the modified
patch.
Ollie
@item -fdirectives-only
@opindex fdirectives-only
This option provides a simplified preprocessor that improves the
performance of applications such as ccache and distcc. In both these cases,
usage is straightforward:
@smallexample
distcc /usr/bin/gcc -fdirectives-only [COMPILER OPTIONS]
@end smallexample
The option's behavior depends on the @option{-E} and @option{-fpreprocessed}
options.
With @option{-E}, preprocessing is limited to the handling of directives
such as @code{#define}, @code{#ifdef}, and @code{#error}. Other
preprocessor operations, such as macro expansion and trigraph
conversion are not performed. In addition, the @option{-dD} option is
implicitly enabled.
With @option{-fpreprocessed}, predefinition of command line and most
builtin macros is disabled. Macros such as @code{__LINE__}, which are
contextually dependent, are handled normally. This enables compilation of
files previously preprocessed with @code{-E -fdirectives-only}.
With both @option{-E} and @option{-fpreprocessed}, the rules for
@option{-fpreprocessed} take precedence. This enables full preprocessing of
files previously preprocessed with @code{-E -fdirectives-only}.
next prev parent reply other threads:[~2007-07-26 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 16:10 Ian Lance Taylor
2007-07-25 16:27 ` Andreas Schwab
2007-07-26 7:16 ` Mark Mitchell
2007-07-26 10:51 ` Dave Korn
2007-07-26 19:37 ` Ian Lance Taylor
2007-07-26 22:10 ` Ollie Wild [this message]
2007-07-29 19:29 ` Mark Mitchell
2007-07-30 18:53 ` Ollie Wild
2007-07-27 23:17 ` Michael Meissner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=65dd6fd50707261433m1889e854web6ae02db161edf@mail.gmail.com \
--to=aaw@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu@the-meissners.org \
--cc=iant@google.com \
--cc=mark@codesourcery.com \
--cc=tromey@redhat.com \
--cc=wilson@specifixinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).