From: Segher Boessenkool <segher@kernel.crashing.org>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: Ajit Agarwal via Gcc-patches <gcc-patches@gcc.gnu.org>,
Ajit Agarwal <aagarwa1@linux.ibm.com>,
Peter Bergner <bergner@linux.ibm.com>,
Richard Biener <richard.guenther@gmail.com>,
Jeff Law <jeffreyalaw@gmail.com>
Subject: Re: [PATCH v2] rtl-optimization: ppc backend generates unnecessary extension.
Date: Thu, 30 Mar 2023 10:28:45 -0500 [thread overview]
Message-ID: <20230330152845.GP25951@gate.crashing.org> (raw)
In-Reply-To: <20230330162851.6ac61e1f@nbbrfq>
Hi!
On Thu, Mar 30, 2023 at 04:28:51PM +0200, Bernhard Reutner-Fischer wrote:
> On Thu, 30 Mar 2023 17:30:43 +0530
> Ajit Agarwal via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
> > * ree.cc(is_feasible_elim_across_basic_blocks):
>
> We often use the lispy _p suffix for predicates.
> Maybe eliminate_across_bbs_p would be shorter.
A bit shorter, but much less clear, and that is the actual reason to
keep names short -- so this misses the goal. Also, many things
currently called _p are not predicates (and/or in some cases are not
even functions!)
> > + if (use == NULL) return NULL;
>
> Missing newline before return.
And better style is
if (!use)
> > +#if 0
> > /* Get all the reaching definitions of an instruction. The definitions are
> > desired for REG used in INSN. Return the definition list or NULL if a
> > definition is missing. If DEST is non-NULL, additionally push the INSN
> > @@ -593,7 +646,7 @@ get_defs (rtx_insn *insn, rtx reg, vec<rtx_insn *> *dest)
> >
> > return ref_chain;
> > }
> > -
> > +#endif
>
> Why did you move get_defs?
And we should not normally have #if 0, too.
Segher
next prev parent reply other threads:[~2023-03-30 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 16:49 Ajit Agarwal
2023-03-30 12:00 ` Ajit Agarwal
2023-03-30 14:28 ` Bernhard Reutner-Fischer
2023-03-30 15:28 ` Segher Boessenkool [this message]
2023-03-30 13:41 ` Segher Boessenkool
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=20230330152845.GP25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=aagarwa1@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=rep.dot.nop@gmail.com \
--cc=richard.guenther@gmail.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).