From: Andrew Stubbs <ams@codesourcery.com>
To: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 2/3] amdgcn: OpenMP SIMD routine support
Date: Tue, 30 Aug 2022 15:53:56 +0100 [thread overview]
Message-ID: <a47936a1-f754-6130-24db-70246e087e8e@codesourcery.com> (raw)
In-Reply-To: <ce4e830f2bd38454020309a366d4e09abe12290f.1660051134.git.ams@codesourcery.com>
On 09/08/2022 14:23, Andrew Stubbs wrote:
>
> Enable and configure SIMD clones for amdgcn. This affects both the __simd__
> function attribute, and the OpenMP "declare simd" directive.
>
> Note that the masked SIMD variants are generated, but the middle end doesn't
> actually support calling them yet.
>
> gcc/ChangeLog:
>
> * config/gcn/gcn.cc (gcn_simd_clone_compute_vecsize_and_simdlen): New.
> (gcn_simd_clone_adjust): New.
> (gcn_simd_clone_usable): New.
> (TARGET_SIMD_CLONE_ADJUST): New.
> (TARGET_SIMD_CLONE_COMPUTE_VECSIZE_AND_SIMDLEN): New.
> (TARGET_SIMD_CLONE_USABLE): New.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.dg/vect/vect-simd-clone-1.c: Add dg-warning.
> * gcc.dg/vect/vect-simd-clone-2.c: Add dg-warning.
> * gcc.dg/vect/vect-simd-clone-3.c: Add dg-warning.
> * gcc.dg/vect/vect-simd-clone-4.c: Add dg-warning.
> * gcc.dg/vect/vect-simd-clone-5.c: Add dg-warning.
> * gcc.dg/vect/vect-simd-clone-8.c: Add dg-warning.
The dependency was approved, so this is now committed.
Andrew
next prev parent reply other threads:[~2022-08-30 14:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 13:23 [PATCH 0/3] OpenMP SIMD routines Andrew Stubbs
2022-08-09 13:23 ` [PATCH 1/3] omp-simd-clone: Allow fixed-lane vectors Andrew Stubbs
2022-08-26 11:04 ` Jakub Jelinek
2022-08-30 14:52 ` Andrew Stubbs
2022-08-30 16:54 ` Rainer Orth
2022-08-31 7:11 ` Martin Liška
2022-08-31 8:29 ` Jakub Jelinek
2022-08-31 8:35 ` Andrew Stubbs
2022-08-09 13:23 ` [PATCH 2/3] amdgcn: OpenMP SIMD routine support Andrew Stubbs
2022-08-30 14:53 ` Andrew Stubbs [this message]
2022-08-09 13:23 ` [PATCH 3/3] vect: inbranch SIMD clones Andrew Stubbs
2022-09-09 14:31 ` Jakub Jelinek
2022-09-14 8:09 ` Richard Biener
2022-09-14 8:34 ` Jakub Jelinek
2022-11-30 15:17 ` Andrew Stubbs
2022-11-30 15:37 ` Jakub Jelinek
2022-12-01 13:35 ` Andrew Stubbs
2022-12-01 14:16 ` Jakub Jelinek
2023-01-06 12:20 ` Andrew Stubbs
2023-02-10 9:11 ` Jakub Jelinek
2023-02-23 10:02 ` Andrew Stubbs
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=a47936a1-f754-6130-24db-70246e087e8e@codesourcery.com \
--to=ams@codesourcery.com \
--cc=gcc-patches@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).