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: Tue, 13 Jun 2023 23:25:49 +0000 (GMT) [thread overview] Message-ID: <20230613232549.9D47F3858D38@sourceware.org> (raw) https://gcc.gnu.org/g:1eba9b607cc94a5a32cdc66d6af24816b726a49f commit 1eba9b607cc94a5a32cdc66d6af24816b726a49f Author: Michael Meissner <meissner@linux.ibm.com> Date: Tue Jun 13 19:25:46 2023 -0400 Update ChangeLog.meissner Diff: --- gcc/ChangeLog.meissner | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 50cef5a69f0..c44d1349a22 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -42,29 +42,34 @@ The solution involves: 1) Don't use ds_form_mem_operand for ld and lwa, always use non_update_memory_operand. - 2) Delete ds_form_mem_operand since it is no longer use. + 2) Delete ds_form_mem_operand since it is no longer used. 3) Use the "YZ" constraints for ld/lwa instead of "m". - 4) Insure that the insn will be recognized as having a prefixed operand - (and hence the instruction length is 16 bytes instead of 8 bytes). + 4) If we don't need to sign extend the lwa, convert it to lwz, and use + cmpwi instead of cmpdi. Adjust the insn name to reflect the code + generate. - 4a) Set the prefixed and maybe_prefix attributes to know that + 5) Insure that the insn using lwa will be recognized as having a prefixed + operand (and hence the instruction length is 16 bytes instead of 8 + bytes). + + 5a) Set the prefixed and maybe_prefix attributes to know that fused_load_cmpi are also load insns; - 4b) In the case where we are just setting CC and not using the memory + 5b) In the case where we are just setting CC and not using the memory afterward, set the clobber to use a DI register, and put an explicit sign_extend operation in the split; - 4c) Set the sign_extend attribute to "yes". + 5c) Set the sign_extend attribute to "yes". - 4d) 4a-4c are the things that prefixed_load_p in rs6000.cc checks to + 5d) 5a-5c are the things that prefixed_load_p in rs6000.cc checks to ensure that lwa is treated as a ds-form instruction and not as a d-form instruction (i.e. lwz). - 5) Add a new test case for this case. + 6) Add a new test case for this case. - 6) Adjust the insn counts in fusion-p10-ldcmpi.c. Because we are no + 7) Adjust the insn counts in fusion-p10-ldcmpi.c. Because we are no longer using ds_form_mem_operand, the ld and lwa instructions will fuse x-form (reg+reg) addresses in addition ds-form (reg+offset or reg).
next reply other threads:[~2023-06-13 23:25 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-13 23:25 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-06-13 17:23 Michael Meissner 2023-06-13 2:58 Michael Meissner 2023-06-09 21:06 Michael Meissner 2023-06-09 6:10 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=20230613232549.9D47F3858D38@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).