public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/51768] New: [4.5/4.6/4.7 Regression] ICE with invalid asm goto
Date: Thu, 05 Jan 2012 15:48:00 -0000	[thread overview]
Message-ID: <bug-51768-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 51768
           Summary: [4.5/4.6/4.7 Regression] ICE with invalid asm goto
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Keywords: ice-on-invalid-code
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: jakub@gcc.gnu.org


void
foo (void)
{
  asm goto ("" : : : : lab, lab, lab2, lab);/* { dg-error "duplicate asm
operand name" } */
lab:;
lab2:;
}

void
bar (void)
{
  asm goto ("" : : [lab] "i" (0) : : lab);/* { dg-error "duplicate asm operand
name" } */
lab:;
}

ICEs with tree-checking (or just crashes during error reporting if not tree
checking).


             reply	other threads:[~2012-01-05 15:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 15:48 jakub at gcc dot gnu.org [this message]
2012-01-05 15:55 ` [Bug middle-end/51768] " jakub at gcc dot gnu.org
2012-01-05 15:57 ` jakub at gcc dot gnu.org
2012-01-05 20:19 ` jakub at gcc dot gnu.org
2012-01-05 20:22 ` [Bug middle-end/51768] [4.5/4.6 " jakub at gcc dot gnu.org
2012-02-09 17:22 ` jakub at gcc dot gnu.org
2012-02-09 21:35 ` [Bug middle-end/51768] [4.5 " jakub at gcc dot gnu.org
2012-02-09 21:46 ` jakub at gcc dot gnu.org
2012-06-12  3:49 ` jye2 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-51768-4@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).