public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61670] ICE on invalid in tree_nop_conversion
Date: Sun, 14 Dec 2014 14:13:00 -0000 [thread overview]
Message-ID: <bug-61670-4-PF3o5gB8he@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61670-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61670
Marc Glisse <glisse at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |error-recovery,
| |ice-on-invalid-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-12-14
Known to work|5.0 |
Ever confirmed|0 |1
--- Comment #2 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Ville Voutilainen from comment #1)
> Current trunk does not ICE. Please close.
It does crash for me. Ville, could you please check the PRs you recently
commented on? There may be others where using a release compiler gave
unexpected results.
next prev parent reply other threads:[~2014-12-14 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 11:14 [Bug c++/61670] New: " dimhen at gmail dot com
2014-12-14 1:07 ` [Bug c++/61670] " ville.voutilainen at gmail dot com
2014-12-14 14:13 ` glisse at gcc dot gnu.org [this message]
2014-12-14 15:06 ` ville.voutilainen at gmail dot com
2014-12-14 15:22 ` glisse at gcc dot gnu.org
2014-12-14 18:27 ` dimhen at gmail dot com
2015-03-25 12:18 ` mpolacek at gcc dot gnu.org
2015-03-25 20:10 ` mpolacek at gcc dot gnu.org
2015-03-25 20:58 ` mpolacek 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-61670-4-PF3o5gB8he@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).