From: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>
To: Karel Gardas <kgardas@objectsecurity.com>
Cc: Michael Matz <matz@suse.de>, <gcc@gcc.gnu.org>
Subject: Re: 3.3 compile time regression (22400%)
Date: Tue, 18 Mar 2003 15:33:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0303181616490.22005-100000@bellatrix.tat.physik.uni-tuebingen.de> (raw)
In-Reply-To: <Pine.LNX.4.43.0303181602390.13056-100000@thinkpad.c0202001.roe.itnq.net>
On Tue, 18 Mar 2003, Karel Gardas wrote:
> On Tue, 18 Mar 2003, Karel Gardas wrote:
>
> > Please wait a moment, I've just found that I have deleted all gcc3.3/3.4
> > builds. I'm building right now...
> >
[snipped results showing that -fno-default-inline helps]
Just a thought: maybe this is due to libstdc++ changes and lazy use of
in class definitions of large methods that used to be out of line in 3.2?
Can we set different inlining limits for only libstdc++? I suspect no.
Just to limit the search, I'm only using <vector> and <iostream>, but from
the compile time distribution in my sources I'd point at <vector> for the
culprit.
Maybe this helps,
Richard.
--
Richard Guenther <richard.guenther@uni-tuebingen.de>
WWW: http://www.tat.physik.uni-tuebingen.de/~rguenth/
next prev parent reply other threads:[~2003-03-18 15:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 12:28 Richard Guenther
2003-03-18 12:33 ` Karel Gardas
2003-03-18 13:22 ` Michael Matz
2003-03-18 14:43 ` Karel Gardas
2003-03-18 13:21 ` Michael Matz
2003-03-18 14:25 ` Richard Guenther
2003-03-18 14:50 ` Karel Gardas
2003-03-18 15:19 ` Karel Gardas
2003-03-18 15:26 ` Richard Guenther
2003-03-18 15:33 ` Richard Guenther [this message]
2003-03-18 15:07 ` Richard Guenther
2003-03-18 15:25 ` Michael Matz
2003-03-18 15:09 ` Richard Guenther
2003-03-18 15:19 ` Michael Matz
2003-03-18 15:12 ` Richard Guenther
2003-03-18 15:20 ` Michael Matz
2003-03-18 15:50 ` Karel Gardas
2003-03-18 16:31 ` Richard Guenther
2003-03-18 16:35 ` Albert Chin
2003-03-18 22:57 John David Anglin
2003-03-18 23:54 ` Albert Chin
2003-03-19 0:29 ` Michael Matz
2003-03-19 0:40 ` John David Anglin
2003-03-19 0:40 ` Steven Bosscher
2003-03-19 1:20 ` John David Anglin
2003-03-20 6:23 ` Albert Chin
2003-03-19 20:12 ` John David Anglin
2003-03-19 23:19 S. Bosscher
[not found] <Pine.LNX.4.44.0303181300580.22005-100000@bellatrix.tat.physik.uni-tuebingen .de>
2003-03-18 17:04 ` Steven Bosscher
2003-03-18 17:31 ` Richard Guenther
2003-03-22 15:13 ` Steven Bosscher
2003-03-22 17:03 ` Steven Bosscher
2003-03-23 4:30 ` Janis Johnson
2003-03-23 22:14 ` Richard Guenther
2003-03-24 3:26 ` Richard Guenther
2003-03-24 8:47 ` Steven Bosscher
2003-03-24 10:06 ` Richard Guenther
2003-03-24 15:21 ` Richard Guenther
2003-03-25 2:27 ` Janis Johnson
2003-03-25 15:11 ` Richard Guenther
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.LNX.4.44.0303181616490.22005-100000@bellatrix.tat.physik.uni-tuebingen.de \
--to=rguenth@tat.physik.uni-tuebingen.de \
--cc=gcc@gcc.gnu.org \
--cc=kgardas@objectsecurity.com \
--cc=matz@suse.de \
/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).