public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-2235] Require fgraphite effective target for pr106737.c test [PR106737] Date: Sat, 27 Aug 2022 07:28:54 +0000 (GMT) [thread overview] Message-ID: <20220827072854.95792382CDD8@sourceware.org> (raw) https://gcc.gnu.org/g:4d291ca6a48eeeef3f51b8ab8452fe2166f021ee commit r13-2235-g4d291ca6a48eeeef3f51b8ab8452fe2166f021ee Author: Jakub Jelinek <jakub@redhat.com> Date: Sat Aug 27 09:28:02 2022 +0200 Require fgraphite effective target for pr106737.c test [PR106737] The test uses -floop-parallelize-all which emits a sorry when graphite isn't configured in. 2022-08-27 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/106737 * gcc.dg/autopar/pr106737.c: Require fgraphite effective target. Diff: --- gcc/testsuite/gcc.dg/autopar/pr106737.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/gcc.dg/autopar/pr106737.c b/gcc/testsuite/gcc.dg/autopar/pr106737.c index 3ec8f5dc9e8..1aa65f5c615 100644 --- a/gcc/testsuite/gcc.dg/autopar/pr106737.c +++ b/gcc/testsuite/gcc.dg/autopar/pr106737.c @@ -1,4 +1,4 @@ -/* { dg-do compile } */ +/* { dg-do compile { target fgraphite } } */ /* { dg-options "-O -floop-parallelize-all -ftree-parallelize-loops=2 -fno-tree-dce" } */ void
reply other threads:[~2022-08-27 7:28 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220827072854.95792382CDD8@sourceware.org \ --to=jakub@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).