From: Andrew Pinski <pinskia@physics.uc.edu>
To: tech@openbsd.org, Marc Espie <espie@quatramaran.ens.fr>
Cc: "gcc@gcc.gnu.org List" <gcc@gcc.gnu.org>,
Andrew Pinski <pinskia@physics.uc.edu>
Subject: gcc and compiling speed
Date: Mon, 01 Mar 2004 00:43:00 -0000 [thread overview]
Message-ID: <75E7D6EA-6B19-11D8-888A-000393A6D2F2@physics.uc.edu> (raw)
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. It seems like you are ignoring
them and still complain about the compile time speed regressions in
GCC. If you (or some from the openbsd project) submit a bug with
numbers and a way to reproduce it with say the openbsd's kernel
sources, we will no longer disagree with you and fix the problem
in GCC.
Thanks,
Andrew Pinski
a gcc bug master and libobjc maintainer
next reply other threads:[~2004-03-01 0:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 0:43 Andrew Pinski [this message]
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
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=75E7D6EA-6B19-11D8-888A-000393A6D2F2@physics.uc.edu \
--to=pinskia@physics.uc.edu \
--cc=espie@quatramaran.ens.fr \
--cc=gcc@gcc.gnu.org \
--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).