public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/98842] optional's spaceship operations generates wrong code when operator== is not present Date: Tue, 26 Jan 2021 22:55:55 +0000 [thread overview] Message-ID: <bug-98842-4-GqgmxEtw8t@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98842-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98842 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2021-01-26
next prev parent reply other threads:[~2021-01-26 22:55 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-26 18:09 [Bug libstdc++/98842] New: " nunoplopes at sapo dot pt 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 [this message] 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-GqgmxEtw8t@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).