From: Gerald Pfeifer <gerald@pfeifer.com>
To: Theo de Raadt <deraadt@cvs.openbsd.org>, tech@openbsd.org
Cc: gcc@gcc.gnu.org, Daniel Berlin <dberlin@dberlin.org>,
Daniel Jacobowitz <drow@false.org>,
Gabriel Dos Reis <gdr@integrable-solutions.net>,
Marc Espie <espie@quatramaran.ens.fr>,
Andrew Pinski <pinskia@physics.uc.edu>
Subject: Re: gcc and compiling speed
Date: Sun, 14 Mar 2004 22:15:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.58.0403142312240.68284@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <1D8A5296-6B37-11D8-B42E-000A95DA505C@dberlin.org>
On Sun, 29 Feb 2004, Daniel Berlin wrote:
> Note that when someone like Gerald provides us with preprocessed C++
> sources of his app that used to compile fast, and then compiled slow
> and took lots of memory, people spent significant amounts of time
> reducing the memory usage and compile time of his application
Indeed, Theo, you should _really_ give it a try and make a self-contained
report.
As an example, below are some of the changes made to GCC in response to
me providing a testcase:
http://gcc.gnu.org/ml/gcc-patches/2004-01/msg00892.html
http://gcc.gnu.org/ml/gcc-patches/2004-01/msg00905.html
http://gcc.gnu.org/ml/gcc/2004-01/msg00670.html
http://gcc.gnu.org/ml/gcc-patches/2004-01/msg00886.html
http://gcc.gnu.org/ml/gcc-patches/2004-01/msg01539.html
http://gcc.gnu.org/ml/gcc-patches/2004-01/msg01630.html
http://gcc.gnu.org/ml/gcc-patches/2004-01/msg01880.html
http://gcc.gnu.org/ml/gcc-patches/2004-01/msg02038.html
http://gcc.gnu.org/ml/gcc-patches/2004-01/msg02055.html
http://gcc.gnu.org/ml/gcc-patches/2004-01/msg02072.html
http://gcc.gnu.org/ml/gcc-patches/2004-01/msg02211.html
http://gcc.gnu.org/ml/gcc-patches/2004-01/msg02279.html
http://gcc.gnu.org/ml/gcc/2004-01/msg01788.html
http://gcc.gnu.org/ml/gcc-patches/2004-01/msg03041.html
http://gcc.gnu.org/ml/gcc-patches/2004-02/msg01930.html
http://gcc.gnu.org/ml/gcc-patches/2004-02/msg01979.html
Gerald
--
Gerald Pfeifer (Jerry) gerald@pfeifer.com http://www.pfeifer.com/gerald/
next prev parent reply other threads:[~2004-03-14 22:15 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 [this message]
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 ` Gabriel Dos Reis
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: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=Pine.BSF.4.58.0403142312240.68284@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=dberlin@dberlin.org \
--cc=deraadt@cvs.openbsd.org \
--cc=drow@false.org \
--cc=espie@quatramaran.ens.fr \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=pinskia@physics.uc.edu \
--cc=tech@openbsd.org \
/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).