public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com>
To: Srinath Parvathaneni <Srinath.Parvathaneni@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	nd <nd@arm.com>,  Richard Earnshaw <Richard.Earnshaw@arm.com>,
	James Greenhalgh <James.Greenhalgh@arm.com>
Subject: Re: [PATCH 1/2][GCC][AArch64] Implement hint intrinsics for AArch64
Date: Tue, 1 Nov 2022 13:04:17 -0700	[thread overview]
Message-ID: <CA+=Sn1n3_2VF-ovOnMFqEHMkw9BHxq6Ea+zqGVUa1qR9+NbNig@mail.gmail.com> (raw)
In-Reply-To: <3b938af0-7978-2646-80d9-b39ed2d04ba1@arm.com>

On Thu, Jan 10, 2019 at 11:20 AM Srinath Parvathaneni
<Srinath.Parvathaneni@arm.com> wrote:
>
> Hi All,
>
> This patch implements the ACLE hint intrinsics (nop, yield, wfe, wfi,
> sev and sevl), for AArch64.

Hmm, this (and the corresponding arm patch) was never reviewed.
It might be useful to get an updated version which could be reviewed
and merged in for GCC 13.

Thanks,
Andrew

>
> The instructions are documented in the ArmARM[1] and the intrinsics
> specification will be
> published on the Arm website [2].
>
> [1]
> https://developer.arm.com/docs/ddi0487/latest/arm-architecture-reference-manual-armv8-for-armv8-a-architecture-profile
> [2]
> http://infocenter.arm.com/help/topic/com.arm.doc.ihi0053c/IHI0053C_acle_2_0.pdf
>
> Bootstrapped on aarch64-none-linux-gnu and regression tested on
> aarch64-none-elf with no regressions.
>
> Ok for trunk? If ok, could someone commit the patch on my behalf, I
> don't have commit rights.
>
> Thanks,
> Srinath
>
> gcc/ChangeLog:
>
> 2019-01-10  Srinath Parvathaneni  <srinath.parvathaneni@arm.com>
>
>         * config/aarch64/aarch64.md (yield): New pattern name.
>         (wfe): Likewise.
>         (wfi): Likewise.
>         (sev): Likewise.
>         (sevl): Likewise.
>         (UNSPECV_YIELD): New volatile unspec.
>         (UNSPECV_WFE): Likewise.
>         (UNSPECV_WFI): Likewise.
>         (UNSPECV_SEV): Likewise.
>         (UNSPECV_SEVL): Likewise.
>         * config/aarch64/aarch64-builtins.c (aarch64_builtins):
>         AARCH64_SYSHINTOP_BUILTIN_NOP: New builtin.
>         AARCH64_SYSHINTOP_BUILTIN_YIELD: Likewise.
>         AARCH64_SYSHINTOP_BUILTIN_WFE: Likewise.
>         AARCH64_SYSHINTOP_BUILTIN_WFI: Likewise.
>         AARCH64_SYSHINTOP_BUILTIN_SEV: Likewise.
>         AARCH64_SYSHINTOP_BUILTIN_SEVL: Likewise.
>         (aarch64_init_syshintop_builtins): New function.
>         (aarch64_init_builtins): New call statement.
>         (aarch64_expand_builtin): New case.
>         * config/aarch64/arm_acle.h (__nop ): New inline function.
>         (__yield): Likewise.
>         (__sev): Likewise.
>         (__sevl): Likewise.
>         (__wfi): Likewise.
>         (__wfe): Likewise.
>
> gcc/testsuite/ChangeLog:
>
> 2019-01-10  Srinath Parvathaneni  <srinath.parvathaneni@arm.com>
>
>         * gcc.target/aarch64/acle/hint-1.c: New test.
>         * gcc.target/aarch64/acle/hint-2.c: Likewise.
>
>
>
>
>
>

      parent reply	other threads:[~2022-11-01 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 19:20 Srinath Parvathaneni
2019-01-11 18:22 ` Sudakshina Das
2022-11-01 20:04 ` Andrew Pinski [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='CA+=Sn1n3_2VF-ovOnMFqEHMkw9BHxq6Ea+zqGVUa1qR9+NbNig@mail.gmail.com' \
    --to=pinskia@gmail.com \
    --cc=James.Greenhalgh@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=Srinath.Parvathaneni@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nd@arm.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).