public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/52424] dom prematurely pops entries from const_and_copies stack
Date: Wed, 29 Feb 2012 20:29:00 -0000	[thread overview]
Message-ID: <bug-52424-4-QOKVLNBuO1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52424-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from William J. Schmidt <wschmidt at gcc dot gnu.org> 2012-02-29 20:27:45 UTC ---
Author: wschmidt
Date: Wed Feb 29 20:27:41 2012
New Revision: 184671

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=184671
Log:
2012-02-29  Bill Schmidt  <wschmidt@linux.vnet.ibm.com>

    PR tree-optimization/52424
    * tree-ssa-dom.c (dom_opt_leave_block): Push a marker before
    calling dom_thread_across_edge.


Modified:
    branches/ibm/gcc-4_6-branch/gcc/ChangeLog.ibm
    branches/ibm/gcc-4_6-branch/gcc/tree-ssa-dom.c


  parent reply	other threads:[~2012-02-29 20:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 21:23 [Bug tree-optimization/52424] New: " wschmidt at gcc dot gnu.org
2012-02-29  3:42 ` [Bug tree-optimization/52424] " jiangning.liu at arm dot com
2012-02-29  3:54 ` jiangning.liu at arm dot com
2012-02-29  9:15 ` rguenth at gcc dot gnu.org
2012-02-29 13:09 ` wschmidt at gcc dot gnu.org
2012-02-29 13:19 ` wschmidt at gcc dot gnu.org
2012-02-29 20:28 ` wschmidt at gcc dot gnu.org
2012-02-29 20:29 ` wschmidt at gcc dot gnu.org [this message]
2012-02-29 21:00 ` pinskia at gcc dot gnu.org
2012-02-29 23:18 ` wschmidt 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-52424-4-QOKVLNBuO1@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).