public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/103051] [12 regression] new test case gcc.dg/vect/tsvc/vect-tsvc-s112.c fails in r12-4840
Date: Thu, 11 Nov 2021 18:03:27 +0000 [thread overview]
Message-ID: <bug-103051-4-iXjTdzDIYl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103051-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103051
--- Comment #10 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #9)
> All right, so something like this should work, right?
>
> diff --git a/gcc/testsuite/gcc.dg/vect/tsvc/vect-tsvc-s112.c
> b/gcc/testsuite/gcc.dg/vect/tsvc/vect-tsvc-s112.c
> index 3c6ae49f212..851b54e68b1 100644
> --- a/gcc/testsuite/gcc.dg/vect/tsvc/vect-tsvc-s112.c
> +++ b/gcc/testsuite/gcc.dg/vect/tsvc/vect-tsvc-s112.c
> @@ -36,4 +36,4 @@ int main (int argc, char **argv)
> return 0;
> }
>
> -/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 1 "vect" } } */
> \ No newline at end of file
> +/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 1 "vect" { target
> { !powerpc*-*-* || has_arch_pwr8 } } } } */
Tcl's || is short-circuiting, so that should work yes. But put that
newline where it should be. And there should be a space after the !
I think? Never sure about that (it's not Tcl, it's parsed manually
by DG, the rules are different).
next prev parent reply other threads:[~2021-11-11 18:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 21:16 [Bug testsuite/103051] New: " seurer at gcc dot gnu.org
2021-11-03 8:26 ` [Bug testsuite/103051] " rguenth at gcc dot gnu.org
2021-11-03 8:45 ` marxin at gcc dot gnu.org
2021-11-03 8:45 ` marxin at gcc dot gnu.org
2021-11-03 9:44 ` marxin at gcc dot gnu.org
2021-11-03 14:23 ` seurer at gcc dot gnu.org
2021-11-04 10:37 ` marxin at gcc dot gnu.org
2021-11-10 13:40 ` marxin at gcc dot gnu.org
2021-11-10 14:56 ` willschm at gcc dot gnu.org
2021-11-10 16:31 ` segher at gcc dot gnu.org
2021-11-10 16:38 ` segher at gcc dot gnu.org
2021-11-11 16:29 ` marxin at gcc dot gnu.org
2021-11-11 18:03 ` segher at gcc dot gnu.org [this message]
2021-11-11 18:44 ` schwab@linux-m68k.org
2021-11-12 14:24 ` cvs-commit at gcc dot gnu.org
2021-11-12 14:24 ` marxin at gcc dot gnu.org
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=bug-103051-4-iXjTdzDIYl@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).