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 tree-optimization/51070] [4.6 Regression] ICE verify_gimple failed
Date: Sat, 31 Dec 2011 11:29:00 -0000 [thread overview]
Message-ID: <bug-51070-4-0UFnRfvXSN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51070-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51070
Zdenek Sojka <zsojka at seznam dot cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zsojka at seznam dot cz
--- Comment #5 from Zdenek Sojka <zsojka at seznam dot cz> 2011-12-31 08:49:48 UTC ---
The testcase fails with -O3 -fno-inline or with -O3 when func_37() is declared
with __attribute__((noinline)).
Compiler output:
$ gcc -v
Using built-in specs.
COLLECT_GCC=/mnt/svn/gcc-trunk/binary-latest/bin/gcc
COLLECT_LTO_WRAPPER=/mnt/svn/gcc-trunk/binary-182733-lto-fortran-checking-yes-rtl-df/libexec/gcc/x86_64-unknown-linux-gnu/4.7.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /mnt/svn/gcc-trunk//configure --enable-checking=yes,rtl,df
--enable-languages=c,c++,lto,fortran
--prefix=/mnt/svn/gcc-trunk/binary-182733-lto-fortran-checking-yes-rtl-df/
--with-cloog --with-ppl --with-cloog-include=/usr/include/cloog-ppl/
--disable-ppl-version-check
Thread model: posix
gcc version 4.7.0 20111229 (experimental) (GCC)
$ gcc -O3 -fno-inline gcc.dg/torture/pr51070.c
gcc.dg/torture/pr51070.c: In function 'func_9':
gcc.dg/torture/pr51070.c:26:1: error: invalid PHI argument
.MEM_5
gcc.dg/torture/pr51070.c:26:1: error: incompatible types in PHI argument 0
int
void
g_95_I_lsm.22_32 = PHI <.MEM_5(5)>
gcc.dg/torture/pr51070.c:26:1: internal compiler error: verify_gimple failed
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
I didn't open a new PR because the ICE message is the same and the conditions
under which it happens are very similiar. Of course, I will open a new PR if
you tell me so.
next prev parent reply other threads:[~2011-12-31 8:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 21:24 [Bug c/51070] New: " regehr at cs dot utah.edu
2011-11-10 11:08 ` [Bug tree-optimization/51070] [4.6/4.7 Regression] " rguenth at gcc dot gnu.org
2011-11-10 12:23 ` rguenth at gcc dot gnu.org
2011-11-10 13:48 ` rguenth at gcc dot gnu.org
2011-11-10 13:59 ` [Bug tree-optimization/51070] [4.6 " rguenth at gcc dot gnu.org
2011-12-31 11:29 ` zsojka at seznam dot cz [this message]
2012-01-02 9:10 ` [Bug tree-optimization/51070] [4.6/4.7 " rguenth at gcc dot gnu.org
2012-01-03 12:07 ` rguenth at gcc dot gnu.org
2012-01-03 12:12 ` rguenth at gcc dot gnu.org
2012-01-03 12:13 ` rguenth at gcc dot gnu.org
2012-06-12 9:44 ` liujiangning 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-51070-4-0UFnRfvXSN@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).