public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "spear at cse dot lehigh.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libitm/60004] New: Conditional return within transaction causes ICE
Date: Fri, 31 Jan 2014 04:08:00 -0000	[thread overview]
Message-ID: <bug-60004-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 60004
           Summary: Conditional return within transaction causes ICE
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libitm
          Assignee: unassigned at gcc dot gnu.org
          Reporter: spear at cse dot lehigh.edu

The following code produces an ICE:
int a;
int f() {
    __transaction_atomic {
        if (a == 5)
            return 1;
    }
}

compilation:
gcc -std=c++11 -fgnu-tm test_if.cc -c

error:
test_if.cc: In function ‘int f()’:
test_if.cc:4:5: internal compiler error: in lower_eh_constructs_2, at
tree-eh.c:2105
 int f()
     ^
0xb96c26 lower_eh_constructs_2
        ../../../src/gcc-libitm/gcc/tree-eh.c:2105
0xb96c26 lower_eh_constructs_1
        ../../../src/gcc-libitm/gcc/tree-eh.c:2123
0xb979a4 lower_try_finally_switch
        ../../../src/gcc-libitm/gcc/tree-eh.c:1392
0xb979a4 lower_try_finally
        ../../../src/gcc-libitm/gcc/tree-eh.c:1722
0xb979a4 lower_eh_constructs_2
        ../../../src/gcc-libitm/gcc/tree-eh.c:2065
0xb979a4 lower_eh_constructs_1
        ../../../src/gcc-libitm/gcc/tree-eh.c:2123
0xb98e91 lower_eh_constructs
        ../../../src/gcc-libitm/gcc/tree-eh.c:2141
0xb98e91 execute
        ../../../src/gcc-libitm/gcc/tree-eh.c:2193
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.

Environment: 
gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/home/spear/gcc/install/gcc/libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../../src/gcc-libitm/configure
--prefix=/home/spear/gcc/install/gcc --with-gmp=/home/spear/gcc/install/gmp/
--with-mpfr=/home/spear/gcc/install/mpfr/
--with-mpc=/home/spear/gcc/install/mpc/ --enable-languages=c,c++,lto
--enable-multilib --enable-lto
Thread model: posix
gcc version 4.9.0 20140129 (experimental) (GCC)
>From gcc-bugs-return-442107-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 31 05:11:11 2014
Return-Path: <gcc-bugs-return-442107-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25134 invoked by alias); 31 Jan 2014 05:11:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25009 invoked by uid 48); 31 Jan 2014 05:11:06 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/52727] [4.9 Regression] internal compiler error at dwarf2cfi.c2:685
Date: Fri, 31 Jan 2014 05:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: REOPENED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.7.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-52727-4-dhgOmAunQR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-01/txt/msg03249.txt.bz2
Content-length: 455

http://gcc.gnu.org/bugzilla/show_bug.cgi?idR727

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dominiq at lps dot ens.fr

--- Comment #21 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
*** Bug 59981 has been marked as a duplicate of this bug. ***


             reply	other threads:[~2014-01-31  4:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31  4:08 spear at cse dot lehigh.edu [this message]
2014-01-31  8:21 ` [Bug libitm/60004] " mpolacek at gcc dot gnu.org
2014-01-31 19:36 ` rth at gcc dot gnu.org
2014-01-31 19:41 ` [Bug middle-end/60004] " rth at gcc dot gnu.org
2014-02-01  5:20 ` rth at gcc dot gnu.org
2014-02-01  5:24 ` rth at gcc dot gnu.org
2014-02-01  5:25 ` rth at gcc dot gnu.org
2014-02-01 19:54 ` spear at cse dot lehigh.edu

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-60004-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).