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 rtl-optimization/54343] RTL postreload leaks DF memory
Date: Wed, 22 Aug 2012 13:02:00 -0000	[thread overview]
Message-ID: <bug-54343-4-RTzUHyxy97@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54343-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> 2012-08-22 13:01:53 UTC ---
On Wed, 22 Aug 2012, dnovillo at google dot com wrote:

> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54343
> 
> --- Comment #5 from dnovillo at google dot com <dnovillo at google dot com> 2012-08-22 12:43:02 UTC ---
> On 2012-08-22 05:32 , rguenth at gcc dot gnu.org wrote:
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54343
> >
> > --- Comment #4 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-08-22 09:32:13 UTC ---
> > (In reply to comment #3)
> >> HJ's fix for PR 54332 will probably fix this one, too.  Could you re-test?
> >>
> >> Thanks.
> >
> > Doesn't fix it.
> 
> OK, then it wasn't related.  Do you know if this started happening with 
> rev 190402?

I don't and I don't believe it did.


  parent reply	other threads:[~2012-08-22 13:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21 11:41 [Bug rtl-optimization/54343] New: " rguenth at gcc dot gnu.org
2012-08-21 11:50 ` [Bug rtl-optimization/54343] " steven at gcc dot gnu.org
2012-08-21 19:20 ` steven at gcc dot gnu.org
2012-08-21 21:25 ` dnovillo at gcc dot gnu.org
2012-08-22  9:33 ` rguenth at gcc dot gnu.org
2012-08-22 12:43 ` dnovillo at google dot com
2012-08-22 13:02 ` rguenther at suse dot de [this message]
2013-03-03 17:09 ` steven at gcc dot gnu.org
2024-02-20 14:01 ` rguenth at gcc dot gnu.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=bug-54343-4-RTzUHyxy97@http.gcc.gnu.org/bugzilla/ \
    --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).