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/46165] New: ICE: verify_flow_info failed when casting-out attribute noreturn with -fno-tree-ccp -fno-tree-copy-prop -fno-tree-dce
Date: Mon, 25 Oct 2010 16:45:00 -0000	[thread overview]
Message-ID: <bug-46165-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: ICE: verify_flow_info failed when casting-out
                    attribute noreturn with -fno-tree-ccp
                    -fno-tree-copy-prop -fno-tree-dce
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: zsojka@seznam.cz


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

Compiler output:
$ gcc -O -fno-tree-ccp -fno-tree-copy-prop -fno-tree-dce pr46165.c 
pr46165.c: In function 'g':
pr46165.c:2:6: error: control flow in the middle of basic block 2
pr46165.c:2:6: internal compiler error: verify_flow_info failed
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

Tested revisions:
r165915 - crash
4.5 r165781 - crash
4.4 r165754 - crash
4.4 r149995 - crash


             reply	other threads:[~2010-10-25 16:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-25 16:45 zsojka at seznam dot cz [this message]
2010-10-25 17:48 ` [Bug tree-optimization/46165] [4.3/4.4/4.5/4.6 Regression] " hjl.tools at gmail dot com
2010-10-25 20:20 ` hjl.tools at gmail dot com
2010-10-26 14:05 ` rguenth at gcc dot gnu.org
2010-11-02 13:54 ` jakub at gcc dot gnu.org
2010-11-03 10:34 ` jakub at gcc dot gnu.org
2010-11-03 10:35 ` [Bug tree-optimization/46165] [4.3/4.4/4.5 " jakub at gcc dot gnu.org
2010-11-11 20:35 ` jakub at gcc dot gnu.org
2010-11-12  9:25 ` [Bug tree-optimization/46165] [4.3/4.4 " jakub at gcc dot gnu.org
2010-11-12 10:26 ` zsojka at seznam dot cz
2010-11-12 13:50 ` jakub at gcc dot gnu.org
2010-11-12 14:45 ` zsojka at seznam dot cz
2010-11-15 21:36 ` zsojka at seznam dot cz
2010-11-15 22:53 ` rguenth at gcc dot gnu.org
2010-11-16  1:33 ` zsojka at seznam dot cz
2011-06-27 10:38 ` rguenth at gcc dot gnu.org
2011-06-27 15:08 ` rguenth at gcc dot gnu.org
2012-03-13 17:13 ` [Bug tree-optimization/46165] [4.4 " jakub 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-46165-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).