public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/89793] Implicit conversion to std::string is ambiguous on GCC 8.2 but not GCC 7.3
Date: Sun, 09 Jul 2023 22:57:12 +0000	[thread overview]
Message-ID: <bug-89793-4-tnp0Tmo5Z2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-89793-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |needs-bisection,
                   |                            |rejects-valid

--- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I suspect r9-6526-gdcfa8518868d9e (r8-10080-g32988aac5be4fa4728 on the branch)
fixed this .

       reply	other threads:[~2023-07-09 22:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-89793-4@http.gcc.gnu.org/bugzilla/>
2023-07-09 22:57 ` pinskia at gcc dot gnu.org [this message]
2023-07-11 12:06 ` 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-89793-4-tnp0Tmo5Z2@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).