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++/106983] [12/13 Regression] ICE tree check: expected class 'type', have 'exceptional' (error_mark) in type_build_dtor_call, at cp/class.cc:5794
Date: Fri, 23 Sep 2022 00:24:31 +0000	[thread overview]
Message-ID: <bug-106983-4-zVauJtNAdD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106983-4@http.gcc.gnu.org/bugzilla/>

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

--- 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:8b449dcd84334068c769a2f427812dadb95e61de

commit r13-2803-g8b449dcd84334068c769a2f427812dadb95e61de
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue Sep 20 14:54:57 2022 -0400

    c++: ICE-on-invalid with designated initializer [PR106983]

    We ICE in the code added in r12-7117: type_build_dtor_call gets
    the error_mark_node because the type of 'prev' wasn't declared.

            PR c++/106983

    gcc/cp/ChangeLog:

            * typeck2.cc (split_nonconstant_init_1): Check TYPE_P.

    gcc/testsuite/ChangeLog:

            * g++.dg/other/error36.C: New test.

  parent reply	other threads:[~2022-09-23  0:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 17:31 [Bug c++/106983] New: " gscfq@t-online.de
2022-09-20 18:28 ` [Bug c++/106983] " mpolacek at gcc dot gnu.org
2022-09-20 18:28 ` mpolacek at gcc dot gnu.org
2022-09-20 18:31 ` pinskia at gcc dot gnu.org
2022-09-20 18:38 ` mpolacek at gcc dot gnu.org
2022-09-23  0:24 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-23  0:57 ` 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-106983-4-zVauJtNAdD@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).