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

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

            Bug ID: 107015
           Summary: __debug::bitset has different ABI for -std=c++98
           Product: gcc
           Version: 12.2.1
            Status: UNCONFIRMED
          Keywords: ABI
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: redi at gcc dot gnu.org
  Target Milestone: ---

g:17e3f4aa17624af245bae5408b6e5c1fdf90c9ec and the
g:c5589aa7e1e8bf1e56d3c46d952675e1087be311 follow-up changed <debug/bitset> to
not use the debug base container in C++11 mode, because that non-literal base
class means that __debug::bitset is non-literal too.

But that means that __debug::bitset is not ABI compatible between -std=c++98
and later modes.

We should either remove the _Safe_sequence_base class unconditionally (and at
that point, we might as well just get rid of <debug/bitset> and make it an
alias for the normal one), or we should use the base unconditionally and give
up the literal class property.

The standard doesn't actually require is_literal_v<bitset<N>> to be true,
although maybe it should.

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 11:26 redi at gcc dot gnu.org [this message]
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

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@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).