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++/102414] [12 Regression] ICE in unify_array_domain, at cp/pt.c:23442 since r12-1933-ge66d0b7b87d105d2 Date: Mon, 31 Jan 2022 20:36:35 +0000 [thread overview] Message-ID: <bug-102414-4-RCLK1ahodF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102414-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102414 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:874ad5d6745bf3bbe4aa138cef09c669b3fb9b07 commit r12-6952-g874ad5d6745bf3bbe4aa138cef09c669b3fb9b07 Author: Marek Polacek <polacek@redhat.com> Date: Thu Jan 27 18:11:03 2022 -0500 c++: ICE with auto[] and VLA [PR102414] Here we ICE in unify_array_domain when we're trying to deduce the type of an array, as in auto(*p)[i] = (int(*)[i])0; but unify_array_domain doesn't arbitrarily complex bounds. Another test is, e.g., auto (*b)[0/0] = &a; where the type of the array is <<< Unknown tree: template_type_parm >>>[0:(sizetype) ((ssizetype) (0 / 0) - 1)] It seems to me that we need not handle these. PR c++/102414 PR c++/101874 gcc/cp/ChangeLog: * decl.cc (create_array_type_for_decl): Use template_placeholder_p. Sorry on a variable-length array of auto. gcc/testsuite/ChangeLog: * g++.dg/cpp23/auto-array3.C: New test. * g++.dg/cpp23/auto-array4.C: New test.
next prev parent reply other threads:[~2022-01-31 20:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-20 19:03 [Bug c++/102414] New: [12 Regression] ICE in unify_array_domain, at cp/pt.c:23442 gscfq@t-online.de 2021-09-20 22:44 ` [Bug c++/102414] " pinskia at gcc dot gnu.org 2021-09-27 12:54 ` [Bug c++/102414] [12 Regression] ICE in unify_array_domain, at cp/pt.c:23442 since r12-1933-ge66d0b7b87d105d2 marxin at gcc dot gnu.org 2021-09-27 13:33 ` mpolacek at gcc dot gnu.org 2022-01-20 9:56 ` rguenth at gcc dot gnu.org 2022-01-31 20:36 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-31 20:38 ` mpolacek 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-102414-4-RCLK1ahodF@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: linkBe 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).