From: "Zack Weinberg" <zackw@Stanford.EDU>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: gcc@gcc.gnu.org
Subject: Re: Precompiled headers (or other speed ups)
Date: Wed, 10 Jan 2001 15:45:00 -0000 [thread overview]
Message-ID: <20010110154447.Q2032@wolery.stanford.edu> (raw)
In-Reply-To: <20010110215317.A25399@daikokuya.demon.co.uk>
On Wed, Jan 10, 2001 at 09:53:18PM +0000, Neil Booth wrote:
> Zack Weinberg wrote:-
>
> > The tokenizer is, in my tests, consistently faster than the analogue
> > in GCC 2.95. Macro expansion can still be a bottleneck under some
> > conditions.
>
> That's interesting. Are these tests you've done recently? i.e. is it
> since I moved us to the forwards-looking, almost-no-step-back lexer?
> It's good news if it is.
I haven't done a rigorous head-to-head test recently, but we are
measurably faster than we were in July, and that wasn't much slower
than 2.95. This is C at -O0, so no major backend or parser
regressions to confuse the issue.
Most of the win is probably from not tokenizing twice.
> Stand-alone CPP is dog slow on token output (50%-70% of run-time!),
> because of GLIBC. But we know that, and decided we don't care too
> much for the moment since for the common case we're now integrated.
*nod*
> If you like, I can work on the function-like macro expansion as a
> "performance enhancement" during the GCC 3.0 branch for release. I
> think we can speed up nested function-like macros a lot (and have an
> old patch on my drive to do so, but it would need dusting off a
> little).
I think that'd be a good idea.
zw
next prev parent reply other threads:[~2001-01-10 15:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 9:56 David Korn
2001-01-10 11:14 ` Zack Weinberg
2001-01-10 13:54 ` Neil Booth
2001-01-10 15:45 ` Zack Weinberg [this message]
2001-01-10 15:26 ` Joe Buck
-- strict thread matches above, loose matches on Subject: below --
2001-01-10 11:45 dewar
2001-01-10 10:21 dewar
2001-01-10 9:35 dewar
2001-01-10 18:53 ` Yu Xuanwei
2001-01-10 9:29 dewar
2001-01-10 9:11 David Korn
2001-01-10 9:02 Phil Edwards
2001-01-10 8:50 dewar
2001-01-09 19:52 dewar
2001-01-09 14:55 dewar
2001-01-09 15:43 ` Stan Shebs
2001-01-10 22:55 ` Toon Moene
2001-01-10 5:29 ` Andi Kleen
2001-01-10 8:32 ` Phil Edwards
2001-01-10 15:12 ` Stan Shebs
2001-01-09 11:26 dewar
2001-01-08 21:09 dewar
2001-01-09 0:33 ` Geoff Keating
2001-01-08 20:41 dewar
2001-01-09 3:01 ` Rob Taylor
2001-01-09 10:04 ` amep
2001-01-09 14:36 ` Stan Shebs
[not found] <978997896.4164.ezmlm@gcc.gnu.org>
2001-01-08 19:45 ` amep
2001-01-08 21:00 ` Geoff Keating
2001-01-09 0:41 ` Adrien Hernot
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=20010110154447.Q2032@wolery.stanford.edu \
--to=zackw@stanford.edu \
--cc=gcc@gcc.gnu.org \
--cc=neil@daikokuya.demon.co.uk \
/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).