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-9512] testsuite: Fix up pr104188.c testcase for i686-linux [PR104188]
Date: Wed, 26 Jan 2022 11:07:56 +0000 (GMT)	[thread overview]
Message-ID: <20220126110756.B9A9C38515DA@sourceware.org> (raw)

https://gcc.gnu.org/g:44d28c67b484fe3be7b693108fc03cbe6aa05329

commit r11-9512-g44d28c67b484fe3be7b693108fc03cbe6aa05329
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Jan 26 11:58:27 2022 +0100

    testsuite: Fix up pr104188.c testcase for i686-linux [PR104188]
    
    On i686-linux this new testcase FAILs with:
    cc1: warning: SSE instruction set disabled, using 387 arithmetics
    FAIL: gcc.target/i386/pr104188.c (test for excess errors)
    Excess errors:
    cc1: warning: SSE instruction set disabled, using 387 arithmetics
    This is because it uses -mfpmath=sse, but -msse2 isn't on.  Fixed
    by adding -msse2 to dg-options and requiring sse2_runtime effective
    target.
    
    2022-01-26  Jakub Jelinek  <jakub@redhat.com>
    
            PR target/104188
            * gcc.target/i386/pr104188.c: Add dg-require-effective-target
            sse2_runtime.  Add -msse2 to dg-options.
    
    (cherry picked from commit 192e4a9fa0880ef153631d5b0de864bc4bbb6a91)

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

diff --git a/gcc/testsuite/gcc.target/i386/pr104188.c b/gcc/testsuite/gcc.target/i386/pr104188.c
index c6f615b9625..3ddd3bc79b9 100644
--- a/gcc/testsuite/gcc.target/i386/pr104188.c
+++ b/gcc/testsuite/gcc.target/i386/pr104188.c
@@ -1,5 +1,6 @@
 /* { dg-do run { target avx512f } } */
-/* { dg-options "-O2 -mfpmath=sse" } */
+/* { dg-require-effective-target sse2_runtime } */
+/* { dg-options "-O2 -msse2 -mfpmath=sse" } */
 
 #include <x86intrin.h>


                 reply	other threads:[~2022-01-26 11:07 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=20220126110756.B9A9C38515DA@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).