public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/rust/master] Merge #1565
Date: Mon, 10 Oct 2022 07:33:58 +0000 (GMT)	[thread overview]
Message-ID: <20221010073358.9A2C5385829E@sourceware.org> (raw)

https://gcc.gnu.org/g:e623ee314fbc9503067bbb379a4055dd4d5d245b

commit e623ee314fbc9503067bbb379a4055dd4d5d245b
Merge: b4096017e3b 71397abfbe5
Author: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Date:   Fri Oct 7 08:00:32 2022 +0000

    Merge #1565
    
    1565: Implement data prefetch intrinsics r=CohenArthur a=CohenArthur
    
    Addresses #658
    Needs #1564 so only review the last commit
    
    This PR implements the two intrinsics related to data prefetching. I have to say, since these are hints for the backend, I am unsure if the current implementation is right. I believe it should be.
    
    Co-authored-by: Arthur Cohen <arthur.cohen@embecosm.com>

Diff:

 gcc/rust/backend/rust-builtins.cc                  |  6 ++
 gcc/rust/backend/rust-compile-intrinsic.cc         | 97 ++++++++++++++++++++--
 .../rust/execute/torture/prefetch_data.rs          | 17 ++++
 3 files changed, 111 insertions(+), 9 deletions(-)

                 reply	other threads:[~2022-10-10  7:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221010073358.9A2C5385829E@sourceware.org \
    --to=tschwinge@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: 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).