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 r12-4181] libstdc++: Fix testcase for newly-implemented C++20 semantics [PR102535]
Date: Tue,  5 Oct 2021 08:36:19 +0000 (GMT)	[thread overview]
Message-ID: <20211005083619.531543857011@sourceware.org> (raw)

https://gcc.gnu.org/g:7646847df71e57edca5ec5b8c3c3dc4550dcb49d

commit r12-4181-g7646847df71e57edca5ec5b8c3c3dc4550dcb49d
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Oct 5 09:32:11 2021 +0100

    libstdc++: Fix testcase for newly-implemented C++20 semantics [PR102535]
    
    libstdc++-v3/ChangeLog:
    
            PR c++/102535
            * testsuite/20_util/is_trivially_constructible/value.cc: Adjust
            expected value for C++20.

Diff:
---
 libstdc++-v3/testsuite/20_util/is_trivially_constructible/value.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/20_util/is_trivially_constructible/value.cc b/libstdc++-v3/testsuite/20_util/is_trivially_constructible/value.cc
index 488ea7585ff..fd1fbb07ecb 100644
--- a/libstdc++-v3/testsuite/20_util/is_trivially_constructible/value.cc
+++ b/libstdc++-v3/testsuite/20_util/is_trivially_constructible/value.cc
@@ -105,7 +105,7 @@ void test01()
   static_assert(test_property<is_trivially_constructible,
 		PODType, const PODType&>(true), "");
   static_assert(test_property<is_trivially_constructible,
-		PODType, int, int>(false), "");
+		PODType, int, int>(__cplusplus >= 202002L), "");
   static_assert(test_property<is_trivially_constructible,
 		NType>(false), "");
   static_assert(test_property<is_trivially_constructible,


                 reply	other threads:[~2021-10-05  8:36 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=20211005083619.531543857011@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: 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).