public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bernds at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/44374] Hoist same instructions in different branches
Date: Thu, 23 Sep 2010 10:05:00 -0000	[thread overview]
Message-ID: <20100923100453.16419.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44374-17659@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from bernds at gcc dot gnu dot org  2010-09-23 10:04 -------
Subject: Bug 44374

Author: bernds
Date: Thu Sep 23 10:04:33 2010
New Revision: 164552

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=164552
Log:
        PR rtl-optimization/44374
        * basic-block.h (enum bb_flags): Add BB_MODIFIED.
        * df-core.c (df_set_bb_dirty): Set it.
        * ifcvt.c (find_memory): Remove function.
        (dead_or_predicable): Use can_move_insns_across.
        * df.h (can_move_insns_across): Declare function.
        * cfgcleanup.c (block_was_dirty): New static variable.
        (try_crossjump_bb, try_forward_edges): Test BB_MODIFIED flag rather
        than df_get_bb_dirty.
        (try_head_merge_bb): New static function.
        (try_optimize_cfg): Call it.  Call df_analyze if block_was_dirty
        is set.
        * df-problems.c: Include "target.h"
        (df_simulate_find_uses): New static function.
        (MEMREF_NORMAL, MEMREF_VOLATILE): New macros.
        (find_memory, find_memory_store): New static functions.
        (can_move_insns_across): New function.
        * Makefile.in (df-problems.o): Update dependencies.

testsuite/
        PR rtl-optimization/44374
        * gcc.target/arm/headmerge-1.c: New test.
        * gcc.target/arm/headmerge-2.c: New test.
        * gcc.target/i386/headmerge-1.c: New test.
        * gcc.target/i386/headmerge-2.c: New test.

Added:
    trunk/gcc/config/i386/core2.md
    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


-- 


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


  parent reply	other threads:[~2010-09-23 10:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02  8:20 [Bug rtl-optimization/44374] New: " carrot at google dot com
2010-06-02  8:21 ` [Bug rtl-optimization/44374] " carrot at google dot com
2010-06-02  8:54 ` steven at gcc dot gnu dot org
2010-09-23 10:05 ` bernds at gcc dot gnu dot org [this message]
2010-09-23 10:08 ` bernds at gcc dot gnu dot org
     [not found] <bug-44374-4@http.gcc.gnu.org/bugzilla/>
2010-11-03 18:25 ` hjl.tools at gmail dot com
2010-12-14  0:23 ` bernds at gcc dot gnu.org
2011-04-02 13:47 ` steven at gcc dot gnu.org
2011-04-02 13:51 ` bernds 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=20100923100453.16419.qmail@sourceware.org \
    --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).