From: Jonathan Wakely <jwakely@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [committed 2/2] libstdc++: Implement constexpr std::bitset for C++23 (P2417R2)
Date: Fri, 23 Sep 2022 00:32:23 +0100 [thread overview]
Message-ID: <CACb0b4=5g8ESbwa2gC9fJou5aq9-hYz=m40uOg4dEi8KOyNTZg@mail.gmail.com> (raw)
In-Reply-To: <20220922142353.1139862-2-jwakely@redhat.com>
On Thu, 22 Sept 2022 at 15:26, Jonathan Wakely via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> Tested x86_64-linux. Pushed to trunk.
>
> -- >8 --
>
> Also add _GLIBCXX_HOSTED checks to simplify making <bitset>
> freestanding in the near future.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/bitset (bitset): Add constexpr for C++23. Guard
> members using std::string with _GLIBCXX_HOSTED.
> * include/std/version (__cpp_lib_constexpr_bitset): Define.
> * testsuite/20_util/bitset/access/constexpr.cc: New test.
> * testsuite/20_util/bitset/cons/constexpr_c++23.cc: New test.
> * testsuite/20_util/bitset/count/constexpr.cc: New test.
> * testsuite/20_util/bitset/ext/constexpr.cc: New test.
> * testsuite/20_util/bitset/operations/constexpr_c++23.cc: New test.
> * testsuite/20_util/bitset/version.cc: New test.
The new tests fail with -D_GLIBCXX_DEBUG because I didn't update <debug/bitset>.
I'll do that tomorrow.
prev parent reply other threads:[~2022-09-22 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 14:23 [committed 1/2] libstdc++: Rearrange tests for <bitset> Jonathan Wakely
2022-09-22 14:23 ` [committed 2/2] libstdc++: Implement constexpr std::bitset for C++23 (P2417R2) Jonathan Wakely
2022-09-22 23:32 ` Jonathan Wakely [this message]
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='CACb0b4=5g8ESbwa2gC9fJou5aq9-hYz=m40uOg4dEi8KOyNTZg@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).