public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Ollie Wild <aaw@google.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: Sun, 29 Jul 2007 19:29:00 -0000	[thread overview]
Message-ID: <46ACE2AD.9060507@codesourcery.com> (raw)
In-Reply-To: <65dd6fd50707261433m1889e854web6ae02db161edf@mail.gmail.com>

Ollie Wild wrote:

> 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

I would replace all of what's quoted above with:

  When preprocessing, handle directives, but do not expand macros.

I don't think the distcc and/or ccache references are appropriate here.
 (The manuals for those tools could be updated to reference this option,
of course.)  If we're going to say more in the GCC manual, it should be
more motivational, like:

  If you need to determine whether two files will be the same after
preprocessing, you can use this option to generate preprocessed source
for comparison.  If the two files are identical after being preprocessed
with @option{-fdirectives-only}, they will also be the same after full
preprocessing.  This option is substantially faster that full preprocessing.

Feel free to add that, if you like.

The patch is OK with those changes.

Thanks,

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713

  reply	other threads:[~2007-07-29 18:55 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
2007-07-29 19:29     ` Mark Mitchell [this message]
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=46ACE2AD.9060507@codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=aaw@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gnu@the-meissners.org \
    --cc=iant@google.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).