public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "StevenSun2021 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108218] New: [12 Regression] Constant arguments in the new expression is not checked in unevaluated operand
Date: Sat, 24 Dec 2022 15:52:56 +0000	[thread overview]
Message-ID: <bug-108218-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108218

            Bug ID: 108218
           Summary: [12 Regression] Constant arguments in the new
                    expression is not checked in unevaluated operand
           Product: gcc
           Version: 12.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: StevenSun2021 at hotmail dot com
  Target Milestone: ---

```
int main() {
    decltype(new int[-1]) a; // compiles with g++-12! <- regression here
                             // does not compile with g++-11


    auto b = new int[-1];    // does not compile with g++-12
                             // does not compile with g++-11
}
```
https://godbolt.org/z/aMGMrbfrd


expected behavior:
if, after conversion to std::size_t, the first dimension is a core constant
expression and it is potentially evaluated, the program is ill-formed.
https://en.cppreference.com/w/cpp/language/new

gcc(<=11.3 (current version)) and clang(>=3) does this check.

             reply	other threads:[~2022-12-24 15:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24 15:52 StevenSun2021 at hotmail dot com [this message]
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
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@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).