From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Require fgraphite effective target for pr107153.c test [PR107153]
Date: Mon, 10 Oct 2022 12:07:07 +0200 [thread overview]
Message-ID: <Y0Puy8QL8/9zgNXp@tucnak> (raw)
In-Reply-To: <20221007122659.274CA13A3D@imap2.suse-dmz.suse.de>
Hi!
On Fri, Oct 07, 2022 at 02:26:56PM +0200, Richard Biener via Gcc-patches wrote:
> * gcc.dg/autopar/pr107153.c: New testcase.
The test uses -floop-parallelize-all which emits a sorry when graphite
isn't configured in.
Tested on x86_64-linux and i686-linux, committed to trunk as obvious.
2022-10-10 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/107153
* gcc.dg/autopar/pr107153.c: Require fgraphite effective target.
--- gcc/testsuite/gcc.dg/autopar/pr107153.c.jj 2022-10-10 09:31:57.664981573 +0200
+++ gcc/testsuite/gcc.dg/autopar/pr107153.c 2022-10-10 11:59:00.365605619 +0200
@@ -1,4 +1,4 @@
-/* { dg-do compile } */
+/* { dg-do compile { target fgraphite } } */
/* { dg-options "-O1 -floop-parallelize-all -ftree-parallelize-loops=2 -fno-tree-dominator-opts" } */
void
Jakub
prev parent reply other threads:[~2022-10-10 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 12:26 [PATCH] tree-optimization/107153 - autopar SSA update issue Richard Biener
2022-10-10 10:07 ` Jakub Jelinek [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=Y0Puy8QL8/9zgNXp@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--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).