public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dberlin at dberlin dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/33237] [4.3 Regression] Tree memory partitioning is spending 430 seconds of a 490 second compile. Date: Fri, 25 Jan 2008 17:43:00 -0000 [thread overview] Message-ID: <20080125165128.5344.qmail@sourceware.org> (raw) In-Reply-To: <bug-33237-11700@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from dberlin at gcc dot gnu dot org 2008-01-25 16:51 ------- Subject: Re: [4.3 Regression] Tree memory partitioning is spending 430 seconds of a 490 second compile. On 25 Jan 2008 16:40:54 -0000, rguenth at gcc dot gnu dot org <gcc-bugzilla@gcc.gnu.org> wrote: > > I think we are also over-counting here - shouldn't we just walk over all > NMTs once? > Yes. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33237
next prev parent reply other threads:[~2008-01-25 16:52 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-08-29 18:52 [Bug tree-optimization/33237] New: " bergner at gcc dot gnu dot org 2007-08-29 18:54 ` [Bug tree-optimization/33237] " bergner at gcc dot gnu dot org 2007-08-29 20:50 ` [Bug tree-optimization/33237] [4.3 Regression]Tree " pinskia at gcc dot gnu dot org 2007-08-29 20:52 ` pinskia at gcc dot gnu dot org 2007-09-05 2:23 ` mmitchel at gcc dot gnu dot org 2007-11-01 15:38 ` [Bug tree-optimization/33237] [4.3 Regression] Tree " rguenth at gcc dot gnu dot org 2007-12-02 23:47 ` pinskia at gcc dot gnu dot org 2008-01-08 12:58 ` steven at gcc dot gnu dot org 2008-01-08 14:14 ` rguenth at gcc dot gnu dot org 2008-01-08 15:16 ` dnovillo at gcc dot gnu dot org 2008-01-25 17:20 ` rguenth at gcc dot gnu dot org 2008-01-25 17:43 ` dberlin at dberlin dot org [this message] 2008-01-25 18:03 ` rguenth at gcc dot gnu dot org 2008-03-14 17:01 ` [Bug tree-optimization/33237] [4.3/4.4 " rguenth at gcc dot gnu dot org 2008-06-06 15:05 ` rguenth at gcc dot gnu dot org 2008-06-06 20:22 ` rguenth at gcc dot gnu dot org 2008-08-27 22:05 ` jsm28 at gcc dot gnu dot org 2008-12-07 11:57 ` steven at gcc dot gnu dot org 2008-12-07 12:23 ` rguenth at gcc dot gnu dot org 2008-12-08 15:04 ` dnovillo at google dot com 2009-01-24 10:28 ` rguenth at gcc dot gnu dot org 2009-02-23 13:35 ` rguenth at gcc dot gnu dot org 2009-04-03 10:28 ` [Bug tree-optimization/33237] [4.3/4.4/4.5 " rguenth at gcc dot gnu dot org 2009-04-03 10:30 ` [Bug tree-optimization/33237] [4.3/4.4 " rguenth at gcc dot gnu dot org 2009-04-23 9:35 ` rguenth at gcc dot gnu dot org 2009-08-04 12:36 ` rguenth at gcc dot gnu dot org 2010-05-22 18:20 ` 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=20080125165128.5344.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: linkBe 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).