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++/99425] [modules] ICE tree check: expected tree_vec, have tree_list in lookup_template_class_1, at cp/pt.c:9803
Date: Mon, 22 Mar 2021 15:27:06 +0000	[thread overview]
Message-ID: <bug-99425-4-jVB5kqLlDc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99425-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Nathan Sidwell <nathan@gcc.gnu.org>:

https://gcc.gnu.org/g:87e3c2ef682e2ba7692ee56142a4eb5b6441c4d3

commit r11-7765-g87e3c2ef682e2ba7692ee56142a4eb5b6441c4d3
Author: Nathan Sidwell <nathan@acm.org>
Date:   Thu Mar 18 05:12:59 2021 -0700

    c++: duplicate alias templates with decltype [PR 99425]

    This failure was ultimately from incorrect handling of alias
    templates, but required a specific set of occurrences to happen in the
    specialization hash table.  This cleans up the specialization
    streaming to add alias instantiations at the same point as other
    instantiations.  I also removed some unneeded global variables dealing
    with mapping of duplicate decl contexts.

            PR c++/99425
            gcc/cp/
            * cp-tree.h (map_context_from, map_context_to): Delete.
            (add_mergeable_specialization): Add is_alias parm.
            * pt.c (add_mergeable_specialization): Add is_alias parm, add them.
            * module.cc (map_context_from, map_context_to): Delete.
            (trees_in::decl_value): Add specializations later, adjust call.
            Drop useless alias lookup. Set duplicate fn parm context.
            (check_mergeable_decl): Drop context mapping.
            (trees_in::is_matching_decl): Likewise.
            (trees_in::read_function_def): Drop parameter context adjustment
            here.
            gcc/testsuite/
            * g++.dg/modules/pr99425-1.h: New.
            * g++.dg/modules/pr99425-1_a.H: New.
            * g++.dg/modules/pr99425-1_b.H: New.
            * g++.dg/modules/pr99425-1_c.C: New.
            * g++.dg/modules/pr99425-2_a.X: New.
            * g++.dg/modules/pr99425-2_b.X: New.
            * g++.dg/template/pr99425.C: New.

  parent reply	other threads:[~2021-03-22 15:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06  7:49 [Bug c++/99425] New: " alexander.lelyakin at googlemail dot com
2021-03-09  8:18 ` [Bug c++/99425] " alexander.lelyakin at googlemail dot com
2021-03-12  6:40 ` alexander.lelyakin at googlemail dot com
2021-03-22 15:27 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-22 15:27 ` nathan 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-99425-4-jVB5kqLlDc@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).