public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/101078] [9/10/11/12 Regression] Rejected code since r12-1272-gf07edb5d7f3e7721
Date: Wed, 16 Jun 2021 17:43:50 +0000 [thread overview]
Message-ID: <bug-101078-4-Oc9MJmPFln@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101078-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101078
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|11.2 |9.5
CC| |jakub at gcc dot gnu.org
Summary|[11/12 Regression] Rejected |[9/10/11/12 Regression]
|code since |Rejected code since
|r12-1272-gf07edb5d7f3e7721 |r12-1272-gf07edb5d7f3e7721
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Indeed. When the f call is in a method of B rather than of a nested class, it
works fine and when it isn't in a template too.
Extending to 9/10 too because of the B::f() case but should be kept P1 because
the f() case is a regression since 11.1.
next prev parent reply other threads:[~2021-06-16 17:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 10:17 [Bug c++/101078] New: [11/12 " marxin at gcc dot gnu.org
2021-06-15 10:17 ` [Bug c++/101078] " marxin at gcc dot gnu.org
2021-06-15 11:32 ` marxin at gcc dot gnu.org
2021-06-15 15:03 ` ppalka at gcc dot gnu.org
2021-06-16 17:43 ` jakub at gcc dot gnu.org [this message]
2021-06-16 18:19 ` [Bug c++/101078] [9/10/11/12 " jason at gcc dot gnu.org
2021-06-16 21:29 ` cvs-commit at gcc dot gnu.org
2021-06-16 21:34 ` [Bug c++/101078] [9/10/11 " jason at gcc dot gnu.org
2021-06-16 21:35 ` cvs-commit at gcc dot gnu.org
2021-06-16 21:35 ` [Bug c++/101078] [9/10 " jason at gcc dot gnu.org
2021-06-16 21:36 ` jason at gcc dot gnu.org
2022-05-13 19:53 ` cvs-commit at gcc dot gnu.org
2022-05-13 20:10 ` cvs-commit at gcc dot gnu.org
2022-05-13 20:10 ` jason 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-101078-4-Oc9MJmPFln@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).