public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103340] [12 Regression] constexpr std::string is incompatible with --enable-libstdcxx-allocator
Date: Wed, 24 Nov 2021 09:33:06 +0000	[thread overview]
Message-ID: <bug-103340-4-lVsCWrPpcM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103340-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103340

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #2)
> Making the others work isn't difficult.

HA!

Making them usable in constexpr wasn't difficult, but analysing the test
results and realising that they're completely broken was much harder, see PR
103400. And --enable-libstdcxx-allocator=bitmap had been unable to bootstrap
for years, see PR 103381.

  parent reply	other threads:[~2021-11-24  9:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-20 12:18 [Bug libstdc++/103340] New: " redi at gcc dot gnu.org
2021-11-20 12:19 ` [Bug libstdc++/103340] [12 Regression] " redi at gcc dot gnu.org
2021-11-20 16:52 ` redi at gcc dot gnu.org
2021-11-24  9:33 ` redi at gcc dot gnu.org [this message]
2021-11-24 10:00 ` redi at gcc dot gnu.org
2021-12-02 16:53 ` cvs-commit at gcc dot gnu.org
2021-12-02 17:10 ` redi 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-103340-4-lVsCWrPpcM@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: 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).