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++/71960] __glibcxx_assert and Debug Mode checks can't be used in constexpr functions
Date: Wed, 26 Aug 2020 13:49:58 +0000 [thread overview]
Message-ID: <bug-71960-4-jQ4QhkfN32@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-71960-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71960
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:85847fd421d7760f45f0e69c7ae3607f2f898bb8
commit r10-8676-g85847fd421d7760f45f0e69c7ae3607f2f898bb8
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Aug 26 14:47:51 2020 +0100
libstdc++: Enable assertions in constexpr string_view members [PR 71960]
Since GCC 6.1 there is no reason we can't just use __glibcxx_assert in
constexpr functions in string_view. As long as the condition is true,
there will be no call to std::__replacement_assert that would make the
function ineligible for constant evaluation.
PR libstdc++/71960
* include/experimental/string_view (basic_string_view):
Enable debug assertions.
* include/std/string_view (basic_string_view):
Likewise.
(cherry picked from commit 3eefb302d2bd8502cb3d8fe44e672b11092ccaf6)
next prev parent reply other threads:[~2020-08-26 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-71960-4@http.gcc.gnu.org/bugzilla/>
2020-08-20 19:44 ` redi at gcc dot gnu.org
2020-08-26 13:49 ` cvs-commit at gcc dot gnu.org
2020-08-26 13:49 ` cvs-commit at gcc dot gnu.org [this message]
2020-08-26 13:50 ` cvs-commit at gcc dot gnu.org
2020-09-01 19:55 ` cvs-commit at gcc dot gnu.org
2020-09-11 10:52 ` cvs-commit at gcc dot gnu.org
2020-09-11 10:59 ` 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-71960-4-jQ4QhkfN32@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).