public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/39860] extremely long compile time
Date: Thu, 23 Apr 2009 09:35:00 -0000	[thread overview]
Message-ID: <20090423093448.12071.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39860-15934@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from rguenth at gcc dot gnu dot org  2009-04-23 09:34 -------
 tree memory partitioning:  51.43 (20%) usr   0.26 ( 9%) sys  51.80 (20%) wall 
    19 kB ( 0%) ggc
 tree operand scan     : 149.30 (58%) usr   1.20 (43%) sys 151.17 (57%) wall  
18536 kB ( 4%) ggc

4.4 uses

 tree memory partitioning:  42.43 (26%) usr   0.33 (14%) sys  42.84 (26%) wall 
    13 kB ( 0%) ggc
 tree operand scan     :  71.91 (45%) usr   0.59 (25%) sys  72.88 (44%) wall  
14670 kB ( 3%) ggc

trunk does not have the above on the radar at all.

thus ...

*** This bug has been marked as a duplicate of 33237 ***


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |DUPLICATE


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39860


      parent reply	other threads:[~2009-04-23  9:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23  4:23 [Bug c++/39860] New: " pletzer at txcorp dot com
2009-04-23  4:38 ` [Bug c++/39860] " pletzer at txcorp dot com
2009-04-23  9:35 ` rguenth at gcc dot gnu dot org [this message]

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=20090423093448.12071.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).