public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/89074] valid pointer equality constexpr comparison rejected Date: Wed, 05 Jan 2022 16:38:01 +0000 [thread overview] Message-ID: <bug-89074-4-X4fQPKqcHZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89074-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89074 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ppalka at gcc dot gnu.org --- Comment #7 from Patrick Palka <ppalka at gcc dot gnu.org> --- The first three testcases are PR94716 and accepted by GCC 12. We still incorrectly reject the comment #5 testcase though.
next prev parent reply other threads:[~2022-01-05 16:38 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89074-4@http.gcc.gnu.org/bugzilla/> 2021-07-27 9:30 ` pinskia at gcc dot gnu.org 2021-11-18 14:18 ` redi at gcc dot gnu.org 2021-11-18 16:14 ` cvs-commit at gcc dot gnu.org 2022-01-05 16:38 ` ppalka at gcc dot gnu.org [this message] 2022-01-05 16:56 ` jakub at gcc dot gnu.org 2022-01-05 17:07 ` ppalka at gcc dot gnu.org 2022-01-05 19:45 ` jakub at gcc dot gnu.org 2022-01-05 19:56 ` jakub at gcc dot gnu.org 2022-01-05 22:07 ` cvs-commit at gcc dot gnu.org 2022-01-05 22:07 ` cvs-commit at gcc dot gnu.org 2022-01-06 20:01 ` jakub at gcc dot gnu.org 2022-01-08 8:54 ` cvs-commit at gcc dot gnu.org 2022-01-14 11:08 ` cvs-commit at gcc dot gnu.org 2022-01-19 8:26 ` cvs-commit at gcc dot gnu.org 2022-02-06 10:21 ` cvs-commit at gcc dot gnu.org 2022-07-07 16:38 ` cvs-commit at gcc dot gnu.org 2022-11-07 14:16 ` 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-89074-4-X4fQPKqcHZ@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).