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++/108206] [12 Regression] ICE: tree check: expected tree that contains 'decl minimal' structure, have 'error_mark' in merge_default_template_args, at cp/decl.cc:1563 since r12-7562-gfe548eb8436f3906
Date: Fri, 10 Feb 2023 17:45:23 +0000	[thread overview]
Message-ID: <bug-108206-4-ZiQRK9wzCJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108206-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:7048e8c1073fcf2bf6be1a3d079393a78864ca61

commit r12-9137-g7048e8c1073fcf2bf6be1a3d079393a78864ca61
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Wed Jan 4 18:42:31 2023 +0100

    c++: Error recovery in merge_default_template_args [PR108206]

    We ICE on the following testcase during error recovery, both new_parm
    and old_parm are error_mark_node, the ICE is on
              error ("redefinition of default argument for %q+#D", new_parm);
              inform (DECL_SOURCE_LOCATION (old_parm),
                      "original definition appeared here");
    where we don't print anything useful for new_parm and ICE trying to
    access DECL_SOURCE_LOCATION of old_parm.  I think we shouldn't diagnose
    anything when either of the parms is erroneous, GCC 11 before
    merge_default_template_args has been added was doing
          if (TREE_VEC_ELT (tmpl_parms, i) == error_mark_node
              || TREE_VEC_ELT (parms, i) == error_mark_node)
            continue;

          tmpl_parm = TREE_VALUE (TREE_VEC_ELT (tmpl_parms, i));
          if (error_operand_p (tmpl_parm))
            return false;
    in redeclare_class_template.

    2023-01-04  Jakub Jelinek  <jakub@redhat.com>

            PR c++/108206
            * decl.cc (merge_default_template_args): Return false if either
            new_parm or old_parm are erroneous.

            * g++.dg/template/pr108206.C: New test.

    (cherry picked from commit fc349931adcf1024ee95e0a0cd98cf4a41996093)

  parent reply	other threads:[~2023-02-10 17:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-23  6:51 [Bug c++/108206] New: ICE: tree check: expected tree that contains 'decl minimal' structure, have 'error_mark' in merge_default_template_args, at cp/decl.cc:1563 asolokha at gmx dot com
2022-12-23  6:52 ` [Bug c++/108206] " asolokha at gmx dot com
2022-12-23  8:53 ` [Bug c++/108206] ICE: tree check: expected tree that contains 'decl minimal' structure, have 'error_mark' in merge_default_template_args, at cp/decl.cc:1563 since r12-7562-gfe548eb8436f3906 marxin at gcc dot gnu.org
2022-12-24 20:33 ` [Bug c++/108206] [12/13 Regression] " pinskia at gcc dot gnu.org
2023-01-03 17:16 ` jakub at gcc dot gnu.org
2023-01-04 17:43 ` cvs-commit at gcc dot gnu.org
2023-01-04 17:44 ` [Bug c++/108206] [12 " jakub at gcc dot gnu.org
2023-01-09 13:25 ` rguenth at gcc dot gnu.org
2023-02-10 17:45 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-10 17:59 ` jakub 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-108206-4-ZiQRK9wzCJ@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).