From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Ajit Agarwal <aagarwa1@linux.ibm.com>
Cc: rep.dot.nop@gmail.com, gcc-patches@gcc.gnu.org,
Vineet Gupta <vineetg@rivosinc.com>,
Jeff Law <jeffreyalaw@gmail.com>,
Richard Biener <richard.guenther@gmail.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
Peter Bergner <bergner@linux.ibm.com>,
gnu-toolchain <gnu-toolchain@rivosinc.com>
Subject: Re: [PATCH v9 4/4] ree: Improve ree pass for rs6000 target using defined ABI interfaces
Date: Mon, 23 Oct 2023 16:10:27 +0200 [thread overview]
Message-ID: <20231023161027.362c626b@nbbrfq.loc> (raw)
In-Reply-To: <fdf4e055-d811-4eae-b83a-100f27dfdb61@linux.ibm.com>
On Mon, 23 Oct 2023 12:16:18 +0530
Ajit Agarwal <aagarwa1@linux.ibm.com> wrote:
> Hello All:
>
> Addressed below review comments in the version 11 of the patch.
> Please review and please let me know if its ok for trunk.
s/satisified/satisfied/
> > As said, I don't see why the below was not cleaned up before the V1 submission.
> > Iff it breaks when manually CSEing, I'm curious why?
The function below looks identical in v12 of the patch.
Why didn't you use common subexpressions?
> >
> >>> +/* Return TRUE if reg source operand of zero_extend is argument registers
> >>> + and not return registers and source and destination operand are same
> >>> + and mode of source and destination operand are not same. */
> >>> +
> >>> +static bool
> >>> +abi_extension_candidate_p (rtx_insn *insn)
> >>> +{
> >>> + rtx set = single_set (insn);
> >>> + machine_mode dst_mode = GET_MODE (SET_DEST (set));
> >>> + rtx orig_src = XEXP (SET_SRC (set), 0);
> >>> +
> >>> + if (!FUNCTION_ARG_REGNO_P (REGNO (orig_src))
> >>> + || abi_extension_candidate_return_reg_p (/*insn,*/ REGNO (orig_src)))
> >>> + return false;
> >>> +
> >>> + /* Mode of destination and source should be different. */
> >>> + if (dst_mode == GET_MODE (orig_src))
> >>> + return false;
> >>> +
> >>> + machine_mode mode = GET_MODE (XEXP (SET_SRC (set), 0));
> >>> + bool promote_p = abi_target_promote_function_mode (mode);
> >>> +
> >>> + /* REGNO of source and destination should be same if not
> >>> + promoted. */
> >>> + if (!promote_p && REGNO (SET_DEST (set)) != REGNO (orig_src))
> >>> + return false;
> >>> +
> >>> + return true;
> >>> +}
> >>> +
> >
> > As said, please also rephrase the above (and everything else if it obviously looks akin the above).
thanks
next prev parent reply other threads:[~2023-10-23 14:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 6:50 Ajit Agarwal
2023-10-20 23:56 ` Vineet Gupta
2023-10-21 10:14 ` Ajit Agarwal
2023-10-21 19:26 ` rep.dot.nop
2023-10-23 6:46 ` Ajit Agarwal
2023-10-23 14:10 ` Bernhard Reutner-Fischer [this message]
2023-10-24 7:36 ` Ajit Agarwal
2023-10-24 20:36 ` rep.dot.nop
2023-10-24 20:49 ` Vineet Gupta
2023-10-25 11:11 ` Ajit Agarwal
2023-10-27 17:16 ` Bernhard Reutner-Fischer
2023-10-27 22:39 ` Vineet Gupta
2023-10-28 10:26 ` Ajit Agarwal
2023-10-29 10:49 ` Ajit Agarwal
2023-10-28 10:25 ` Ajit Agarwal
2023-10-29 10:48 ` Ajit Agarwal
2023-10-25 11:08 ` Ajit Agarwal
2023-10-23 18:32 ` Vineet Gupta
2023-10-24 7:40 ` Ajit Agarwal
2023-10-24 9:36 ` Ajit Agarwal
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=20231023161027.362c626b@nbbrfq.loc \
--to=rep.dot.nop@gmail.com \
--cc=aagarwa1@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=jeffreyalaw@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=segher@kernel.crashing.org \
--cc=vineetg@rivosinc.com \
/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).