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/work134-vsubreg)] Allow OOmode to tie with 128-bit vector modes. Date: Thu, 21 Sep 2023 19:09:40 +0000 (GMT) [thread overview] Message-ID: <20230921190940.674FC3858D39@sourceware.org> (raw) https://gcc.gnu.org/g:14dcdd097870195fb2a1dfdfcdb4adbfb4ed5db9 commit 14dcdd097870195fb2a1dfdfcdb4adbfb4ed5db9 Author: Michael Meissner <meissner@linux.ibm.com> Date: Thu Sep 21 15:09:13 2023 -0400 Allow OOmode to tie with 128-bit vector modes. 2023-09-21 Michael Meissner <meissner@linux.ibm.com> gcc/ PR target/109116 * gcc/config/rs6000/rs6000.cc (rs6000_modes_tieable_p): Make OOmdoe tieable with 128-bit vector modes. Diff: --- gcc/config/rs6000/rs6000.cc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/gcc/config/rs6000/rs6000.cc b/gcc/config/rs6000/rs6000.cc index 4bfc62d930b..c1bce790dda 100644 --- a/gcc/config/rs6000/rs6000.cc +++ b/gcc/config/rs6000/rs6000.cc @@ -1964,13 +1964,13 @@ rs6000_hard_regno_mode_ok (unsigned int regno, machine_mode mode) static bool rs6000_modes_tieable_p (machine_mode mode1, machine_mode mode2) { - if (mode1 == PTImode || mode1 == OOmode || mode1 == XOmode - || mode2 == PTImode || mode2 == OOmode || mode2 == XOmode) + if (mode1 == PTImode || mode1 == XOmode + || mode2 == PTImode || mode2 == XOmode) return mode1 == mode2; - if (ALTIVEC_OR_VSX_VECTOR_MODE (mode1)) - return ALTIVEC_OR_VSX_VECTOR_MODE (mode2); - if (ALTIVEC_OR_VSX_VECTOR_MODE (mode2)) + if (mode1 == OOmode || ALTIVEC_OR_VSX_VECTOR_MODE (mode1)) + return (mode2 == OOmode || ALTIVEC_OR_VSX_VECTOR_MODE (mode2)); + if (mode2 == OOmode || ALTIVEC_OR_VSX_VECTOR_MODE (mode2)) return false; if (SCALAR_FLOAT_MODE_P (mode1))
reply other threads:[~2023-09-21 19:09 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=20230921190940.674FC3858D39@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).