From: Mark Mitchell <mark@codesourcery.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>,
Joe Buck <jbuck@synopsys.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: C++ compile-time regressions (was: GCC 3.0.1 Status Report)
Date: Mon, 23 Jul 2001 14:36:00 -0000 [thread overview]
Message-ID: <3814871836.995952317@[192.168.0.164]> (raw)
In-Reply-To: <Pine.BSF.4.33.0107232051290.91617-100000@deneb.dbai.tuwien.ac.at>
> No. Not yet. :-( Performance benchmarks are *detrimental*. Desastrous.
> :-(
Would you try experimenting with `--param max-inline-insns=N' for different
values of N to find where a better compromise is? (It looks like perhaps
100 was too small. Daniel also indicated the heuristic used to approximate
instructions from statements wasn't scaled quite right, so 100 isn't really
a literal value here.)
You might have already done this experiment, in which case you could submit
a patch to pick a better value.
Realistically, I think we have to be willing to compromise here; the 3.0.1
compiler is going to be slower *and* probably generate slower code than
2.95, which is too bad, but that seems to be where we're at. If we could
get to 10-25% on both figures that would be better than having one figure
small and the other massive.
Then, we continue working on Nathan/Daniel's stuff and hope to have it
ready for 3.1, or maybe even 3.0.2.
-- Mark
next prev parent reply other threads:[~2001-07-23 14:36 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
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 [this message]
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='3814871836.995952317@[192.168.0.164]' \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.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).