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++/107015] __debug::bitset has different ABI for -std=c++98
Date: Fri, 23 Sep 2022 11:33:27 +0000	[thread overview]
Message-ID: <bug-107015-4-wb7XW9k95q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107015-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
And we don't even do that check for the const overload, even in debug mode!

      // _GLIBCXX_RESOLVE_LIB_DEFECTS
      // 11. Bitset minor problems
      _GLIBCXX_CONSTEXPR bool
      operator[](size_t __pos) const
      {
#if __cplusplus < 201103L
        // TODO: Check in debug-mode too.
        __glibcxx_check_subscript(__pos);
#endif
        return _Base::operator[](__pos);
      }

I think we should just scrap <debug/bitset>.

      parent reply	other threads:[~2022-09-23 11:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 11:26 [Bug libstdc++/107015] New: " redi at gcc dot gnu.org
2022-09-23 11:32 ` [Bug libstdc++/107015] " redi at gcc dot gnu.org
2022-09-23 11:33 ` redi at gcc dot gnu.org [this message]

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-107015-4-wb7XW9k95q@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).