public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andysem at mail dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/98978] Consider packing _M_Engaged in the tail padding of T in optional<> Date: Fri, 05 Feb 2021 20:44:41 +0000 [thread overview] Message-ID: <bug-98978-4-C4DJFGcKqE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98978-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98978 --- Comment #3 from andysem at mail dot ru --- (In reply to Jonathan Wakely from comment #1) > This would be an ABI break, and so not going to happen. Is there no way to improve standard components implementation? I'd imagine you could provide the new implementation in the new version inline namespace and still support the old ABI for backward compatibility. (In reply to Jonathan Wakely from comment #2) > If we were going to do this, we could also make std::optional<bool> occupy a > single byte, using one bit for the value and one for the engaged flag. This would be more problematic as emplace(), value() and operator*() need to return T&, which would not be possible.
next prev parent reply other threads:[~2021-02-05 20:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-05 17:14 [Bug libstdc++/98978] New: " andysem at mail dot ru 2021-02-05 17:58 ` [Bug libstdc++/98978] " redi at gcc dot gnu.org 2021-02-05 18:00 ` redi at gcc dot gnu.org 2021-02-05 20:44 ` andysem at mail dot ru [this message] 2021-02-06 17:26 ` redi at gcc dot gnu.org 2021-08-31 16:24 ` redi at gcc dot gnu.org 2022-09-07 12:30 ` redi at gcc dot gnu.org 2022-09-18 12:27 ` andysem at mail dot ru
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-98978-4-C4DJFGcKqE@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).