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++/58646] [9/10/11 Regression] ICE on a multidimensional VLA with an empty initializer list
Date: Tue, 22 Mar 2022 05:18:11 +0000	[thread overview]
Message-ID: <bug-58646-4-jo3qXyb5Ex@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58646-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:

https://gcc.gnu.org/g:09d0fc6912c4f600432caecc6ab0a277f2aef480

commit r11-9679-g09d0fc6912c4f600432caecc6ab0a277f2aef480
Author: Jason Merrill <jason@redhat.com>
Date:   Mon Mar 21 17:48:01 2022 -0400

    c++: initialized array of vla [PR58646]

    We went into build_vec_init because we're dealing with a VLA, but then
    build_vec_init thought it was safe to just build an INIT_EXPR because the
    outer dimension is constant.  Nope.

            PR c++/58646

    gcc/cp/ChangeLog:

            * init.c (build_vec_init): Check for vla element type.

    gcc/testsuite/ChangeLog:

            * g++.dg/ext/vla24.C: New test.

  parent reply	other threads:[~2022-03-22  5:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-06 20:32 [Bug c++/58646] New: ICEs initializing VLAs reichelt at gcc dot gnu.org
2013-10-06 20:36 ` [Bug c++/58646] " reichelt at gcc dot gnu.org
2013-10-07 11:44 ` mpolacek at gcc dot gnu.org
2020-04-01  9:00 ` [Bug c++/58646] [8/9/10 Regression] ICE on a multidimensional VLA with an empty initializer list rguenth at gcc dot gnu.org
2021-05-14  9:46 ` [Bug c++/58646] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:06 ` rguenth at gcc dot gnu.org
2021-09-19 17:33 ` pinskia at gcc dot gnu.org
2021-10-01  7:16 ` pinskia at gcc dot gnu.org
2022-01-05 11:14 ` pinskia at gcc dot gnu.org
2022-01-21 17:48 ` pinskia at gcc dot gnu.org
2022-03-21 21:10 ` jason at gcc dot gnu.org
2022-03-21 22:25 ` cvs-commit at gcc dot gnu.org
2022-03-22  5:18 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-27  9:34 ` [Bug c++/58646] [10/11 " rguenth at gcc dot gnu.org
2022-06-28 10:30 ` jakub at gcc dot gnu.org
2023-07-07  7:22 ` 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-58646-4-jo3qXyb5Ex@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).