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 debug/64511] [5 Regression] ICE at -O3 with -g enabled on x86_64-linux-gnu
Date: Wed, 21 Jan 2015 09:02:00 -0000	[thread overview]
Message-ID: <bug-64511-4-zxCIQjw19A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64511-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64511

--- Comment #9 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 20 Jan 2015, jakub at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64511
> 
> --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> Note, this problem went away with r219646.  Shall we declare it as fixed or at
> least turn into non-regression?

I'd say the bug has gone latent again.  At some point we may decide to
drop the regression marker but for now I'd like somebody to investigate
and fix the issue.


  parent reply	other threads:[~2015-01-21  9:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 19:01 [Bug c/64511] New: " su at cs dot ucdavis.edu
2015-01-06 21:03 ` [Bug c/64511] [5 Regression] " hjl.tools at gmail dot com
2015-01-06 22:07 ` [Bug debug/64511] " glisse at gcc dot gnu.org
2015-01-08  9:06 ` rguenth at gcc dot gnu.org
2015-01-12 14:51 ` rguenth at gcc dot gnu.org
2015-01-13 12:40 ` rguenth at gcc dot gnu.org
2015-01-13 15:31 ` jakub at gcc dot gnu.org
2015-01-20 17:42 ` jakub at gcc dot gnu.org
2015-01-21  6:38 ` su at cs dot ucdavis.edu
2015-01-21  9:02 ` rguenther at suse dot de [this message]
2015-01-21 10:04 ` jakub at gcc dot gnu.org
2015-01-21 10:30 ` jakub at gcc dot gnu.org
2015-01-21 22:00 ` jakub at gcc dot gnu.org
2015-01-22  7:44 ` su at cs dot ucdavis.edu
2015-01-22  7:48 ` jakub at gcc dot gnu.org
2015-01-22  7:51 ` su at cs dot ucdavis.edu
2015-01-22 14:06 ` jakub at gcc dot gnu.org
2015-02-01 17:32 ` jakub at gcc dot gnu.org
2015-02-01 22:01 ` jakub at gcc dot gnu.org
2015-02-03 20:41 ` aoliva at gcc dot gnu.org
2015-02-04 14:29 ` jakub 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-64511-4-zxCIQjw19A@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).