From: Joe Buck <jbuck@synopsys.COM>
To: mark@codesourcery.com (Mark Mitchell)
Cc: pfeifer@dbai.tuwien.ac dot@(Gerald Pfeifer),
gcc@gcc.gnu.org (gcc@gcc.gnu.org)
Subject: Re: C++ compile-time regressions (was: GCC 3.0.1 Status Report)
Date: Fri, 20 Jul 2001 14:22:00 -0000 [thread overview]
Message-ID: <200107202121.OAA02177@atrus.synopsys.com> (raw)
In-Reply-To: <35850000.995650535@warlock.codesourcery.com>
Gerald:
> > Well, here I have to step up again, I'm afraid. If you look at
> > http://gcc.gnu.org/ml/gcc/2001-07/msg01376.html
> > you'll see that C++ projects heavily relying on STL apparently
> > simply cannot use GCC 3.0.
Mark:
> An extreme statement, but, that aside, as you know people are working
> on fixes. The point is that 3.0.1 is better than 3.0; that is good.
> Ideally, it would be better, but the point is to make consistent
> progress.
To make more progress and make 3.0.2 usable, we may need to broaden the
acceptance criteria beyond just fixing regressions. If we can find
fairly simple patches that improve performance, they should be considered
for inclusion.
next prev parent reply other threads:[~2001-07-20 14:22 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 18:41 GCC 3.0.1 Status Report Mark Mitchell
2001-07-19 6:17 ` Joseph S. Myers
2001-07-20 3:45 ` Nathan Sidwell
2001-07-20 10:26 ` C++ compile-time regressions (was: GCC 3.0.1 Status Report) Gerald Pfeifer
2001-07-20 10:54 ` Nathan Sidwell
2001-07-20 16:41 ` Loren James Rittle
2001-07-23 5:17 ` Gerald Pfeifer
2001-07-23 11:56 ` Daniel Berlin
2001-07-23 2:51 ` Gerald Pfeifer
2001-07-20 10:55 ` Mark Mitchell
2001-07-20 14:22 ` Joe Buck [this message]
2001-07-20 16:28 ` Mark Mitchell
2001-07-20 21:05 ` Joe Buck
2001-07-23 10:44 ` Gerald Pfeifer
2001-07-23 11:12 ` Joe Buck
2001-07-23 11:57 ` Gerald Pfeifer
2001-07-23 13:30 ` Joe Buck
2001-07-24 7:18 ` Gerald Pfeifer
2001-07-24 7:55 ` Daniel Berlin
2001-07-24 10:09 ` Joe Buck
2001-07-24 10:19 ` Gabriel Dos Reis
2001-07-24 10:44 ` Joe Buck
2001-07-24 10:56 ` Gabriel Dos Reis
2001-07-24 10:25 ` Daniel Berlin
2001-07-24 10:49 ` Joe Buck
2001-07-24 11:08 ` Daniel Berlin
2001-07-23 14:36 ` Mark Mitchell
2001-07-25 8:06 ` Gerald Pfeifer
2001-08-02 0:20 ` C++ compile-time regressions Gerald Pfeifer
2001-08-02 0:26 ` Mark Mitchell
2001-08-02 11:00 ` aoliva
2001-08-02 12:00 ` Mark Mitchell
2001-08-02 12:26 ` aoliva
2001-08-02 12:37 ` Joe Buck
2001-08-02 12:41 ` Mark Mitchell
2001-08-02 12:48 ` Joe Buck
2001-08-02 13:53 ` Daniel Berlin
2001-08-07 7:54 ` Gerald Pfeifer
2001-07-23 11:54 ` C++ compile-time regressions (was: GCC 3.0.1 Status Report) Daniel Berlin
2001-07-23 12:42 ` Bernd Schmidt
2001-07-23 12:50 ` law
2001-07-23 13:15 ` Daniel Berlin
2001-07-23 14:00 ` law
2001-07-20 10:57 ` Daniel Berlin
2001-07-20 14:20 ` Joe Buck
2001-07-25 17:52 ` GCC 3.0.1 Status Report Marc Espie
2001-08-13 23:15 ` Mark Mitchell
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=200107202121.OAA02177@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=mark@codesourcery.com \
--cc=pfeifer@dbai.tuwien.ac \
/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).