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/work047)] Update ChangeLog.meissner.
Date: Tue, 13 Apr 2021 22:19:07 +0000 (GMT) [thread overview]
Message-ID: <20210413221908.03DF53951C83@sourceware.org> (raw)
https://gcc.gnu.org/g:b75435a274bcbd4d2130cbfce8f6a42fb236ca46
commit b75435a274bcbd4d2130cbfce8f6a42fb236ca46
Author: Michael Meissner <meissner@linux.ibm.com>
Date: Tue Apr 13 18:18:45 2021 -0400
Update ChangeLog.meissner.
gcc/
2021-04-13 Michael Meissner <meissner@linux.ibm.com>
* ChangeLog.meissner: Update.
Diff:
---
gcc/ChangeLog.meissner | 26 +++++++++++++++++++++++---
1 file changed, 23 insertions(+), 3 deletions(-)
diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner
index fc0a066b6db..33928740e51 100644
--- a/gcc/ChangeLog.meissner
+++ b/gcc/ChangeLog.meissner
@@ -1,10 +1,26 @@
+work047.patch019:
+2021-04-13 Michael Meissner <meissner@linux.ibm.com>
+
+ * config/rs6000/altivec.md (UNSPEC_XXBLEND): Move to vsx.md.
+ (VM3): Move to vsx.md and rename to VBLEND.
+ (VM3_char): Move to vsx.md and rename to VBLEND_char.
+ (xxblend_<mode>): Move to vsx.md.
+ * config/rs6000/vsx.md (UNSPEC_XXEVAL): Move from altivec.md.
+ (VBLEND): Move from altivec.md and rename VM3 to VBLEND.
+ (VBLEND_char): Move from altivec.md and rename VM3_char to
+ VBLEND_char.
+ (xxblend_<mode>): Move from altivec.md. Use vsx_register_operand
+ instead of register operand. Change the insn type from vecsimple
+ to vecperm.
+
work047.patch018:
2021-04-13 Michael Meissner <meissner@linux.ibm.com>
* config/rs6000/altivec.md (UNSPEC_XXEVAL): Move to vsx.md.
(xxeval): Move to vsx.md.
* config/rs6000/vsx.md (UNSPEC_XXEVAL): Move from altivec.md.
- (xxeval): Move from altivec.md.
+ (xxeval): Move from altivec.md. Change altivec_register_operand
+ to vsx_register_operand. Change insn type to vecperm.
work047.patch017:
2021-04-13 Michael Meissner <meissner@linux.ibm.com>
@@ -13,8 +29,12 @@ work047.patch017:
(xxpermx): Move to vsx.md.
(xxpermx_inst): Move to vsx.md.
* config/rs6000/vsx.md (UNSPEC_XXPERMX): Move from altivec.md.
- (xxpermx): Move from altivec.md.
- (xxpermx_inst): Move from altivec.md.
+ (xxpermx): Move from altivec.md. Use vsx_register_operand
+ instead of register_operand. Remove setting the insn attribute
+ "type" on the expander.
+ (xxpermx_inst): Move from altivec.md. Use vsx_register_operand
+ instead of register_operand. Change the constraint from "v" to
+ "wa" to match the instruction. Change insn type to vecperm.
work047.patch016:
2021-04-13 Michael Meissner <meissner@linux.ibm.com>
next reply other threads:[~2021-04-13 22:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 22:19 Michael Meissner [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-13 19:55 Michael Meissner
2021-04-13 18:07 Michael Meissner
2021-04-13 17:19 Michael Meissner
2021-04-13 16:37 Michael Meissner
2021-04-13 13:54 Michael Meissner
2021-04-13 13:37 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=20210413221908.03DF53951C83@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: 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).