public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99493] Address of template parameter object is not a valid template argument
Date: Wed, 17 Jan 2024 18:02:03 +0000 [thread overview]
Message-ID: <bug-99493-4-u1S8MUWBFu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99493-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99493
--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>:
https://gcc.gnu.org/g:68cea2d32a9fd525154b6a48042e5835d4c5e371
commit r14-8189-g68cea2d32a9fd525154b6a48042e5835d4c5e371
Author: Patrick Palka <ppalka@redhat.com>
Date: Wed Jan 17 13:01:01 2024 -0500
c++: address of class NTTP object as targ [PR113242]
invalid_tparm_referent_p was rejecting using the address of a class NTTP
object as a template argument, but this should be fine.
PR c++/113242
PR c++/99493
gcc/cp/ChangeLog:
* pt.cc (invalid_tparm_referent_p) <case ADDR_EXPR>: Suppress
DECL_ARTIFICIAL rejection test for class NTTP objects.
gcc/testsuite/ChangeLog:
* g++.dg/cpp2a/nontype-class61.C: New test.
* g++.dg/cpp2a/nontype-class62.C: New test.
Reviewed-by: Jason Merrill <jason@redhat.com>
next prev parent reply other threads:[~2024-01-17 18:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 18:20 [Bug c++/99493] New: " johelegp at gmail dot com
2021-03-15 5:02 ` [Bug c++/99493] " johelegp at gmail dot com
2021-03-15 18:44 ` johelegp at gmail dot com
2022-01-19 2:43 ` pinskia at gcc dot gnu.org
2022-01-19 2:46 ` pinskia at gcc dot gnu.org
2024-01-17 18:02 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-18 15:53 ` cvs-commit at gcc dot gnu.org
2024-01-18 15:54 ` ppalka at gcc dot gnu.org
2024-01-18 15:55 ` johelegp at gmail dot com
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-99493-4-u1S8MUWBFu@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).