public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Lulu Cheng <chenglulu@loongson.cn>
To: Xi Ruoyao <xry111@xry111.site>, gcc-patches@gcc.gnu.org
Cc: i@xen0n.name, xuchenghua@loongson.cn, xujiahao <xujiahao@loongson.cn>
Subject: Re: [PATCH v2] LoongArch: Add prefetch instructions.
Date: Tue, 15 Nov 2022 17:32:59 +0800	[thread overview]
Message-ID: <506be736-e5d5-f867-9167-fc011c0bc822@loongson.cn> (raw)
In-Reply-To: <7c1bd73e7e05416a9d94085aa0f1ffd63671fd9d.camel@xry111.site>


在 2022/11/15 下午5:17, Xi Ruoyao 写道:
> On Sat, 2022-11-12 at 17:45 +0800, Xi Ruoyao via Gcc-patches wrote:
>> void prefetch(char *ptr, int off)
>> {
>>          return __builtin_prefetch(ptr + off);
>> }
>>
>> It's compiled to "preldx 0,$r4,$r5".  I don't think it's correct
>> because
>> according to the doc, rk should contains several bit-fields instead of
>> an offset.
> Hi Lulu,
>
> Considering we are in stage 3 now and we can still push patches which
> have been reviewed (in the first week of stage 3), I guess we can add
> preld for GCC 13 and try preldx in the next development cycle?
>
> BTW if preldx behaves exactly as how the manual says, I think it's not
> possible to invoke it correctly in GNU C unless using inline assembly...
>
Well, I also want to add preld and instant load optimization support in 
this release.

I will send patch in the next two days:-)



      reply	other threads:[~2022-11-15  9:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-12  7:37 Lulu Cheng
2022-11-12  9:45 ` Xi Ruoyao
2022-11-15  9:17   ` Xi Ruoyao
2022-11-15  9:32     ` Lulu Cheng [this message]

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=506be736-e5d5-f867-9167-fc011c0bc822@loongson.cn \
    --to=chenglulu@loongson.cn \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=i@xen0n.name \
    --cc=xry111@xry111.site \
    --cc=xuchenghua@loongson.cn \
    --cc=xujiahao@loongson.cn \
    /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).