From: "Ben Elliston" <bje@au1.ibm.com>
To: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
Cc: gcc@gcc.gnu.org
Subject: loop unswitching is sensitive to edge order
Date: Sat, 25 Sep 2004 13:22:00 -0000 [thread overview]
Message-ID: <87mzzepp13.fsf@au.ibm.com> (raw)
Hi Zdenek,
The following patch of yours seems to add some code that is sensitive
to the order of edges in the bb edge list. Am I right?
I could try and fix it myself, but I figure you know the code best.
Is it possible that you can correct it?
Thanks, Ben
2004-09-23 Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
* cfgloop.h (update_single_exits_after_duplication): Declare.
(loopify, split_loop_bb): Declaration changed.
* cfgloopmanip.c (split_loop_bb): Take void * as an argument instead
of rtx.
(loopify): Added redirect_all_edges argument.
(update_single_exits_after_duplication): Export.
* loop-unswitch.c (unswitch_loop): Changed due to loopify change.
* tree-flow.h (tree_duplicate_loop_to_header_edge,
tree_ssa_loop_version): Declare.
* tree-ssa-loop-manip.c (copy_phi_node_args, rename_variables,
set_phi_def_stmts, tree_duplicate_loop_to_header_edge,
lv_adjust_loop_header_phi, lv_adjust_loop_entry_edge,
lv_update_pending_stmts, tree_ssa_loop_version): New functions.
* tree-ssa-loop-unswitch.c: New file.
* Makefile.in (tree-ssa-loop-unswitch.o): Add.
* timevar.def (TV_TREE_LOOP_UNSWITCH): New timevar.
* tree-flow.h (tree_ssa_unswitch_loops): Declare.
* tree-optimize.c (init_tree_optimization_passes): Add pass_unswitch.
* tree-pass.h (pass_unswitch): Declare.
* tree-ssa-loop.c (tree_ssa_loop_unswitch,
gate_tree_ssa_loop_unswitch, pass_unswitch): New pass.
* doc/passes.texi: Documen tree level loop unswitching.
next reply other threads:[~2004-09-25 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-25 13:22 Ben Elliston [this message]
2004-09-25 13:40 ` Zdenek Dvorak
2004-09-25 13:47 ` Ben Elliston
2004-09-25 14:12 ` Zdenek Dvorak
2004-09-25 15:14 ` Ben Elliston
2004-09-25 14:40 ` Steven Bosscher
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=87mzzepp13.fsf@au.ibm.com \
--to=bje@au1.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=rakdver@atrey.karlin.mff.cuni.cz \
/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).