From: "Andre Vieira (lists)" <andre.simoesdiasvieira@arm.com>
To: Jakub Jelinek <jakub@redhat.com>, Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix vect-simd-clone testcase dump scanning
Date: Fri, 14 Apr 2023 11:59:02 +0100 [thread overview]
Message-ID: <aefa0f30-6e9c-b53e-22f1-cf415af62d4e@arm.com> (raw)
In-Reply-To: <ZDkqAbHL4o6lNiHG@tucnak>
On the other thread I commented that inbranch simdclones are failing for
AVX512F because it sets the mask_mode, for which inbranch hasn't been
implemented, and so it is rejected.
On 14/04/2023 11:25, Jakub Jelinek via Gcc-patches wrote:
> On Fri, Apr 14, 2023 at 10:15:06AM +0000, Richard Biener wrote:
>> Oops. Indeed target_avx checks whether it can compile sth with
>> -O2 -mavx rather than verifying avx is present. I've seen scan
>> failures with -m32/-march=cascadelake on a zen2 host. I'm not exactly
>> sure why.
>
> That is strange. Sure, -march=cascadelake implies -mavx (-mavx512f even),
> but it would surprise me if on such a host avx_runtime wasn't true.
> But we've been there before, I think cascadelake turns on the vector
> epilogues.
> In r13-6784 I've added --param vect-epilogues-nomask=0 to some testcases
> that were affected at that point, but perhaps something is affected since
> then. Will have a look.
>
> Jakub
>
next prev parent reply other threads:[~2023-04-14 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 9:42 Richard Biener
2023-04-14 9:50 ` Jakub Jelinek
2023-04-14 10:15 ` Richard Biener
2023-04-14 10:25 ` Jakub Jelinek
2023-04-14 10:59 ` Andre Vieira (lists) [this message]
2023-04-14 11:00 ` Jakub Jelinek
2023-04-14 13:38 ` Andre Vieira (lists)
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=aefa0f30-6e9c-b53e-22f1-cf415af62d4e@arm.com \
--to=andre.simoesdiasvieira@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=rguenther@suse.de \
/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).