public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nunoplopes at sapo dot pt" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/98842] New: optional's spaceship operations generates wrong code when operator== is not present Date: Tue, 26 Jan 2021 18:09:59 +0000 [thread overview] Message-ID: <bug-98842-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98842 Bug ID: 98842 Summary: optional's spaceship operations generates wrong code when operator== is not present Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: nunoplopes at sapo dot pt Target Milestone: --- struct expr { std::strong_ordering operator<=>(const expr &rhs) const; //bool operator==(const expr &rhs) const; }; int f() { return std::is_eq(std::optional<expr>() <=> std::optional<expr>()); //return std::optional<expr>() == std::optional<expr>(); } Function f() is compiled to 0 like that. But if you uncomment the expr::operator== line, it returns 1. https://gcc.godbolt.org/z/fv85eP
next reply other threads:[~2021-01-26 18:09 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-26 18:09 nunoplopes at sapo dot pt [this message] 2021-01-26 18:56 ` [Bug libstdc++/98842] " gcc@nicholas-schwab.de 2021-01-26 21:45 ` gcc@nicholas-schwab.de 2021-01-26 22:55 ` redi at gcc dot gnu.org 2021-06-07 14:47 ` cvs-commit at gcc dot gnu.org 2021-06-11 22:25 ` cvs-commit at gcc dot gnu.org 2021-07-22 15:34 ` cvs-commit at gcc dot gnu.org 2021-07-22 15:36 ` redi at gcc dot gnu.org 2024-03-28 11:24 ` 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-98842-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: 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).