From: Jeff Law <jlaw@ventanamicro.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [committed][RISC-V] Turn on overlap_op_by_pieces for generic-ooo tuning
Date: Tue, 7 May 2024 15:36:19 -0600 [thread overview]
Message-ID: <4ecd66d9-8f83-4312-8e6c-11afec683b4f@ventanamicro.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 88 bytes --]
Per quick email exchange with Palmer. Given the triviality, I'm just
pushing it.
jeff
[-- Attachment #2: P --]
[-- Type: text/plain, Size: 977 bytes --]
commit 9f14f1978260148d4d6208dfd73df1858e623758
Author: Jeff Law <jlaw@ventanamicro.com>
Date: Tue May 7 15:34:16 2024 -0600
[committed][RISC-V] Turn on overlap_op_by_pieces for generic-ooo tuning
Per quick email exchange with Palmer. Given the triviality, I'm just pushing
it.
gcc/
* config/riscv/riscv.cc (generic_ooo_tune_info): Turn on
overlap_op_by_pieces.
diff --git a/gcc/config/riscv/riscv.cc b/gcc/config/riscv/riscv.cc
index a9b57d41184..62207b6b227 100644
--- a/gcc/config/riscv/riscv.cc
+++ b/gcc/config/riscv/riscv.cc
@@ -536,7 +536,7 @@ static const struct riscv_tune_param generic_ooo_tune_info = {
4, /* fmv_cost */
false, /* slow_unaligned_access */
false, /* use_divmod_expansion */
- false, /* overlap_op_by_pieces */
+ true, /* overlap_op_by_pieces */
RISCV_FUSE_NOTHING, /* fusible_ops */
&generic_vector_cost, /* vector cost */
};
reply other threads:[~2024-05-07 21:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4ecd66d9-8f83-4312-8e6c-11afec683b4f@ventanamicro.com \
--to=jlaw@ventanamicro.com \
--cc=gcc-patches@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).