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)] Update ChangeLog.meissner Date: Fri, 15 Sep 2023 17:45:24 +0000 (GMT) [thread overview] Message-ID: <20230915174524.3D86B3858C52@sourceware.org> (raw) https://gcc.gnu.org/g:79525116f092e18371746a98f4793a53c7af6010 commit 79525116f092e18371746a98f4793a53c7af6010 Author: Michael Meissner <meissner@linux.ibm.com> Date: Fri Sep 15 13:45:21 2023 -0400 Update ChangeLog.meissner Diff: --- gcc/ChangeLog.meissner | 96 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 96 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index d36aae3dd25..ad48598b70a 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,5 +1,101 @@ +==================== Branch work134, patch #2 ==================== + +Add -mno-lxvp and -mno-stxvp. + +This patch adds the options -mno-lxvp and -mno-stxvp that control whether GCC +will generate vector pair load/stores or split the instructions into separate +vector loads/stores. These switches are not documented, but are there to allow +us to look at some places where the paired load/store instructions slow things +down. + +With this patch, GCC will not allow X-form (register + register) vector +pair loads or stores unless both lxvp and stxvp are being generated. + +I also added the lxvp and stxvp command line options to the options that the +user can enable or disable with #pragma target or attribute target. + +The default is to generate the vector pair load/store instructions. + +2023-09-15 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + * config/rs6000/mma.md (movoo): Add support for -mno-lxvp and + -mno-stxvp. + * config/rs6000/rs6000.cc (rs6000_debug_reg_global): If -mdebug=reg, + print out whether we are generating lxvp and/or stxvp instructions. + (rs6000_option_override_internal): Warn if -mlxvp or -mstxvp was used + without -mmma being set. + (rs6000_setup_reg_addr_masks structure): Add support for -mno-lxvp and + -mno-stxvp. + (rs6000_opt_vars): Add lxvp and stxvp command line options. + * config/rs6000/rs6000.md (isa attribute): Add lxvp and stxvp isa + support. + (enabled attribute): Likewise. + * config/rs6000/rs6000.opt (-mlxvp): New option. + (-mstxvp): Likewise. + +gcc/testsuite/ + + * gcc.target/powerpc/p10-lxvp-stxvp.c: New test. + +==================== Branch work134, patch #1 ==================== + +Replace UNSPEC_COPYSIGN with copysign RTL + +When I first implemented COPYSIGN support in the power7 days, we did not have a +copysign RTL insn, so I had to use UNSPEC to represent the copysign +instruction. This patch removes those UNSPECs, and it uses the native RTL +copysign insn. + +2023-09-15 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + * config/rs6000/rs6000.md (UNSPEC_COPYSIGN): Delete. + (copysign<mode>3_fcpsg): Use copysign RTL instead of UNSPEC. + (copysign<mode>3_hard): Likewise. + (copysign<mode>3_soft): Likewise. + * config/rs6000/vector.md (vector_copysign<mode>3): Use copysign RTL + instead of UNSPEC. + * config/rs6000/vsx.md (vsx_copysign<mode>3): Use copysign RTL instead + of UNSPEC. + ==================== Branch work134, baseline ==================== +Add ChangeLog.meissner and REVISION. + +2023-09-15 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + * REVISION: New file for branch. + * ChangeLog.meissner: New file. + +gcc/c-family/ + + * ChangeLog.meissner: New file. + +gcc/c/ + + * ChangeLog.meissner: New file. + +gcc/cp/ + + * ChangeLog.meissner: New file. + +gcc/fortran/ + + * ChangeLog.meissner: New file. + +gcc/testsuite/ + + * ChangeLog.meissner: New file. + +libgcc/ + + * ChangeLog.meissner: New file. + 2023-09-15 Michael Meissner <meissner@linux.ibm.com> Clone branch
reply other threads:[~2023-09-15 17:45 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=20230915174524.3D86B3858C52@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).