From: "Marc Poulhiès" <poulhies@adacore.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, Mike Stump <mikestump@comcast.net>,
Andrew Stubbs <ams@codesourcery.com>,
Julian Brown <julian@codesourcery.com>,
Richard Biener <rguenther@suse.de>
Subject: Re: [PATCH] testsuite: require avx_runtime for some tests
Date: Fri, 08 Dec 2023 10:08:46 +0100 [thread overview]
Message-ID: <87r0jx3vpr.fsf@adacore.com> (raw)
In-Reply-To: <87y1e5rrj9.fsf@euler.schwinge.homeip.net>
Thomas Schwinge <thomas@codesourcery.com> writes:
> Hi Marc!
>
> On 2023-11-06T11:59:18+0100, Marc Poulhiès <poulhies@adacore.com> wrote:
>> These 3 tests fails parsing the 'vect' dump when not using -mavx. Make
>> the dependency explicit.
>
> But that means that the tests are now enabled *only* for
> effective-target 'avx_runtime', so, for example, on GCN I see:
>
> -PASS: gcc.dg/vect/vect-ifcvt-18.c (test for excess errors)
> -PASS: gcc.dg/vect/vect-ifcvt-18.c execution test
> +UNSUPPORTED: gcc.dg/vect/vect-ifcvt-18.c
>
> -PASS: gcc.dg/vect/vect-simd-clone-16f.c (test for excess errors)
> -PASS: gcc.dg/vect/vect-simd-clone-16f.c execution test
> -PASS: gcc.dg/vect/vect-simd-clone-16f.c scan-tree-dump-times vect "[\\n\\r] [^\\n]* = foo\\.simdclone" 2
> +UNSUPPORTED: gcc.dg/vect/vect-simd-clone-16f.c
>
> -PASS: gcc.dg/vect/vect-simd-clone-18f.c (test for excess errors)
> -PASS: gcc.dg/vect/vect-simd-clone-18f.c execution test
> -PASS: gcc.dg/vect/vect-simd-clone-18f.c scan-tree-dump-times vect "[\\n\\r] [^\\n]* = foo\\.simdclone" 2
> +UNSUPPORTED: gcc.dg/vect/vect-simd-clone-18f.c
>
> ..., which was not the intention, I suppose?
Hello Thomas,
No, that was an oversight, Jakub also spotted that in another patch.
I'll revert it now.
Sorry for the inconvenience,
Marc
prev parent reply other threads:[~2023-12-08 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 10:59 Marc Poulhiès
2023-12-01 16:23 ` Marc Poulhiès
2023-12-01 17:35 ` Mike Stump
2023-12-08 9:07 ` Thomas Schwinge
2023-12-08 9:08 ` Marc Poulhiès [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=87r0jx3vpr.fsf@adacore.com \
--to=poulhies@adacore.com \
--cc=ams@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=julian@codesourcery.com \
--cc=mikestump@comcast.net \
--cc=rguenther@suse.de \
--cc=thomas@codesourcery.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).