public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56534] [4.7/4.8 Regression] ICE Segfault on invalid code in check_elaborated_type_specifier
Date: Tue, 05 Mar 2013 16:37:00 -0000	[thread overview]
Message-ID: <bug-56534-4-Feo7lhizNL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56534-4@http.gcc.gnu.org/bugzilla/>


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

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2013-03-05
         AssignedTo|unassigned at gcc dot       |paolo.carlini at oracle dot
                   |gnu.org                     |com
     Ever Confirmed|0                           |1

--- Comment #2 from Paolo Carlini <paolo.carlini at oracle dot com> 2013-03-05 16:36:42 UTC ---
Must be easy to fix.


  parent reply	other threads:[~2013-03-05 16:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 13:19 [Bug c++/56534] New: " gcc at abeckmann dot de
2013-03-05 13:31 ` [Bug c++/56534] " paolo.carlini at oracle dot com
2013-03-05 13:43 ` rguenth at gcc dot gnu.org
2013-03-05 16:37 ` paolo.carlini at oracle dot com [this message]
2013-03-06  8:40 ` jakub at gcc dot gnu.org
2013-03-06 10:13 ` paolo.carlini at oracle dot com
2013-03-06 23:41 ` paolo.carlini at oracle dot com
2013-03-06 23:48 ` paolo at gcc dot gnu.org
2013-03-07  0:38 ` [Bug c++/56534] [4.7 " paolo.carlini at oracle dot com
2013-03-09 10:32 ` paolo.carlini at oracle dot com
2013-03-09 11:49 ` paolo at gcc dot gnu.org
2013-03-09 11:50 ` paolo.carlini at oracle dot com

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-56534-4-Feo7lhizNL@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).