public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fiesh at zefix dot tv" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/95832] std::vector<bool> specialization leading std::variant ctor treating it as int rather than bool
Date: Tue, 23 Jun 2020 14:44:58 +0000	[thread overview]
Message-ID: <bug-95832-4-h1vEwLMaIU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95832-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from fiesh at zefix dot tv ---
> Not possible to backport to gcc-10, because the front end support
isn't there. That unfortunately means std::variant construction works
differently in each of gcc-9, gcc-10 and master.

Doesn't the new formulation basically revert the change for bool but not pick
bool when given a pointer?  If so, couldn't this be implemented without the
front end considering "pointer to bool" narrowing by checking if the argument
type is a pointer and, if so, not construct the bool?

  parent reply	other threads:[~2020-06-23 14:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23  4:48 [Bug libstdc++/95832] New: " fiesh at zefix dot tv
2020-06-23  5:04 ` [Bug libstdc++/95832] " fiesh at zefix dot tv
2020-06-23  6:48 ` redi at gcc dot gnu.org
2020-06-23  7:22 ` fiesh at zefix dot tv
2020-06-23  7:39 ` redi at gcc dot gnu.org
2020-06-23  9:27 ` cvs-commit at gcc dot gnu.org
2020-06-23  9:29 ` redi at gcc dot gnu.org
2020-06-23 14:44 ` fiesh at zefix dot tv [this message]
2020-06-23 15:36 ` 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-95832-4-h1vEwLMaIU@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).