From: "Michael Meissner" <michael.meissner@amd.com>
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, christophe.harle@amd.com
Subject: Re: PATCH PING: distcc and ccache speedup: adds directives-only preprocessing
Date: Fri, 27 Jul 2007 23:17:00 -0000 [thread overview]
Message-ID: <20070727223412.GA19661@mmeissner-gold.amd.com> (raw)
In-Reply-To: <m3myxkfp6x.fsf@localhost.localdomain>
On Wed, Jul 25, 2007 at 09:00:54AM -0700, Ian Lance Taylor wrote:
> This is the patch to speed up the preprocessor that I mentioned at the
> summit. I've reviewed the patch a few times now, and it looks good to
> me. It has been in active use at Google for every compilation for
> about six months with no problems.
>
> I would approve the patch if I could, but, unfortunately, since it
> adds a new option and a new way of reading files, it is probably
> non-algorithmic. That means that I can't approve it, nor can Tom. We
> need an approval from a global write maintainer, or from a C or C++
> front-end maintainer.
>
> Can somebody take a look? Thanks.
>
> Ian
Sorry this got routed to my old email that mostly gathers spam, and I didn't
notice it at first. Some comments:
1) On line 123 of directives-c.c in function _cpp_handle_directive, there is a
'\' at the end of a line, but since it isn't inside of a macro, you really
don't need it.
2) In line 179 of c-ppoutput.c in function print_lines_directives_only, I
noticed there is a fwrite without checking to see if it succeeded or not.
However, since scan_translation_unit_trad also does this, so it isn't any
different from the current code.
3) I'm not up on the .texi style guidelines, but you might want to quote distcc
with something like @samp{distcc}.
Other that, it looks good.
--
Michael Meissner, AMD
90 Central Street, MS 83-29, Boxborough, MA, 01719, USA
michael.meissner@amd.com
prev parent reply other threads:[~2007-07-27 22:34 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
2007-07-30 18:53 ` Ollie Wild
2007-07-27 23:17 ` Michael Meissner [this message]
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=20070727223412.GA19661@mmeissner-gold.amd.com \
--to=michael.meissner@amd.com \
--cc=aaw@google.com \
--cc=christophe.harle@amd.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).