public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davidxl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/39557]  New: Invalid PDOM lead to infinite loop to be generated
Date: Wed, 25 Mar 2009 23:09:00 -0000	[thread overview]
Message-ID: <bug-39557-16184@http.gcc.gnu.org/bugzilla/> (raw)

Compiling the attached source with the following options

 -Wall -fno-exceptions -O2 -fprofile-use=/blah  -fno-rtti 

will result in a code with infinite loop.

In DCE, special code is added to handle dead loops conservatively. However this
requires PDOM information (control dep info) to be valid. The PDOM is created
in unintialized variable warning, but gets invalidated before cddce pass (the
incremental update does not work well). With the wrong CD info, DCE pass tries
to eliminate the loop, but the exit edge fixup code ends up linking the
precessor not to its post-dom bb, but to itself -- leading to infinite loop.

A proposed patch will be posted to gcc-patches.

David


-- 
           Summary: Invalid PDOM lead to infinite loop to be generated
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: davidxl at gcc dot gnu dot org


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


             reply	other threads:[~2009-03-25 23:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 23:09 davidxl at gcc dot gnu dot org [this message]
2009-03-25 23:10 ` [Bug tree-optimization/39557] " davidxl at gcc dot gnu dot org
2009-03-27 18:26 ` davidxl at gcc dot gnu dot org
2009-03-27 20:21 ` rguenth at gcc dot gnu dot 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-39557-16184@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).