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++/108218] [12/13 Regression] Constant arguments in the new expression is not checked in unevaluated operand since r12-5253-g4df7f8c79835d569
Date: Tue, 10 Jan 2023 15:16:51 +0000 [thread overview]
Message-ID: <bug-108218-4-YPU8dSFxk6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108218-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108218
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ppalka at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=108219
--- Comment #9 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to Steven Sun from comment #7)
> I got one simple idea as a workaround. I do not have the resources to do the
> tests.
FWIW that seems like the right idea, but it regresses
gcc/testsuite/g++.dg/DRs/dr2392.C:
$ cat gcc/testsuite/g++.dg/DRs/dr2392.C
// 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 ()]);
$ gcc gcc/testsuite/g++.dg/DRs/dr2392.C
gcc/testsuite/g++.dg/DRs/dr2392.C: In instantiation of ‘constexpr int foo()
[with T = void]’:
gcc/testsuite/g++.dg/DRs/dr2392.C:12:33: required from here
gcc/testsuite/g++.dg/DRs/dr2392.C:8:5: error: variable or field ‘t’ declared
void
8 | T t;
| ^
next prev parent reply other threads:[~2023-01-10 15:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 15:52 [Bug c++/108218] New: [12 Regression] Constant arguments in the new expression is not checked in unevaluated operand StevenSun2021 at hotmail dot com
2022-12-24 16:00 ` [Bug c++/108218] " StevenSun2021 at hotmail dot com
2022-12-24 19:19 ` [Bug c++/108218] [12/13 " pinskia at gcc dot gnu.org
2022-12-24 20:44 ` StevenSun2021 at hotmail dot com
2022-12-24 20:46 ` pinskia at gcc dot gnu.org
2022-12-24 20:49 ` StevenSun2021 at hotmail dot com
2022-12-24 20:56 ` StevenSun2021 at hotmail dot com
2022-12-24 22:53 ` StevenSun2021 at hotmail dot com
2022-12-27 12:24 ` [Bug c++/108218] [12/13 Regression] Constant arguments in the new expression is not checked in unevaluated operand since r12-5253-g4df7f8c79835d569 marxin at gcc dot gnu.org
2023-01-09 13:42 ` rguenth at gcc dot gnu.org
2023-01-10 15:16 ` ppalka at gcc dot gnu.org [this message]
2023-01-10 18:52 ` pinskia at gcc dot gnu.org
2023-01-21 17:22 ` StevenSun2021 at hotmail dot com
2023-01-25 2:59 ` jason at gcc dot gnu.org
2023-01-25 3:19 ` jason at gcc dot gnu.org
2023-03-01 19:09 ` cvs-commit at gcc dot gnu.org
2023-04-28 22:13 ` [Bug c++/108218] [12/13/14 " cvs-commit at gcc dot gnu.org
2023-05-08 12:26 ` 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-108218-4-YPU8dSFxk6@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).