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/work131-vpair)] Update ChangeLog.vpair Date: Wed, 16 Aug 2023 23:05:14 +0000 (GMT) [thread overview] Message-ID: <20230816230514.771BB3858C2F@sourceware.org> (raw) https://gcc.gnu.org/g:c8aa634fbd31e19d643a70bbdfdcc976547023e4 commit c8aa634fbd31e19d643a70bbdfdcc976547023e4 Author: Michael Meissner <meissner@linux.ibm.com> Date: Wed Aug 16 19:05:11 2023 -0400 Update ChangeLog.vpair Diff: --- gcc/ChangeLog.vpair | 25 ++++++++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog.vpair b/gcc/ChangeLog.vpair index f7bf15392184..5fe02b4e1c77 100644 --- a/gcc/ChangeLog.vpair +++ b/gcc/ChangeLog.vpair @@ -1,4 +1,27 @@ -==================== Branch work131-vpair, baseline ==================== +==================== Branch work131-vpair, patch #21 ==================== + +Move splitting vector pair to rs6000.cc + +2023-08-15 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + * config/rs6000/rs6000-protos.h (split_unary_vector_pair): New + declaration. + (split_binary_vector_pair): Likewise. + (split_fma_vector_pair): Likewise. + * config/rs6000/rs6000.cc (split_unary_vector_pair): New vector pair + splitter. + (split_binary_vector_pair): Likewise. + (split_fma_vector_pair): Likewise. + * config/rs6000/rvector-mode.md (vp_insn): Standard name for not is + one_cmpl. + (vp_vmode): New int attribute. + (all insns): Change to use splitter functions in rs6000.cc instead of + doing all splits in place. Fix up integer negate to use subtract for + V16QI and V8HI modes. + +==================== Branch work131-vpair, patch #21 ==================== Fix __vector_pair tests.
next reply other threads:[~2023-08-16 23:05 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-16 23:05 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-08-22 2:57 Michael Meissner 2023-08-16 3:30 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=20230816230514.771BB3858C2F@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).