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 r11-7957] testsuite: Fix up gcc.target/i386/pr99726.c test [PR99726]
Date: Fri,  2 Apr 2021 08:09:19 +0000 (GMT)	[thread overview]
Message-ID: <20210402080919.B6562388A034@sourceware.org> (raw)

https://gcc.gnu.org/g:e53c0696113cced90561e79ade27445f6c0926d0

commit r11-7957-ge53c0696113cced90561e79ade27445f6c0926d0
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Apr 2 10:07:50 2021 +0200

    testsuite: Fix up gcc.target/i386/pr99726.c test [PR99726]
    
    -m32 shouldn't be used in gcc.target/i386/ testcases, people do
    test with -m32/-m64 to get 32-bit compilation tested.
    And, -floop-nest-optimize is a graphite optimization, so might not
    be enabled in all gcc builds.
    
    2021-04-02  Jakub Jelinek  <jakub@redhat.com>
    
            PR tree-optimization/99726
            * gcc.target/i386/pr99726.c: Remove -m32 from dg-options.  Move
            -floop-nest-optimize to dg-additional-options guarded on fgraphite
            effective target.

Diff:
---
 gcc/testsuite/gcc.target/i386/pr99726.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.target/i386/pr99726.c b/gcc/testsuite/gcc.target/i386/pr99726.c
index ff19bcabe4f..98ccce6a979 100644
--- a/gcc/testsuite/gcc.target/i386/pr99726.c
+++ b/gcc/testsuite/gcc.target/i386/pr99726.c
@@ -1,4 +1,5 @@
-/* { dg-options "-flive-patching=inline-clone -mavx512f -O2 -floop-nest-optimize -ftree-loop-vectorize -ftrapv -m32" } */
+/* { dg-options "-flive-patching=inline-clone -mavx512f -O2 -ftree-loop-vectorize -ftrapv" } */
+/* { dg-additional-options "-floop-nest-optimize" { target fgraphite } } */
 
 extern int a[256][1024];
 int b;


                 reply	other threads:[~2021-04-02  8:09 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=20210402080919.B6562388A034@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: 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).