From: Jan Hubicka <jh@suse.cz>
To: Fergus Henderson <fjh@cs.mu.oz.au>
Cc: Jan Hubicka <jh@suse.cz>,
Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>,
Nathanael Nerode <neroden@twcny.rr.com>,
gcc@gcc.gnu.org
Subject: Re: GCC still getting a lot slower
Date: Fri, 03 Jan 2003 14:05:00 -0000 [thread overview]
Message-ID: <20030103140502.GA4000@kam.mff.cuni.cz> (raw)
In-Reply-To: <20030103002119.GB10549@ceres.cs.mu.oz.au>
> On 02-Jan-2003, Jan Hubicka <jh@suse.cz> wrote:
> >
> > For C performance I think it can be practical to just benchmark linux
> > kernel build - it is fixed piece as it does not include any external
> > headers, large enought to make measurements hopefully stable enought and
> > tests performance of "usual hand writen C program" that (for C) is about
> > the most important.
>
> The trouble is, which version?
> The Linux kernel itself is not stable. To make a useful benchmark,
> you need to pick a specific version of the Linux kernel.
>
> Old versions of the Linux kernel don't work with current versions of GCC,
> and probably current versions of the Linux kernel won't work with future
> versions of GCC.
Yes, but I think there is large enought overlap to make the measurements
usefull. In casee we are interested in compilation speed only, we can
simply fix new syntax errors.
Honza
>
> --
> Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
> The University of Melbourne | of excellence is a lethal habit"
> WWW: <http://www.cs.mu.oz.au/~fjh> | -- the last words of T. S. Garp.
next prev parent reply other threads:[~2003-01-03 14:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 14:11 Nathanael Nerode
2002-12-31 14:49 ` Paul Jarc
2002-12-31 17:16 ` Diego Novillo
2003-01-02 10:59 ` Gerald Pfeifer
2003-01-02 14:21 ` Jan Hubicka
2003-01-03 0:21 ` Fergus Henderson
2003-01-03 14:05 ` Jan Hubicka [this message]
2003-01-03 10:33 ` Ben Elliston
[not found] <1041382480.23232.35.camel@steven>
2003-01-02 14:24 ` Jan Hubicka
-- strict thread matches above, loose matches on Subject: below --
2002-12-31 23:01 Ritzert
2002-12-31 16:14 Nathanael Nerode
2002-12-31 16:53 ` Paul Jarc
2002-12-31 13:44 Neil Booth
2002-12-31 13:47 ` Paolo Carlini
2002-12-31 13:48 ` Neil Booth
2002-12-31 13:55 ` Paolo Carlini
2002-12-31 14:00 ` Neil Booth
2002-12-31 20:22 ` David Edelsohn
2002-12-31 14:00 ` Diego Novillo
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=20030103140502.GA4000@kam.mff.cuni.cz \
--to=jh@suse.cz \
--cc=fjh@cs.mu.oz.au \
--cc=gcc@gcc.gnu.org \
--cc=neroden@twcny.rr.com \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).