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++/113529] Incorrect result of requires-expression in case of function call ambiguity and `operator<=>`
Date: Sun, 21 Jan 2024 09:03:00 +0000 [thread overview]
Message-ID: <bug-113529-4-Zpj2kE0cZf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113529-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113529
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Incorrect result of |Incorrect result of
|requires-expression in case |requires-expression in case
|of function call ambiguity |of function call ambiguity
| |and `operator<=>`
Last reconfirmed| |2024-01-21
Keywords| |wrong-code
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.
I just tried a normal function and not operator<=> and GCC does the correct
thing.
It is definitely `operator<=>` related because removing `operator<=>` and
having an ambigous `operator<` does the correct thing too.
next prev parent reply other threads:[~2024-01-21 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 8:51 [Bug c++/113529] New: Incorrect result of requires-expression in case of function call ambiguity fchelnokov at gmail dot com
2024-01-21 9:03 ` pinskia at gcc dot gnu.org [this message]
2024-01-22 18:15 ` [Bug c++/113529] Incorrect result of requires-expression in case of function call ambiguity and `operator<=>` ppalka at gcc dot gnu.org
2024-01-24 22:11 ` cvs-commit at gcc dot gnu.org
2024-01-26 14:42 ` cvs-commit at gcc dot gnu.org
2024-01-26 14:43 ` ppalka 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-113529-4-Zpj2kE0cZf@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).