From: Segher Boessenkool <segher@kernel.crashing.org>
To: Hongtao Liu <crazylht@gmail.com>
Cc: Haochen Jiang <haochen.jiang@intel.com>,
aoliva@gcc.gnu.org, richard.sandiford@arm.com,
uweigand@de.ibm.com, linkw@gcc.gnu.org, gnu@amylaar.uk,
dje.gcc@gmail.com, olegendo@gcc.gnu.org, claziss@synopsys.com,
mfortune@gmail.com, gcc-patches@gcc.gnu.org, davem@redhat.com,
dave.anglin@bell.net, hubicka@ucw.cz, richard.earnshaw@arm.com,
rguenther@suse.de, marcus.shawcroft@arm.com,
ramana.radhakrishnan@arm.com, hongtao.liu@intel.com
Subject: Re: [PATCH 1/2] Add a parameter for the builtin function of prefetch to align with LLVM
Date: Thu, 20 Oct 2022 13:44:48 -0500 [thread overview]
Message-ID: <20221020184448.GT25951@gate.crashing.org> (raw)
In-Reply-To: <CAMZc-bxAYkovA63mD1OHVYVkMZQYbuS8cq25_4xQ9-k6WX8R5w@mail.gmail.com>
On Thu, Oct 20, 2022 at 11:12:01AM +0800, Hongtao Liu wrote:
> On Thu, Oct 20, 2022 at 9:39 AM Hongtao Liu <crazylht@gmail.com> wrote:
> > On Thu, Oct 20, 2022 at 5:08 AM Segher Boessenkool
> > > Please use a separate pattern for this, and leave prefetch to mean data
> > > prefetch, as documented! Documentation you didn't change btw. Call the
> > > new one instruction_prefetch or something equally boring maybe :-)
> Yes, Maybe we should add new rtl def named "iprefetch", so there will
> be no need to change other backend.
Spelling it out ("instruction_prefetch") is nicer. This is not used
so often to warrant a cryptic short name. But yes, that is what I am
asking for.
Segher
next prev parent reply other threads:[~2022-10-20 18:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 8:34 [PATCH 0/2] Add a Fourth parameter for prefetch and Support Intel PREFETCHI Haochen Jiang
2022-10-14 8:34 ` [PATCH 1/2] Add a parameter for the builtin function of prefetch to align with LLVM Haochen Jiang
2022-10-14 8:46 ` Hongtao Liu
2022-10-17 15:28 ` Richard Earnshaw
2022-10-18 9:20 ` [PATCH v2] " Haochen Jiang
2022-10-19 17:14 ` [PATCH 1/2] " Andrew Pinski
2022-10-19 21:14 ` Segher Boessenkool
2022-10-20 1:27 ` Hongtao Liu
2022-10-20 1:44 ` Jiang, Haochen
2022-10-20 17:25 ` Segher Boessenkool
2022-10-20 17:37 ` Andrew Pinski
2022-10-21 10:17 ` Richard Earnshaw
2022-10-21 18:08 ` Segher Boessenkool
2022-10-19 21:06 ` Segher Boessenkool
2022-10-20 1:39 ` Hongtao Liu
2022-10-20 3:12 ` Hongtao Liu
2022-10-20 18:44 ` Segher Boessenkool [this message]
2022-10-20 7:34 ` Jiang, Haochen
2022-10-20 18:54 ` Segher Boessenkool
2022-10-21 3:17 ` Jiang, Haochen
2022-10-24 10:00 ` Richard Sandiford
2022-10-24 21:19 ` Segher Boessenkool
2022-10-14 8:34 ` [PATCH 2/2] Support Intel prefetchit0/t1 Haochen Jiang
2022-10-20 3:45 ` H.J. Lu
2022-10-20 4:04 ` Hongtao Liu
2022-10-19 20:49 ` [PATCH 0/2] Add a Fourth parameter for prefetch and Support Intel PREFETCHI 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=20221020184448.GT25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=aoliva@gcc.gnu.org \
--cc=claziss@synopsys.com \
--cc=crazylht@gmail.com \
--cc=dave.anglin@bell.net \
--cc=davem@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu@amylaar.uk \
--cc=haochen.jiang@intel.com \
--cc=hongtao.liu@intel.com \
--cc=hubicka@ucw.cz \
--cc=linkw@gcc.gnu.org \
--cc=marcus.shawcroft@arm.com \
--cc=mfortune@gmail.com \
--cc=olegendo@gcc.gnu.org \
--cc=ramana.radhakrishnan@arm.com \
--cc=rguenther@suse.de \
--cc=richard.earnshaw@arm.com \
--cc=richard.sandiford@arm.com \
--cc=uweigand@de.ibm.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).