public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/45865] [4.6 Regression] ifcvt/crossjump failed to mark return jump
Date: Wed, 03 Nov 2010 17:07:00 -0000 [thread overview]
Message-ID: <bug-45865-4-8vSf6YiDr8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45865-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45865
--- Comment #14 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> 2010-11-03 17:07:08 UTC ---
Author: hjl
Date: Wed Nov 3 17:07:04 2010
New Revision: 166259
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=166259
Log:
Revert revision 164552.
gcc/
2010-11-03 H.J. Lu <hongjiu.lu@intel.com>
PR rtl-optimization/45865
* Makefile.in (df-problems.o): Revert revision 164552.
* basic-block.h (enum bb_flags): Likewise.
* cfgcleanup.c (block_was_dirty): Likewise.
(try_forward_edges): Likewise.
(try_crossjump_bb): Likewise.
(try_head_merge_bb): Likewise.
(try_optimize_cfg): Likewise.
(cleanup_cfg): Likewise.
* df-core.c (df_set_bb_dirty): Likewise.
* df-problems.c: Likewise.
(df_simulate_find_uses): Likewise.
(MEMREF_NORMAL, MEMREF_VOLATILE): Likewise.
(find_memory, find_memory_store): Likewise.
(can_move_insns_across): Likewise.
* df.h (can_move_insns_across): Likewise.
* ifcvt.c (find_memory): Likewise.
(dead_or_predicable): Likewise.
gcc/testsuite/
2010-11-03 H.J. Lu <hongjiu.lu@intel.com>
PR rtl-optimization/45865
* gcc.dg/pr45865.c: New.
* gcc.dg/torture/pr45865.c: Likewise.
* gcc.target/arm/headmerge-1.c: Revert revision 164552.
* gcc.target/arm/headmerge-2.c: Likewise.
* gcc.target/i386/headmerge-1.c: Likewise.
* gcc.target/i386/headmerge-2.c: Likewise.
Added:
trunk/gcc/testsuite/gcc.dg/pr45865.c
trunk/gcc/testsuite/gcc.dg/torture/pr45865.c
Removed:
trunk/gcc/testsuite/gcc.target/arm/headmerge-1.c
trunk/gcc/testsuite/gcc.target/arm/headmerge-2.c
trunk/gcc/testsuite/gcc.target/i386/headmerge-1.c
trunk/gcc/testsuite/gcc.target/i386/headmerge-2.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/Makefile.in
trunk/gcc/basic-block.h
trunk/gcc/cfgcleanup.c
trunk/gcc/df-core.c
trunk/gcc/df-problems.c
trunk/gcc/df.h
trunk/gcc/ifcvt.c
trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2010-11-03 17:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 12:02 [Bug debug/45865] New: [4.6 regression] Failed to build 403.gcc in SPEC CPU 2006 hjl.tools at gmail dot com
2010-10-02 13:06 ` [Bug debug/45865] " hjl.tools at gmail dot com
2010-10-03 0:22 ` hjl.tools at gmail dot com
2010-10-06 1:11 ` hjl.tools at gmail dot com
2010-10-06 2:50 ` hjl.tools at gmail dot com
2010-10-09 13:06 ` hjl.tools at gmail dot com
2010-10-09 22:46 ` hjl.tools at gmail dot com
2010-10-10 0:49 ` hjl.tools at gmail dot com
2010-10-10 1:12 ` hjl.tools at gmail dot com
2010-10-12 21:59 ` hjl.tools at gmail dot com
2010-10-16 17:51 ` [Bug rtl-optimization/45865] [4.6 Regression] ifcvt/crossjump failed to mark return jump hjl.tools at gmail dot com
2010-10-18 4:37 ` hjl.tools at gmail dot com
2010-10-21 17:47 ` hjl.tools at gmail dot com
2010-10-23 17:26 ` rth at gcc dot gnu.org
2010-10-26 3:54 ` jakub at gcc dot gnu.org
2010-11-03 17:07 ` hjl at gcc dot gnu.org [this message]
2010-11-05 11:53 ` hjl.tools at gmail dot com
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-45865-4-8vSf6YiDr8@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).