From: Jakub Jelinek <jakub@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: [PATCH] c++: Add testcase for DR 2392
Date: Sun, 13 Nov 2022 22:36:03 -1200 [thread overview]
Message-ID: <Y3IaE4OIQGHhvhXv@tucnak> (raw)
Hi!
Working virtually out of Baker Island.
The testcase from DR 2392 passes, so I assume we don't need to do
anything further for the DR.
Tested on x86_64-linux, ok for trunk?
2022-11-13 Jakub Jelinek <jakub@redhat.com>
* g++.dg/DRs/dr2392.C: Add testcase for DR 2392.
--- gcc/testsuite/g++.dg/DRs/dr2392.C.jj 2022-11-13 20:49:22.107817793 -1200
+++ gcc/testsuite/g++.dg/DRs/dr2392.C 2022-11-13 20:49:17.506880524 -1200
@@ -0,0 +1,12 @@
+// DR 2392
+// { dg-do compile { target c++11 } }
+
+template <class T = void>
+constexpr int
+foo ()
+{
+ T t;
+ return 1;
+}
+
+using V = decltype (new int[foo ()]);
Jakub
next reply other threads:[~2022-11-14 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 10:36 Jakub Jelinek [this message]
2022-11-15 0:02 ` Jason Merrill
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=Y3IaE4OIQGHhvhXv@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
/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).