public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Ian Lance Taylor <iant@google.com>
Cc: gnu@the-meissners.org, wilson@specifixinc.com,
		mark@codesourcery.com, aaw@google.com, tromey@redhat.com,
		gcc-patches@gcc.gnu.org
Subject: Re: PATCH PING: distcc and ccache speedup: adds directives-only preprocessing
Date: Wed, 25 Jul 2007 16:27:00 -0000	[thread overview]
Message-ID: <jesl7c4fzo.fsf@sykes.suse.de> (raw)
In-Reply-To: <m3myxkfp6x.fsf@localhost.localdomain> (Ian Lance Taylor's 	message of "25 Jul 2007 09\:00\:54 -0700")

Ian Lance Taylor <iant@google.com> writes:

> diff --git a/gcc/doc/cppopts.texi b/gcc/doc/cppopts.texi
> index 17235bd..14187b6 100644
> --- a/gcc/doc/cppopts.texi
> +++ b/gcc/doc/cppopts.texi
> @@ -518,6 +518,22 @@ Search @var{dir} only for header files requested with
>  If @var{dir} begins with @code{=}, then the @code{=} will be replaced
>  by the sysroot prefix; see @option{--sysroot} and @option{-isysroot}.
>  
> +@item -fdirectives-only
> +@opindex fdirectives-only
> +This option provides a simplified preprocessor to improve the
> +performance of distributed build systems such as distcc.  It's
> +behavior depends on a number of other flags.

s/It's/Its/

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2007-07-25 16:15 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 [this message]
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
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=jesl7c4fzo.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=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).