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/60903] New: [4.8/4.9/4.10 Regression] ICE: in verify_loop_structure, at cfgloop.c:1647: : edge from 13 to 14 should be marked irreducible
Date: Sun, 20 Apr 2014 08:59:00 -0000	[thread overview]
Message-ID: <bug-60903-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 60903
           Summary: [4.8/4.9/4.10 Regression] ICE: in
                    verify_loop_structure, at cfgloop.c:1647: : edge from
                    13 to 14 should be marked irreducible
           Product: gcc
           Version: 4.10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zsojka at seznam dot cz

Created attachment 32636
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32636&action=edit
reduced testcase

Compiler output:
$ gcc -Os -fno-tree-copy-prop -ftree-loop-distribute-patterns
-fno-tree-scev-cprop --param=allow-store-data-races=0 testcase.c
testcase.c: In function 'foo':
testcase.c:4:1: error: edge from 13 to 14 should be marked irreducible
 foo ()
 ^
testcase.c:4:1: error: basic block 14 should be marked irreducible
testcase.c:4:1: error: edge from 14 to 12 should be marked irreducible
testcase.c:4:1: internal compiler error: in verify_loop_structure, at
cfgloop.c:1647
0x762369 verify_loop_structure()
        /mnt/svn/gcc-trunk/gcc/cfgloop.c:1647
0xbb2c32 execute
        /mnt/svn/gcc-trunk/gcc/tree-loop-distribution.c:1821
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.

$ gcc -v
Using built-in specs.
COLLECT_GCC=/mnt/svn/gcc-trunk/binary-latest/bin/gcc
COLLECT_LTO_WRAPPER=/mnt/svn/gcc-trunk/binary-209530-lto-fortran-checking-yes-rtl-df/libexec/gcc/x86_64-unknown-linux-gnu/4.10.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-209530-lto-fortran-checking-yes-rtl-df/
--without-cloog --without-ppl
Thread model: posix
gcc version 4.10.0 20140419 (experimental) (GCC) 

Tested revisions:
r209530 - ICE
4.9 r209346 - ICE
4.8 r209342 - ICE
4.7 r209345 - OK


             reply	other threads:[~2014-04-20  8:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-20  8:59 zsojka at seznam dot cz [this message]
2014-04-22  8:49 ` [Bug tree-optimization/60903] " rguenth at gcc dot gnu.org
2014-04-23  9:17 ` rguenth at gcc dot gnu.org
2014-04-23 11:26 ` rguenth at gcc dot gnu.org
2014-04-23 11:28 ` rguenth at gcc dot gnu.org
2014-05-06  9:02 ` [Bug tree-optimization/60903] [4.8 " rguenth at gcc dot gnu.org
2014-05-06  9:02 ` 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-60903-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).