public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
To: Andrew Carlotti <andrew.carlotti@arm.com>
Cc: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com,
	 Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [GCC 13 PATCH] aarch64: Remove architecture dependencies from intrinsics
Date: Wed, 19 Jul 2023 19:35:26 +0100	[thread overview]
Message-ID: <CAJA7tRZRkfLq+y2aQDNY9s87UpzNFXgk3zDh48V4y+yTWBjmpA@mail.gmail.com> (raw)
In-Reply-To: <e88fc414-c5b2-ac42-b531-dc0dd4268cff@e124511.cambridge.arm.com>

On Wed, Jul 19, 2023 at 5:44 PM Andrew Carlotti via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Updated patch to fix the fp16 intrinsic pragmas, and pushed to master.
> OK to backport to GCC 13?
>
>
> Many intrinsics currently depend on both an architecture version and a
> feature, despite the corresponding instructions being available within
> GCC at lower architecture versions.
>
> LLVM has already removed these explicit architecture version
> dependences; this patch does the same for GCC. Note that +fp16 does not
> imply +simd, so we need to add an explicit +simd for the Neon fp16
> intrinsics.
>
> Binutils did not previously support all of these architecture+feature
> combinations, but this problem is already reachable from GCC.  For
> example, compiling the test gcc.target/aarch64/usadv16qi-dotprod.c
> with -O3 -march=armv8-a+dotprod has resulted in an assembler error since
> GCC 10.  This is fixed in Binutils 2.41.

Are there any implementations that actually implement v8-a + dotprod
?. As far as I'm aware this was v8.2-A as the base architecture where
this was allowed. Has this changed recently?


regards
Ramana

  reply	other threads:[~2023-07-19 18:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 13:55 [PATCH] " Andrew Carlotti
2023-06-27  6:23 ` Richard Sandiford
2023-06-29 18:24   ` Andrew Carlotti
2023-07-19 16:44     ` [GCC 13 PATCH] " Andrew Carlotti
2023-07-19 18:35       ` Ramana Radhakrishnan [this message]
2023-07-19 23:27         ` Andrew Carlotti
2023-07-20  6:48       ` Richard Sandiford
2023-07-20  7:37         ` Richard Biener
2023-07-20  8:22           ` Andrew Carlotti

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=CAJA7tRZRkfLq+y2aQDNY9s87UpzNFXgk3zDh48V4y+yTWBjmpA@mail.gmail.com \
    --to=ramana.gcc@googlemail.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=andrew.carlotti@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.sandiford@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).