public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "holger dot hopp at sap dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/34029]  New: internal compiler error: verify_stmts failed
Date: Thu, 08 Nov 2007 13:40:00 -0000	[thread overview]
Message-ID: <bug-34029-15329@http.gcc.gnu.org/bugzilla/> (raw)

I discovered following internal compiler error in gcc 4.3.0 (trunk).
The cause is the svn change 125925.

The title sounds to be similar to bug 34018, but the removal of change
125925 does not help for bug 34018. So this bug must be something
different.

gcc version:  gcc 4.3.0 svn revision 125925 and later
at least with gcc 4.3.0 svn revision 129958 (20071107).

$ gcc -v
Using built-in specs.
Target: x86_64-unknown-linux-gnu
Configured with: ../configure --prefix=...my_path... --enable-shared
--with-gmp=...my_path... --with-mpfr=...my_path... --enable-languages=c,c++
Thread model: posix
gcc version 4.3.0 20071107 (experimental) (GCC)

steps to reproduce:

$ gcc -O2 -c testcase.c
testcase.c: In function 'checkVersionLibtestcase':
testcase.c:10: error: invalid array index
20 - (<unnamed-signed:64>) &version_testcase;

testcase.c:10: internal compiler error: verify_stmts failed
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
Exit 1

Without optimization it compiles fine:
$ gcc -c testcase.c

Commenting out change 125925 also compiles fine (patch attached).


-- 
           Summary: internal compiler error: verify_stmts failed
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: holger dot hopp at sap dot com
 GCC build triplet: x86_64-unknown-linux-gnu
  GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu


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


             reply	other threads:[~2007-11-08 13:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 13:40 holger dot hopp at sap dot com [this message]
2007-11-08 13:41 ` [Bug tree-optimization/34029] " holger dot hopp at sap dot com
2007-11-08 18:21 ` [Bug tree-optimization/34029] [4.3 Regression] " pinskia at gcc dot gnu dot org
2007-11-08 20:27 ` jakub at gcc dot gnu dot org
2007-11-10 22:25 ` pinskia at gcc dot gnu dot org
2007-11-10 22:26 ` pinskia at gcc dot gnu dot org
2007-11-20 11:50 ` jakub at gcc dot gnu dot org
2007-11-27 22:17 ` mmitchel at gcc dot gnu dot org
2008-01-03 16:49 ` rguenth at gcc dot gnu dot org
2008-01-03 17:03 ` pinskia at gcc dot gnu dot org
2008-01-04 13:49 ` rguenth at gcc dot gnu dot org
2008-01-04 13:51 ` rguenth at gcc dot gnu dot org
2008-01-04 16:04 ` rguenth at gcc dot gnu dot org
2008-01-04 16:12 ` rguenth at gcc dot gnu dot 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-34029-15329@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).