public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r14-3657] libstdc++: Remove unnecessary dg-options and outdated comment Date: Mon, 4 Sep 2023 16:29:19 +0000 (GMT) [thread overview] Message-ID: <20230904162919.61A803856DF1@sourceware.org> (raw) https://gcc.gnu.org/g:270e702edae3e508ee91ff041d97400803eef009 commit r14-3657-g270e702edae3e508ee91ff041d97400803eef009 Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Sep 4 15:13:35 2023 +0100 libstdc++: Remove unnecessary dg-options and outdated comment It's no longer true that 1.0if has type float _Complex when GNU extensions are enabled, so remove the hardcoded -std option. libstdc++-v3/ChangeLog: * testsuite/26_numerics/complex/literals/types.cc: Remove dg-options and add target selector instead. Diff: --- libstdc++-v3/testsuite/26_numerics/complex/literals/types.cc | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/libstdc++-v3/testsuite/26_numerics/complex/literals/types.cc b/libstdc++-v3/testsuite/26_numerics/complex/literals/types.cc index 5cc46d741ef7..69c6781d7399 100644 --- a/libstdc++-v3/testsuite/26_numerics/complex/literals/types.cc +++ b/libstdc++-v3/testsuite/26_numerics/complex/literals/types.cc @@ -1,7 +1,4 @@ -// Use -std=c++14 explicitly, because -std=gnu++14 enables GNU extension for -// complex literals, so 1.0if is __complex__ float not std::complex<float>. -// { dg-options "-std=c++14" } -// { dg-do compile } +// { dg-do compile { target c++14 } } // Copyright (C) 2013-2023 Free Software Foundation, Inc. //
reply other threads:[~2023-09-04 16:29 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=20230904162919.61A803856DF1@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-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).