public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/66357] New: ICE on valid code at -O1, -O2 and -O3 on x86_64-linux-gnu in verify_loop_structure, at cfgloop.c:1662
Date: Sun, 31 May 2015 23:44:00 -0000 [thread overview]
Message-ID: <bug-66357-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66357
Bug ID: 66357
Summary: ICE on valid code at -O1, -O2 and -O3 on
x86_64-linux-gnu in verify_loop_structure, at
cfgloop.c:1662
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: su at cs dot ucdavis.edu
Target Milestone: ---
The following code causes an ICE when compiled with the current gcc trunk at
-O1, -O2 and -O3 on x86_64-linux-gnu in both 32-bit and 64-bit modes.
It is a regression from 5.1.x.
$ gcc-trunk -v
Using built-in specs.
COLLECT_GCC=gcc-trunk
COLLECT_LTO_WRAPPER=/usr/local/gcc-trunk/libexec/gcc/x86_64-unknown-linux-gnu/6.0.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc-trunk/configure --prefix=/usr/local/gcc-trunk
--enable-languages=c,c++ --disable-werror --enable-multilib
Thread model: posix
gcc version 6.0.0 20150531 (experimental) [trunk revision 223897] (GCC)
$
$ gcc-trunk -O0 -c small.c
$ gcc-trunk -Os -c small.c
$ gcc-5.1 -O1 -c small.c
$
$ gcc-trunk -O1 -c small.c
small.c: In function ‘fn1’:
small.c:5:1: error: size of loop 1 should be 3, not 2
fn1 ()
^
small.c:5:1: error: bb 16 does not belong to loop 1
small.c:5:1: error: bb 17 does not belong to loop 1
small.c:5:1: error: bb 11 does not belong to loop 1
small.c:5:1: error: loop 1’s header does not belong directly to it
small.c:5:1: internal compiler error: in verify_loop_structure, at
cfgloop.c:1662
0x6f4b85 verify_loop_structure()
../../gcc-trunk/gcc/cfgloop.c:1662
0x9929e0 fix_loop_structure(bitmap_head*)
../../gcc-trunk/gcc/loop-init.c:344
0xb3a5ac repair_loop_structures
../../gcc-trunk/gcc/tree-cfgcleanup.c:784
0xb3a5ac cleanup_tree_cfg()
../../gcc-trunk/gcc/tree-cfgcleanup.c:814
0xa314d4 execute_function_todo
../../gcc-trunk/gcc/passes.c:1899
0xa31d73 execute_todo
../../gcc-trunk/gcc/passes.c:2003
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.
$
---------------------------------
int a, c, e, f;
volatile int d;
void
fn1 ()
{
if (!e)
for (; a; a++)
{
if (e)
for (d++; d;)
;
else
for (c = 0; c; --c)
;
if (f)
for (;;)
{
if (e)
break;
a = 0;
}
}
}
>From gcc-bugs-return-487668-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jun 01 03:24:55 2015
Return-Path: <gcc-bugs-return-487668-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50558 invoked by alias); 1 Jun 2015 03:24:54 -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 50513 invoked by uid 48); 1 Jun 2015 03:24:50 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66331] gfortran.dg/continuation_13.f90 execution failure
Date: Mon, 01 Jun 2015 03:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 5.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-66331-4-pgErOCsGin@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66331-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66331-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: 2015-06/txt/msg00000.txt.bz2
Content-length: 435
https://gcc.gnu.org/bugzilla/show_bug.cgi?idf331
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #4 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Not a bug
next reply other threads:[~2015-05-31 23:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 23:44 su at cs dot ucdavis.edu [this message]
2015-06-01 6:51 ` [Bug tree-optimization/66357] [6 Regression] " miyuki at gcc dot gnu.org
2015-06-01 8:16 ` rguenth at gcc dot gnu.org
2015-06-01 13:59 ` rguenth at gcc dot gnu.org
2015-06-01 13:59 ` rguenth 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-66357-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).