public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/36498] [4.3 Regression] time/memory hog for large c++ source.
Date: Sat, 14 Jun 2008 22:04:00 -0000	[thread overview]
Message-ID: <20080614220404.24023.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36498-7667@http.gcc.gnu.org/bugzilla/>



------- Comment #15 from rguenther at suse dot de  2008-06-14 22:04 -------
Subject: Re:  [4.3 Regression] time/memory hog for large
 c++ source.

On Fri, 13 Jun 2008, mmitchel at gcc dot gnu dot org wrote:

> Richard --
> 
> Is this still an issue, after your patch?

It's still 4 times slower and uses twice as much memory.  It will
be fixed with the partitioning patch I posted yesterday.

Richard.


-- 


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


  parent reply	other threads:[~2008-06-14 22:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11 14:05 [Bug other/36498] New: " pluto at agmk dot net
2008-06-11 14:06 ` [Bug other/36498] " pluto at agmk dot net
2008-06-11 14:11 ` pluto at agmk dot net
2008-06-11 14:47 ` rguenth at gcc dot gnu dot org
2008-06-11 14:56 ` rguenth at gcc dot gnu dot org
2008-06-11 15:21 ` rguenth at gcc dot gnu dot org
2008-06-11 19:28 ` pluto at agmk dot net
2008-06-11 19:36 ` rguenth at gcc dot gnu dot org
2008-06-11 20:15 ` pluto at agmk dot net
2008-06-11 20:42 ` rguenth at gcc dot gnu dot org
2008-06-11 20:50 ` pluto at agmk dot net
2008-06-11 21:05 ` rguenth at gcc dot gnu dot org
2008-06-11 21:18 ` pluto at agmk dot net
2008-06-13  8:43 ` rguenth at gcc dot gnu dot org
2008-06-13 21:53 ` mmitchel at gcc dot gnu dot org
2008-06-14 22:04 ` rguenther at suse dot de [this message]
2008-06-23 10:14 ` rguenth at gcc dot gnu dot org

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=20080614220404.24023.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).