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/46465] New: ICE: in calc_dfs_tree, at dominance.c:394 with -Os -fno-rerun-cse-after-loop -fno-tree-ccp -fno-tree-copy-prop -fno-tree-dce
Date: Sat, 13 Nov 2010 16:29:00 -0000	[thread overview]
Message-ID: <bug-46465-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: ICE: in calc_dfs_tree, at dominance.c:394 with -Os
                    -fno-rerun-cse-after-loop -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
              Host: x86_64-pc-linux-gnu
            Target: x86_64-pc-linux-gnu


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

This happens even after fixing PR46183.

Compiler output:
$ gcc -Os -fno-rerun-cse-after-loop -fno-tree-ccp -fno-tree-copy-prop
-fno-tree-dce pr46465.c 
pr46465.c: In function 'foo':
pr46465.c:7:1: internal compiler error: in calc_dfs_tree, at dominance.c:396
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

Tested revisions:
r166703 - crash
4.5 r166509 - crash
4.4 r166509 - crash


             reply	other threads:[~2010-11-13 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-13 16:29 zsojka at seznam dot cz [this message]
2010-12-03  8:24 ` [Bug tree-optimization/46465] " zsojka at seznam dot cz
2010-12-17 20:40 ` steven 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-46465-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).