public inbox for gcc-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 r10-10565] libstdc++: Fix macro checked by test Date: Tue, 26 Apr 2022 13:12:15 +0000 (GMT) [thread overview] Message-ID: <20220426131215.409D53858405@sourceware.org> (raw) https://gcc.gnu.org/g:a8f0679fadd64ff53235e12d74550160c92db080 commit r10-10565-ga8f0679fadd64ff53235e12d74550160c92db080 Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Apr 20 13:50:14 2022 +0100 libstdc++: Fix macro checked by test The macro being tested here is wrong, but just happens to have the same value as the one supposed to be tested. libstdc++-v3/ChangeLog: * testsuite/21_strings/basic_string_view/operations/copy/char/constexpr.cc: Check correct feature test macro. (cherry picked from commit 67ded3a1f5b667b4cb5eb2fee8a031e8e4060a7d) Diff: --- .../21_strings/basic_string_view/operations/copy/char/constexpr.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libstdc++-v3/testsuite/21_strings/basic_string_view/operations/copy/char/constexpr.cc b/libstdc++-v3/testsuite/21_strings/basic_string_view/operations/copy/char/constexpr.cc index 64a0766281d..731c82a029b 100644 --- a/libstdc++-v3/testsuite/21_strings/basic_string_view/operations/copy/char/constexpr.cc +++ b/libstdc++-v3/testsuite/21_strings/basic_string_view/operations/copy/char/constexpr.cc @@ -22,7 +22,7 @@ #ifndef __cpp_lib_constexpr_string_view # error "Feature test macro for constexpr copy is missing in <string_view>" -#elif __cpp_lib_constexpr_iterator < 201811L +#elif __cpp_lib_constexpr_string_view < 201811L # error "Feature test macro for constexpr copy has wrong value in <string_view>" #endif
reply other threads:[~2022-04-26 13:12 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=20220426131215.409D53858405@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).