public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/52097] New: ICE: in get_bit_range, at expr.c:4535 with -O -flto -fexceptions -fnon-call-exceptions --param allow-store-data-races=0
Date: Thu, 02 Feb 2012 20:02:00 -0000	[thread overview]
Message-ID: <bug-52097-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52097
           Summary: ICE: in get_bit_range, at expr.c:4535 with -O -flto
                    -fexceptions -fnon-call-exceptions --param
                    allow-store-data-races=0
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: zsojka@seznam.cz
              Host: x86_64-pc-linux-gnu
            Target: x86_64-pc-linux-gnu


Created attachment 26556
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26556
reduced testcase (from gcc.c-torture/execute/20031201-1.c)

Compiler output:
$ gcc -O -flto -fexceptions -fnon-call-exceptions --param
allow-store-data-races=0 testcase.c 
In file included from testcase.c:5:0,
                 from :0:
testcase.c: In function 'main':
testcase.c:10:9: internal compiler error: in get_bit_range, at expr.c:4535
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
lto-wrapper: /mnt/svn/gcc-trunk/binary-latest/bin/gcc returned 1 exit status
/usr/bin/ld: lto-wrapper failed
collect2: error: ld returned 1 exit status

Tested revisions:
r183741 - crash


             reply	other threads:[~2012-02-02 20:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02 20:02 zsojka at seznam dot cz [this message]
2012-02-03 10:10 ` [Bug middle-end/52097] " rguenth at gcc dot gnu.org
2012-02-14  1:11 ` aldyh at gcc dot gnu.org
2012-02-14  9:04 ` rguenther at suse dot de
2012-02-14 10:09 ` rguenth at gcc dot gnu.org
2012-02-14 13:23 ` rguenth at gcc dot gnu.org
2012-02-14 14:01 ` rguenth at gcc dot gnu.org
2012-02-14 15:52 ` markus at trippelsdorf dot de
2012-03-06  9:54 ` rguenth at gcc dot gnu.org
2012-03-06  9:57 ` rguenth at gcc dot gnu.org
2012-03-08  7:56 ` krebbel at gcc dot gnu.org
2012-03-08  8:27 ` pinskia at gcc dot gnu.org
2012-03-14 11:03 ` rguenth at gcc dot gnu.org
2012-06-04  8:43 ` rguenth at gcc dot gnu.org
2013-02-19 20:38 ` LpSolit at netscape dot net

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