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++/92752] [9/10/11/12 Regression] Bogus "ignored qualifiers" warning on const-qualified pointer-to-member-function objects Date: Fri, 18 Jun 2021 18:07:22 +0000 [thread overview] Message-ID: <bug-92752-4-bJeZX14Tsw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-92752-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92752 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |10.1.0, 11.1.0, 8.4.0, | |9.3.0 Last reconfirmed| |2021-06-18 Known to work| |7.5.0 Summary|Bogus "ignored qualifiers" |[9/10/11/12 Regression] |warning on const-qualified |Bogus "ignored qualifiers" |pointer-to-member-function |warning on const-qualified |objects |pointer-to-member-function | |objects Ever confirmed|0 |1 CC| |ppalka at gcc dot gnu.org Target Milestone|--- |9.5 Status|UNCONFIRMED |NEW --- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> --- Confirmed. We started to emit the bogus warning after r8-901.
next parent reply other threads:[~2021-06-18 18:07 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-92752-4@http.gcc.gnu.org/bugzilla/> 2021-06-18 18:07 ` ppalka at gcc dot gnu.org [this message] 2022-01-21 13:44 ` rguenth at gcc dot gnu.org 2022-01-28 16:21 ` ppalka at gcc dot gnu.org 2022-01-28 20:41 ` cvs-commit at gcc dot gnu.org 2022-01-28 20:41 ` [Bug c++/92752] [9/10/11 " ppalka at gcc dot gnu.org 2022-05-27 9:41 ` [Bug c++/92752] [10/11 " rguenth at gcc dot gnu.org 2022-06-28 10:39 ` jakub at gcc dot gnu.org 2023-05-22 3:11 ` cvs-commit at gcc dot gnu.org 2023-06-30 4:04 ` [Bug c++/92752] [10 " cvs-commit at gcc dot gnu.org 2023-07-07 8:43 ` rguenth 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-92752-4-bJeZX14Tsw@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).