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++/111250] __glibcxx_requires_subscript assertions are not checked during constant evaluation Date: Thu, 08 Feb 2024 12:33:29 +0000 [thread overview] Message-ID: <bug-111250-4-OB9KY0Tv1x@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111250-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111250 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=112314 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- Bug 112314 comment 6 has a suggestion for making __glibcxx_requires_valid_range do some checks without _GLIBCXX_DEBUG.
next prev parent reply other threads:[~2024-02-08 12:33 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-30 23:55 [Bug libstdc++/111250] New: " redi at gcc dot gnu.org 2024-01-17 11:53 ` [Bug libstdc++/111250] " redi at gcc dot gnu.org 2024-01-17 12:01 ` redi at gcc dot gnu.org 2024-02-08 12:33 ` redi at gcc dot gnu.org [this message] 2024-06-18 20:11 ` 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-111250-4-OB9KY0Tv1x@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).