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++/103191] vector<bool> doesn't have any checks enabled by _GLIBCXX_ASSERTIONS Date: Thu, 27 Jun 2024 08:42:16 +0000 [thread overview] Message-ID: <bug-103191-4-6GO5SeIsnP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103191-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103191 --- Comment #1 from GCC 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:8fd84bc009b3073666a24047c78a04c19eeab752 commit r15-1689-g8fd84bc009b3073666a24047c78a04c19eeab752 Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Jun 18 10:57:45 2024 +0100 libstdc++: Add debug assertions to std::vector<bool> [PR103191] This adds debug assertions for std::vector<bool> element access. libstdc++-v3/ChangeLog: PR libstdc++/103191 * include/bits/stl_bvector.h (vector<bool>::operator[]) (vector<bool>::front, vector<bool>::back): Add debug assertions. * testsuite/23_containers/vector/bool/element_access/constexpr.cc: Remove dg-error that no longer triggers.
next prev parent reply other threads:[~2024-06-27 8:42 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-11 14:04 [Bug libstdc++/103191] New: " redi at gcc dot gnu.org 2024-02-08 12:29 ` [Bug libstdc++/103191] " redi at gcc dot gnu.org 2024-06-18 20:12 ` redi at gcc dot gnu.org 2024-06-27 8:42 ` cvs-commit at gcc dot gnu.org [this message] 2024-06-27 9:04 ` 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-103191-4-6GO5SeIsnP@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).