public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/57320] New: Shrink-wrapping breaks graph dumping
Date: Fri, 17 May 2013 21:51:00 -0000	[thread overview]
Message-ID: <bug-57320-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 57320
           Summary: Shrink-wrapping breaks graph dumping
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: steven at gcc dot gnu.org

Compiling gcc.target/i386/pad-10.c with:

$ ./xgcc -B. -O2 -fomit-frame-pointer -march=atom pad-10.c \
 -fdump-rtl-pro_and_epilogue-graph

gives:

pad-10.c: In function 'foo2':
pad-10.c:19:1: internal compiler error: in pre_and_rev_post_order_compute, at
cfganal.c:869
 }
 ^
0x61dbaa pre_and_rev_post_order_compute(int*, int*, bool)
        ../../trunk/gcc/cfganal.c:869
0xd28d21 draw_cfg_nodes_no_loops
        ../../trunk/gcc/graph.c:183
0xd28d21 draw_cfg_nodes
        ../../trunk/gcc/graph.c:265
0xd28d21 print_graph_cfg(char const*, function*)
        ../../trunk/gcc/graph.c:306


This happens because shrink-wrapping leaves unreachable blocks
in the CFG.  For a more detailed analysis see:
http://gcc.gnu.org/ml/gcc-patches/2013-05/msg01016.html


             reply	other threads:[~2013-05-17 21:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17 21:51 steven at gcc dot gnu.org [this message]
2013-05-17 21:53 ` [Bug rtl-optimization/57320] Shrink-wrapping leaves unreachable blocks in the CFG steven at gcc dot gnu.org
2014-01-07 11:53 ` [Bug rtl-optimization/57320] [4.9 Regression] " rguenth at gcc dot gnu.org
2014-02-19 22:36 ` steven at gcc dot gnu.org
2014-03-13 19:13 ` 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-57320-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).