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/work144-vsize)] Update ChangeLog.* Date: Fri, 17 Nov 2023 02:55:28 +0000 (GMT) [thread overview] Message-ID: <20231117025528.901DC3858D28@sourceware.org> (raw) https://gcc.gnu.org/g:079f9dcb905c526214b30fb17b66c981ed030299 commit 079f9dcb905c526214b30fb17b66c981ed030299 Author: Michael Meissner <meissner@linux.ibm.com> Date: Thu Nov 16 21:55:25 2023 -0500 Update ChangeLog.* Diff: --- gcc/ChangeLog.vsize | 41 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) diff --git a/gcc/ChangeLog.vsize b/gcc/ChangeLog.vsize index a39166a1696..c3cbc7b17a0 100644 --- a/gcc/ChangeLog.vsize +++ b/gcc/ChangeLog.vsize @@ -1,5 +1,46 @@ ==================== Branch work144-vsize, patch #411 ==================== +Add integer logical vector pair instructions + +2023-11-16 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + * config/rs6000/rs600-protos.h (vector_pair_to_vector_mode): Delete. + (rs6000_adjust_for_vector_pair): Delete. + * config/rs6000/rs6000.cc (rs6000_modes_tieable_p): Allow vector pair + modes to be tied with vector modes. + (vector_pair_to_vector_mode): Make static. Move higher. Add integer + vector pair support. + (rs6000_split_vpair_constan): Move higher. + (rs6000_expand_vector_pair_init): Add integer vector pair support. + (altivec_expand_vec_perm_le): Add support for permuting V32QImode. + (rs6000_adjust_for_vector_pair): Delete. + * config/rs6000/vector-pair.md (VPAIR): Add integer pair modes. + (VPAIR_FP): New mode iterator. + (VPAIR_FP_UNARY): Rename from VPAIR_UNARY. + (VPAIR_FP_BINARY): Rename from VPAIR_BINARY. + (VPAIR_LOGICAL): New mode iterator. + (VPAIR_LOGICAL_UNARY): New code iterator. + (VPAIR_LOGICAL_BINARY): Likewise. + (vpair_op): Add integer ops. + (VPAIR_VECTOR): Add integer vector pair modes. + (vpair_vector_l): Likewise. + (VPAIR_ELEMENT): Likewise. + (vpair_element_l): Likewise. + (floating point operations): Switch from VPAIR to VPAIR_FP. + (<vpair_op><mode>2, VPAIR_LOGICAL_UNARY iterator): New insns. + (<vpair_op><mode>3, VPAIR_LOGICAL_BINARY iterator): Likewise. + (nor<mode>3_1): New combiner insn. + (nor<mode>3_): Likewise. + (andc<mode>3): Likewise. + (eqv<mode>3): Likewise. + (nand<mode>3_1): Likewise. + (nand<mode>3_2): Likewise. + (*orc<mode>3): Likewise. + +==================== Branch work144-vsize, patch #411 ==================== + Eliminate vpair_concat_<mode>_{le,be} rtl constructor. 2023-11-16 Michael Meissner <meissner@linux.ibm.com>
next reply other threads:[~2023-11-17 2:55 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-17 2:55 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-11-17 16:23 Michael Meissner 2023-11-17 3:46 Michael Meissner 2023-11-16 22:38 Michael Meissner 2023-11-16 22:23 Michael Meissner 2023-11-16 22:02 Michael Meissner 2023-11-16 20:16 Michael Meissner 2023-11-16 17:47 Michael Meissner 2023-11-16 7:17 Michael Meissner 2023-11-16 3:15 Michael Meissner 2023-11-16 0:43 Michael Meissner 2023-11-15 19:58 Michael Meissner 2023-11-15 19:35 Michael Meissner 2023-11-15 18:35 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=20231117025528.901DC3858D28@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).