From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Theo de Raadt <deraadt@cvs.openbsd.org>
Cc: Zack Weinberg <zack@codesourcery.com>,
Andrew Pinski <pinskia@physics.uc.edu>,
tech@openbsd.org, Marc Espie <espie@quatramaran.ens.fr>,
"gcc@gcc.gnu.org List" <gcc@gcc.gnu.org>
Subject: Re: gcc and compiling speed
Date: Mon, 01 Mar 2004 04:00:00 -0000 [thread overview]
Message-ID: <m3d67xjkdj.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <200403010349.i213nxpD008197@cvs.openbsd.org>
Theo de Raadt <deraadt@cvs.openbsd.org> writes:
| > Theo de Raadt <deraadt@cvs.openbsd.org> writes:
| >
| > >> Marc,
| > >> Now I know you have been asked before every time you bring up on the
| > >> GCC's mailing list about a set of preprocessed source for openbsd so
| > >> that the speed of GCC will improve.
| > >
| > > How will this improve the speed of gcc?
| >
| > If Marc (or anyone) provides us with a test case for the performance
| > regression - for instance, the set of files produced by running gcc -E
| > over all of the openbsd kernel, which is what Andrew meant - then we
| > can find out why the compiler is slower, and fix it.
| >
| > We do have our own test cases for compile time, and they have been
| > being fixed (mostly by Jan Hubicka) but we don't know that this will
| > help you.
|
| How big is your mailbox?
Well, there is a central database for GCC
http://gcc.gnu.org/bugzilla/
that saves people from getting huge testcases directly in their
mailboxes.
I have no idea how large is GCC's bugzilla harddrive though
-- Gaby
next prev parent reply other threads:[~2004-03-01 4:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 0:43 Andrew Pinski
2004-03-01 2:58 ` Theo de Raadt
2004-03-01 3:07 ` Daniel Jacobowitz
2004-03-01 3:46 ` Theo de Raadt
2004-03-01 3:55 ` Gabriel Dos Reis
2004-03-01 3:59 ` Theo de Raadt
2004-03-01 4:15 ` Daniel Berlin
2004-03-14 22:15 ` Gerald Pfeifer
2004-03-01 6:00 ` Andreas Jaeger
2004-03-01 19:40 ` Peter Galbavy
2004-03-01 19:51 ` Andreas Jaeger
2004-03-01 20:05 ` Peter Galbavy
2004-03-01 20:15 ` William Ahern
2004-03-01 3:10 ` Zack Weinberg
2004-03-01 3:49 ` Theo de Raadt
2004-03-01 4:00 ` Eric Christopher
2004-03-01 4:05 ` Theo de Raadt
2004-03-01 4:11 ` Eric Christopher
2004-03-01 4:00 ` Gabriel Dos Reis [this message]
2004-03-01 4:01 ` Zack Weinberg
[not found] ` <20040301071403.GA8953@tetto.gentiane.org>
2004-03-01 7:27 ` Zack Weinberg
2004-03-01 8:09 ` Steven Bosscher
2004-03-01 4:23 Vincent Diepeveen
2004-03-01 5:00 ` John S. Dyson
2004-03-01 5:31 ` Zack Weinberg
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=m3d67xjkdj.fsf@uniton.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=deraadt@cvs.openbsd.org \
--cc=espie@quatramaran.ens.fr \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@physics.uc.edu \
--cc=tech@openbsd.org \
--cc=zack@codesourcery.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).