public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/sphinx] testsuite: Add extra ia32 options so that -fprefetch-loop-arrays works [PR106397]
Date: Thu, 28 Jul 2022 12:10:33 +0000 (GMT)	[thread overview]
Message-ID: <20220728121033.5A43D385AE5B@sourceware.org> (raw)

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

commit e23c73a42463fda2ca33a69d6b6af1d6b1fbc20e
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Jul 27 12:00:36 2022 +0200

    testsuite: Add extra ia32 options so that -fprefetch-loop-arrays works [PR106397]
    
    -fprefetch-loop-arrays isn't supported on ia32 with just -march=i386 and
    similar, the following patch adds extra options similar testcases use.
    
    2022-07-27  Jakub Jelinek  <jakub@redhat.com>
    
            PR tree-optimization/106397
            * gcc.dg/pr106397.c: For ia32, add dg-additional-options
            -march=i686 -msse.

Diff:
---
 gcc/testsuite/gcc.dg/pr106397.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/testsuite/gcc.dg/pr106397.c b/gcc/testsuite/gcc.dg/pr106397.c
index a6b2e913346..2bc17f8cf80 100644
--- a/gcc/testsuite/gcc.dg/pr106397.c
+++ b/gcc/testsuite/gcc.dg/pr106397.c
@@ -1,5 +1,6 @@
 /* { dg-do compile } */
 /* { dg-options "-O3 -fprefetch-loop-arrays --param l2-cache-size=0 --param prefetch-latency=3 -fprefetch-loop-arrays" } */
+/* { dg-additional-options "-march=i686 -msse" { target { { i?86-*-* x86_64-*-* } && ia32 } } } */
 
 int
 bar (void)


                 reply	other threads:[~2022-07-28 12:10 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=20220728121033.5A43D385AE5B@sourceware.org \
    --to=marxin@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).