public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Michael Meissner <meissner@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/meissner/heads/work095)] Make BLOCK_OPTS options settable with ISA flags. Date: Mon, 18 Jul 2022 19:32:02 +0000 (GMT) [thread overview] Message-ID: <20220718193202.E6D593858438@sourceware.org> (raw) https://gcc.gnu.org/g:2ea1fb851857d8031d5cdc8f60cb9dfb9d473d47 commit 2ea1fb851857d8031d5cdc8f60cb9dfb9d473d47 Author: Michael Meissner <meissner@linux.ibm.com> Date: Mon Jul 18 15:31:46 2022 -0400 Make BLOCK_OPTS options settable with ISA flags. In wanting to turn off block moves from generating load and store vector pair operations on the power10, I noticed that the options for controlling the code block moves generate (OPTION_MASK_BLOCK_OPS_UNALIGNED_VSX and OPTION_MASK_BLOCK_OPS_VECTOR_PAIR) were not set in POWERPC_MASKS. It is possible in future CPUs we might want to enable these options automatically. This code moves these options to POWERPC_MASKS. 2022-07-18 Michael Meissner <meissner@linux.ibm.com> gcc/ * config/rs6000/rs6000-cpus.def (POWERPC_MASKS): Add OPTION_MASK_BLOCK_OPS_VECTOR_PAIR and OPTION_MASK_BLOCK_OPS_UNALIGNED_VSX. Diff: --- gcc/config/rs6000/rs6000-cpus.def | 2 ++ 1 file changed, 2 insertions(+) diff --git a/gcc/config/rs6000/rs6000-cpus.def b/gcc/config/rs6000/rs6000-cpus.def index c3825bcccd8..f3d2692cb86 100644 --- a/gcc/config/rs6000/rs6000-cpus.def +++ b/gcc/config/rs6000/rs6000-cpus.def @@ -122,6 +122,8 @@ /* Mask of all options to set the default isa flags based on -mcpu=<xxx>. */ #define POWERPC_MASKS (OPTION_MASK_ALTIVEC \ + | OPTION_MASK_BLOCK_OPS_VECTOR_PAIR \ + | OPTION_MASK_BLOCK_OPS_UNALIGNED_VSX \ | OPTION_MASK_CMPB \ | OPTION_MASK_CRYPTO \ | OPTION_MASK_DFP \
next reply other threads:[~2022-07-18 19:32 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-18 19:32 Michael Meissner [this message] 2022-07-19 21:20 Michael Meissner
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=20220718193202.E6D593858438@sourceware.org \ --to=meissner@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).