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/work122)] Update ChangeLog.meissner Date: Fri, 9 Jun 2023 06:10:02 +0000 (GMT) [thread overview] Message-ID: <20230609061002.E6D6F3856962@sourceware.org> (raw) https://gcc.gnu.org/g:10017ae72ffb1c5b518de6abe4677fb9d90fbb29 commit 10017ae72ffb1c5b518de6abe4677fb9d90fbb29 Author: Michael Meissner <meissner@linux.ibm.com> Date: Fri Jun 9 02:09:59 2023 -0400 Update ChangeLog.meissner Diff: --- gcc/ChangeLog.meissner | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 055d3cd71b8..3ba4840234b 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,4 +1,4 @@ -==================== Branch work122, patch #4 ==================== +==================== Branch work122, patch #5 ==================== Fix power10 fusion and -fstack-protector, PR target/105325 @@ -11,15 +11,13 @@ There are several problems with the current GCC: 1) The constraints in fusion.md (generated by genfusion.pl) use "m" for LWA and LD, when they should use "YZ". - 2) The normal calls to address_is_non_pfx_d_or_x doesn't work with lwa, - because you need to pass in DImode instead of SImode. It is simplified - if you use the lwa_operand predicate instead of ds_form_mem_operand. + 2) The calls to address_is_non_pfx_d_or_x doesn't work with lwa using + SImode as the mode. You need to pass in DImode instead of SImode. This + is to allow lwz to be treated differently than lwa. The fix is to modify genfusion.pl that it sets the "YZ" constraint instead of -"m" for the ld and lwa instructions. - -I modified the genfusion.pl code use to use lwa_operand for the lwa instruction -to prevent prefixed addresses at combine time. +"m" for the ld and lwa instructions. And to pass DImode to the +address_is_non_pfx_d_or_x function for lwa. 2023-06-08 Michael Meissner <meissner@linux.ibm.com> @@ -33,6 +31,8 @@ gcc/testsuite/ * g++.target/powerpc/pr105325.C: New test. +==================== Branch work122, patch #4 was reverted ==================== + ==================== Branch work122, patch #3 was reverted ==================== ==================== Branch work122, patch #2 was reverted ====================
next reply other threads:[~2023-06-09 6:10 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-09 6:10 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-06-13 23:25 Michael Meissner 2023-06-13 17:23 Michael Meissner 2023-06-13 2:58 Michael Meissner 2023-06-09 21:06 Michael Meissner 2023-06-09 4:18 Michael Meissner 2023-06-09 1:33 Michael Meissner 2023-06-08 16:54 Michael Meissner 2023-06-07 20:58 Michael Meissner 2023-06-07 18:57 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=20230609061002.E6D6F3856962@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).