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++/109658] [14 Regression] ICE when building aria2-1.36.0 (internal compiler error: in instantiate_decl, at cp/pt.cc:27095) since r14-283-g95d4c0d2e6318a
Date: Fri, 05 May 2023 01:07:27 +0000	[thread overview]
Message-ID: <bug-109658-4-xFtRxNgikt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109658-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:6f18f344338b370031e75924eed2bdd1ce5c8dba

commit r14-487-g6f18f344338b370031e75924eed2bdd1ce5c8dba
Author: Jason Merrill <jason@redhat.com>
Date:   Thu May 4 18:37:19 2023 -0400

    Revert "c++: restore instantiate_decl assert"

    In the testcase the assert fails because we use one member function from
    another while we're in the middle of instantiating them all, which is
    perfectly fine.  It seems complicated to detect this situation, so let's
    remove the assert again.

            PR c++/109658

    This reverts commit 95d4c0d2e6318aef88ba0bc607dfc1ec6b7a612f.

    gcc/testsuite/ChangeLog:

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

  parent reply	other threads:[~2023-05-05  1:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28  2:22 [Bug c++/109658] New: ICE when building aria2-1.36.0 (internal compiler error: in instantiate_decl, at cp/pt.cc:27095) sjames at gcc dot gnu.org
2023-04-28  2:23 ` [Bug c++/109658] " sjames at gcc dot gnu.org
2023-04-28  2:28 ` pinskia at gcc dot gnu.org
2023-04-28  5:05 ` [Bug c++/109658] ICE when building aria2-1.36.0 (internal compiler error: in instantiate_decl, at cp/pt.cc:27095) since r14-283-g95d4c0d2e6318a sjames at gcc dot gnu.org
2023-04-28  5:06 ` sjames at gcc dot gnu.org
2023-04-28  5:58 ` sjames at gcc dot gnu.org
2023-04-28  6:32 ` sjames at gcc dot gnu.org
2023-04-28  6:47 ` [Bug c++/109658] [14 Regression] " rguenth at gcc dot gnu.org
2023-05-05  1:07 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-05  1:08 ` jason at gcc dot gnu.org
2023-05-05  1:09 ` jason at gcc dot gnu.org
2023-05-05  1:09 ` jason 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-109658-4-xFtRxNgikt@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).