public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: [PATCH] testsuite: Require fgraphite effective target for pr106737.c test [PR106737]
Date: Sat, 27 Aug 2022 09:30:31 +0200	[thread overview]
Message-ID: <YwnIF5Fo6LkAHPfJ@tucnak> (raw)
In-Reply-To: <20220825084433.2681813517@imap2.suse-dmz.suse.de>

On Thu, Aug 25, 2022 at 10:44:32AM +0200, Richard Biener via Gcc-patches wrote:
> 	* gcc.dg/autopar/pr106737.c: New testcase.

The test uses -floop-parallelize-all which emits a sorry when graphite
isn't configured in.

Fixed thusly, tested on x86_64-linux (where it PASSed for me before and
keeps PASSing) and on i686-linux (where it FAILed and now is UNSUPPORTED
as I don't have 32-bit libisl installed), committed to trunk as obvious.

2022-08-27  Jakub Jelinek  <jakub@redhat.com>

	PR tree-optimization/106737
	* gcc.dg/autopar/pr106737.c: Require fgraphite effective target.

--- gcc/testsuite/gcc.dg/autopar/pr106737.c.jj	2022-08-25 20:34:49.333893224 +0200
+++ gcc/testsuite/gcc.dg/autopar/pr106737.c	2022-08-27 09:22:07.141807077 +0200
@@ -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

	Jakub


      reply	other threads:[~2022-08-27  7:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25  8:44 [PATCH] tree-optimization/106737 - remove intermediate SSA verification in autopar Richard Biener
2022-08-27  7:30 ` 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=YwnIF5Fo6LkAHPfJ@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).