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 r13-7248] testsuite: Fix up ext-floating2.C on powerpc64-linux Date: Wed, 26 Apr 2023 08:37:52 +0000 (GMT) [thread overview] Message-ID: <20230426083752.875613854157@sourceware.org> (raw) https://gcc.gnu.org/g:60e0164a371de9129ec0bfdc49a93381cf79c965 commit r13-7248-g60e0164a371de9129ec0bfdc49a93381cf79c965 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Apr 25 16:00:48 2023 +0200 testsuite: Fix up ext-floating2.C on powerpc64-linux Another testcase that is failing on powerpc64-linux. The test expects a diagnostics when float64 && float128 or in another spot when float32 && float128. Now, float128 effective target is satisfied on powerpc64-linux, despite __CPP_FLOAT128_T__ not being defined, because one needs to add some extra options for it. I think 32-bit arm has similar case for float16. 2023-04-25 Jakub Jelinek <jakub@redhat.com> * g++.dg/cpp23/ext-floating2.C: Add dg-add-options for float16, float32, float64 and float128. (cherry picked from commit 78aaaf862e70cea45f3a2be7cb855cfe1a4ead21) Diff: --- gcc/testsuite/g++.dg/cpp23/ext-floating2.C | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/gcc/testsuite/g++.dg/cpp23/ext-floating2.C b/gcc/testsuite/g++.dg/cpp23/ext-floating2.C index 41e9a54ada5..6ae5c6cd247 100644 --- a/gcc/testsuite/g++.dg/cpp23/ext-floating2.C +++ b/gcc/testsuite/g++.dg/cpp23/ext-floating2.C @@ -1,6 +1,10 @@ // P1467R9 - Extended floating-point types and standard names. // { dg-do compile { target c++23 } } // { dg-options "" } +// { dg-add-options float16 } +// { dg-add-options float32 } +// { dg-add-options float64 } +// { dg-add-options float128 } #include "ext-floating.h"
reply other threads:[~2023-04-26 8:37 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=20230426083752.875613854157@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: linkBe 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).