From: Lehua Ding <lehua.ding@rivai.ai>
To: gcc-patches@gcc.gnu.org
Cc: vmakarov@redhat.com, richard.sandiford@arm.com,
juzhe.zhong@rivai.ai, lehua.ding@rivai.ai
Subject: [PATCH 0/4] Add DF_LIVE_SUBREG data and apply to IRA and LRA
Date: Sat, 3 Feb 2024 18:50:08 +0800 [thread overview]
Message-ID: <20240203105012.208998-1-lehua.ding@rivai.ai> (raw)
Hi,
These patches are used to add a new data flow DF_LIVE_SUBREG,
which will track subreg liveness and then apply it to IRA and LRA
passes (enabled via -O3 or -ftrack-subreg-liveness). These patches
are for GCC 15.
These patches are separated from the subreg-coalesce patches submitted
a few months ago. I refactored the code according to comments. The next
patches will support subreg coalesce base on they. Here are some data
abot build time of SPEC INT 2017 (x86-64 target):
baseline baseline(+track-subreg-liveness)
specint2017 build time : 1892s 1883s
Regarding build times, I've run it a few times, but they all seem to take
much less time. Since the difference is small, it's possible that it's just
a change in environment. But it's theoretically possible, since supporting
subreg-liveness could have reduced the number of living regs.
For memory usage, I trided PR 69609 by valgrind, peak memory size grow from
2003910656 to 2003947520, very small increase.
For SPEC INT 2017, when using upstream GCC (whitout these patches), I get a
coredump when training the peak case, so no data yet. The cause of the core
dump still needs to be investigated.
No regression on x86-64, AArch64 and RISC-V target.
Best,
Lehua
Lehua Ding (4):
df: Add -ftrack-subreg-liveness option
df: Add DF_LIVE_SUBREG problem
ira: Apply DF_LIVE_SUBREG data
lra: Apply DF_LIVE_SUBREG data
gcc/Makefile.in | 1 +
gcc/common.opt | 4 +
gcc/df-problems.cc | 855 ++++++++++++++++++++++++++++++++++++++-
gcc/df.h | 155 +++++++
gcc/ira-build.cc | 7 +-
gcc/ira-color.cc | 8 +-
gcc/ira-emit.cc | 12 +-
gcc/ira-lives.cc | 7 +-
gcc/ira.cc | 19 +-
gcc/lra-coalesce.cc | 27 +-
gcc/lra-constraints.cc | 109 ++++-
gcc/lra-int.h | 4 +
gcc/lra-lives.cc | 355 ++++++++++++----
gcc/lra-remat.cc | 8 +-
gcc/lra-spills.cc | 27 +-
gcc/lra.cc | 10 +-
gcc/opts.cc | 1 +
gcc/regs.h | 5 +
gcc/sbitmap.cc | 98 +++++
gcc/sbitmap.h | 2 +
gcc/subreg-live-range.cc | 53 +++
gcc/subreg-live-range.h | 206 ++++++++++
gcc/timevar.def | 1 +
23 files changed, 1839 insertions(+), 135 deletions(-)
create mode 100644 gcc/subreg-live-range.cc
create mode 100644 gcc/subreg-live-range.h
--
2.36.3
next reply other threads:[~2024-02-03 10:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 10:50 Lehua Ding [this message]
2024-02-03 10:50 ` [PATCH 1/4] df: Add -ftrack-subreg-liveness option Lehua Ding
2024-02-03 10:50 ` [PATCH 2/4] df: Add DF_LIVE_SUBREG problem Lehua Ding
2024-02-03 10:50 ` [PATCH 3/4] ira: Apply DF_LIVE_SUBREG data Lehua Ding
2024-05-01 16:21 ` Vladimir Makarov
2024-02-03 10:50 ` [PATCH 4/4] lra: " Lehua Ding
2024-05-01 16:24 ` Vladimir Makarov
2024-05-08 3:01 ` Lehua Ding
2024-05-08 16:29 ` Vladimir Makarov
2024-05-08 22:16 ` 钟居哲
2024-02-05 7:01 ` [PATCH 0/4] Add DF_LIVE_SUBREG data and apply to IRA and LRA Lehua Ding
2024-02-05 16:10 ` Jeff Law
2024-02-06 1:44 ` Lehua Ding
2024-02-06 13:43 ` Vladimir Makarov
2024-02-05 18:17 ` Joseph Myers
2024-02-06 1:44 ` Lehua Ding
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=20240203105012.208998-1-lehua.ding@rivai.ai \
--to=lehua.ding@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=richard.sandiford@arm.com \
--cc=vmakarov@redhat.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).