From: Phil Edwards <pedwards@disaster.jaj.com>
To: Justin Guyett <jfg@sonicity.com>
Cc: Neil Booth <neil@daikokuya.demon.co.uk>,
Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>,
Marc Espie <espie@quatramaran.ens.fr>,
gcc@gcc.gnu.org
Subject: Re: [GCC 3.0] Bad regression, binary size
Date: Mon, 09 Jul 2001 14:59:00 -0000 [thread overview]
Message-ID: <20010709180015.A8502@disaster.jaj.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0107091344450.1118-100000@straylight.int.sonicity.com>
On Mon, Jul 09, 2001 at 02:54:21PM -0700, Justin Guyett wrote:
> I dunno about the 1minute+ helloworld compile time someone just suggested,
> but this is disturbing:
> (v2.95) g++ -o hello hello.cc 0.15s user 0.03s system 96% cpu 0.186 total
> (v3.0) g++ -o hello hello.cc 2.04s user 0.06s system 99% cpu 2.102 total
>
> if there's a 2 second loading overhead for g++v3, that's 2 seconds * (#
> files) which can be quite a lot in large trees. Is this simply from
> linking in the new libstdc++?
Parsing the libstdc++ headers takes time, mostly because nearly all the
code is in the headers. Once we have 'export' this should be better.
Phil
--
Would I had phrases that are not known, utterances that are strange, in
new language that has not been used, free from repetition, not an utterance
which has grown stale, which men of old have spoken.
- anonymous Egyptian scribe, c.1700 BC
next prev parent reply other threads:[~2001-07-09 14:59 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 8:42 dewar
2001-07-09 0:06 ` Marc Espie
2001-07-09 13:12 ` Gerald Pfeifer
2001-07-09 13:28 ` Neil Booth
2001-07-09 14:13 ` Gerald Pfeifer
2001-07-09 14:36 ` Bobby McNulty
2001-07-09 16:32 ` Inlining heuristics fun (Re: [GCC 3.0] Bad regression, binary size) Daniel Berlin
2001-07-09 14:54 ` [GCC 3.0] Bad regression, binary size Justin Guyett
2001-07-09 14:59 ` Phil Edwards [this message]
2001-07-09 15:04 ` Marc Espie
2001-07-09 16:43 ` Daniel Berlin
-- strict thread matches above, loose matches on Subject: below --
2001-07-23 19:42 dewar
2001-07-24 9:27 ` Linus Torvalds
2001-07-23 4:46 Jonathan Thornburg
2001-07-23 15:14 ` Linus Torvalds
2001-07-09 10:13 dewar
2001-07-09 10:37 ` Linus Torvalds
2001-07-09 7:50 dewar
2001-07-09 7:18 dewar
2001-07-09 7:22 ` Marc Espie
2001-07-05 8:31 dewar
2001-07-05 8:38 ` Marc Espie
2001-07-05 7:39 Marc Espie
2001-07-05 7:51 ` Marc Espie
2001-07-05 8:07 ` Joern Rennecke
2001-07-05 8:12 ` Marc Espie
2001-07-05 8:17 ` David Edelsohn
2001-07-05 8:22 ` Marc Espie
2001-07-05 15:14 ` Geoff Keating
2001-07-07 13:09 ` Richard Henderson
2001-07-07 14:41 ` Jamie Lokier
2001-07-07 16:45 ` Richard Henderson
2001-07-08 14:28 ` Linus Torvalds
2001-07-08 23:59 ` Marc Espie
2001-07-09 6:06 ` Tim Prince
2001-07-09 9:10 ` Linus Torvalds
2001-07-09 9:28 ` Marc Espie
2001-07-09 9:58 ` Linus Torvalds
2001-07-09 10:10 ` Paolo Carlini
2001-07-09 14:49 ` Richard Henderson
2001-07-09 15:23 ` Linus Torvalds
2001-07-09 15:55 ` Joern Rennecke
2001-07-09 16:14 ` Linus Torvalds
2001-07-09 16:05 ` Richard Henderson
2001-07-09 16:24 ` Linus Torvalds
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=20010709180015.A8502@disaster.jaj.com \
--to=pedwards@disaster.jaj.com \
--cc=espie@quatramaran.ens.fr \
--cc=gcc@gcc.gnu.org \
--cc=jfg@sonicity.com \
--cc=neil@daikokuya.demon.co.uk \
--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).