public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Marc Poulhi?s <dkm@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-6274] testsuite: skip gcc.target/i386/pr106910-1.c test when using newlib
Date: Thu,  7 Dec 2023 13:43:41 +0000 (GMT)	[thread overview]
Message-ID: <20231207134341.11140385E451@sourceware.org> (raw)

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

commit r14-6274-gd36cac18724a63b1dbcbe722015232c72214ce93
Author: Marc Poulhiès <poulhies@adacore.com>
Date:   Mon Nov 6 11:57:16 2023 +0100

    testsuite: skip gcc.target/i386/pr106910-1.c test when using newlib
    
    Using newlib produces a different codegen because the support for c99
    differs (see libc_has_function hook).
    
    gcc/testsuite/ChangeLog:
    
            * gcc.target/i386/pr106910-1.c: Disable for newlib.

Diff:
---
 gcc/testsuite/gcc.target/i386/pr106910-1.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/testsuite/gcc.target/i386/pr106910-1.c b/gcc/testsuite/gcc.target/i386/pr106910-1.c
index c7685a32183..13901a1fe89 100644
--- a/gcc/testsuite/gcc.target/i386/pr106910-1.c
+++ b/gcc/testsuite/gcc.target/i386/pr106910-1.c
@@ -1,4 +1,5 @@
 /* { dg-do compile { target { ! ia32 } } } */
+/* { dg-skip-if "newlib libc math causes different codegen" { newlib } } */
 /* { dg-options "-msse4.1 -O2 -Ofast" } */
 /* { dg-final { scan-assembler-times "roundps" 9 } } */
 /* { dg-final { scan-assembler-times "cvtps2dq" 1 } } */

                 reply	other threads:[~2023-12-07 13:43 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=20231207134341.11140385E451@sourceware.org \
    --to=dkm@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).