public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/112882] [14 Regression] std::clamp no longer usable in header only mode
Date: Thu, 07 Dec 2023 08:23:19 +0000 [thread overview]
Message-ID: <bug-112882-4-foScOp0KuH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112882-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112882
--- Comment #4 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Awesome! Thanks for taking a look!
> > It seems that undefining `_GLIBCXX_VERBOSE_ASSERT` gets it to go to
> > `__builtin_abort()` which makes it work again.
> >
> > If this change was intentional, would it be possible to make
> > `_GLIBCXX_VERBOSE_ASSERT` user configurable?
>
> You can use --disable-libstdcxx-verbose for that, or do you need to control
> it during preprocessing?
Yeah I meant during preprocessing, we distribute the library as source to
client too, so would be harder if they'd also need to recompile the toolchain
:)
Thanks for the fixes!
next prev parent reply other threads:[~2023-12-07 8:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 15:20 [Bug libstdc++/112882] New: " tnfchris at gcc dot gnu.org
2023-12-06 16:47 ` [Bug libstdc++/112882] " redi at gcc dot gnu.org
2023-12-06 16:55 ` redi at gcc dot gnu.org
2023-12-06 17:07 ` redi at gcc dot gnu.org
2023-12-06 17:09 ` redi at gcc dot gnu.org
2023-12-06 17:20 ` redi at gcc dot gnu.org
2023-12-07 8:23 ` tnfchris at gcc dot gnu.org [this message]
2023-12-07 9:49 ` redi at gcc dot gnu.org
2023-12-07 20:55 ` cvs-commit at gcc dot gnu.org
2023-12-07 21:03 ` 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-112882-4-foScOp0KuH@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).