From: Xionghu Luo <luoxhu@linux.ibm.com>
To: gcc-patches@gcc.gnu.org
Cc: segher@kernel.crashing.org, dje.gcc@gmail.com,
wschmidt@linux.ibm.com, guojiufu@linux.ibm.com,
linkw@gcc.gnu.org, rguenther@suse.de, hubicka@kam.mff.cuni.cz,
Xionghu Luo <luoxhu@linux.ibm.com>
Subject: [PATCH v2 0/4] loop split fix and functions renaming
Date: Wed, 27 Oct 2021 01:34:44 -0500 [thread overview]
Message-ID: <20211027063448.1844771-1-luoxhu@linux.ibm.com> (raw)
This patchset is an followed update from [1].
Patch 1 is expecting review comments from Honza[2];
Patch 2 refactors loop_version to remove loopify call and adjust
condition generation later than loopify;
Patch 3 and Patch 4 are function renamings to help better understanding.
[1] https://gcc.gnu.org/pipermail/gcc-patches/2021-October/582600.html
[2] https://gcc.gnu.org/pipermail/gcc-patches/2021-October/582607.html
Xionghu Luo (4):
Fix loop split incorrect count and probability
Refactor loop_version
Rename loop_version to clone_loop_to_header_edge.
Rename duplicate_loop_to_header_edge to duplicate_loop_body_to_header_edge
gcc/cfghooks.c | 27 +++----
gcc/cfghooks.h | 13 ++-
gcc/cfgloopmanip.c | 144 +++++++++++-----------------------
gcc/cfgloopmanip.h | 17 ++--
gcc/cfgrtl.c | 2 +-
gcc/doc/loop.texi | 4 +-
gcc/gimple-loop-versioning.cc | 11 +--
gcc/loop-unroll.c | 27 +++----
gcc/modulo-sched.c | 6 +-
gcc/tree-cfg.c | 2 +-
gcc/tree-if-conv.c | 13 +--
gcc/tree-loop-distribution.c | 4 +-
gcc/tree-parloops.c | 10 +--
gcc/tree-ssa-loop-ivcanon.c | 4 +-
gcc/tree-ssa-loop-manip.c | 31 ++++----
gcc/tree-ssa-loop-manip.h | 7 +-
gcc/tree-ssa-loop-split.c | 39 +++++----
gcc/tree-ssa-loop-unswitch.c | 8 +-
gcc/tree-vect-loop-manip.c | 5 +-
19 files changed, 159 insertions(+), 215 deletions(-)
--
2.27.0.90.geebb51ba8c
next reply other threads:[~2021-10-27 6:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 6:34 Xionghu Luo [this message]
2021-10-27 6:34 ` [PATCH v2 1/4] Fix loop split incorrect count and probability Xionghu Luo
2021-10-27 7:07 ` Jan Hubicka
2021-10-27 7:23 ` Jan Hubicka
2021-10-27 7:29 ` Richard Biener
2021-10-27 7:44 ` Jan Hubicka
2021-11-08 6:09 ` [PATCH v3 " Xionghu Luo
2021-11-24 5:11 ` Xionghu Luo
2021-10-27 6:34 ` [PATCH v2 2/4] Refactor loop_version Xionghu Luo
2021-10-29 11:52 ` Richard Biener
2021-11-01 5:28 ` Xionghu Luo
2021-10-27 6:34 ` [PATCH v2 3/4] Rename loop_version to clone_loop_to_header_edge Xionghu Luo
2021-11-03 13:36 ` Richard Biener
2021-10-27 6:34 ` [PATCH v2 4/4] Rename duplicate_loop_to_header_edge to duplicate_loop_body_to_header_edge Xionghu Luo
2021-10-29 11:50 ` Richard Biener
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=20211027063448.1844771-1-luoxhu@linux.ibm.com \
--to=luoxhu@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=guojiufu@linux.ibm.com \
--cc=hubicka@kam.mff.cuni.cz \
--cc=linkw@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.ibm.com \
/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).