public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/97930] pair is not a structural type Date: Wed, 28 Apr 2021 17:17:47 +0000 [thread overview] Message-ID: <bug-97930-4-vE7X3Ef9W2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97930-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97930 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:c8767ee9f9355a63bfeb8318df32bc39c5b0f3ad commit r12-225-gc8767ee9f9355a63bfeb8318df32bc39c5b0f3ad Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Apr 28 18:14:05 2021 +0100 libstdc++: Add testcase for std::pair as a structural type [PR 97930] This PR was fixed by r12-221-ge1543e694dadf1ea70eb72325219bc0cdc914a35 (for compilers that support C++20 Concepts) so this adds the testcase. libstdc++-v3/ChangeLog: PR libstdc++/97930 * testsuite/20_util/pair/requirements/structural.cc: New test.
next prev parent reply other threads:[~2021-04-28 17:17 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-20 18:03 [Bug libstdc++/97930] New: " stinkingmadgod at gmail dot com 2020-11-20 20:06 ` [Bug libstdc++/97930] " redi at gcc dot gnu.org 2020-11-20 20:07 ` redi at gcc dot gnu.org 2021-04-07 10:29 ` redi at gcc dot gnu.org 2021-04-28 17:17 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-28 17:20 ` redi at gcc dot gnu.org 2021-07-28 7:04 ` rguenth at gcc dot gnu.org 2022-09-29 18:06 ` redi at gcc dot gnu.org 2023-05-29 10:03 ` jakub at gcc dot gnu.org
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=bug-97930-4-vE7X3Ef9W2@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).