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++/91706] [9/10/11/12 Regression] ICE: tree check: expected class 'type', have 'exceptional' (error_mark) in equate_type_number_to_die, at dwarf2out.c:5782
Date: Tue, 08 Jun 2021 03:56:59 +0000	[thread overview]
Message-ID: <bug-91706-4-YBkoSxymtd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91706-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:1a98f830332e5a623278aaeea39c2a88177b2a9a

commit r12-1273-g1a98f830332e5a623278aaeea39c2a88177b2a9a
Author: Jason Merrill <jason@redhat.com>
Date:   Fri Apr 16 13:52:02 2021 -0400

    c++: preserve BASELINK from lookup [PR91706]

    In the earlier patch for PR91706 I fixed the BASELINK built by
    baselink_for_fns, but since we already had one from lookup, we should keep
    that one around instead of stripping it.  The removed hunk in
    get_class_binding was a wierdly large amount of code to decide whether to
    pull out BASELINK_FUNCTIONS.

    gcc/cp/ChangeLog:

            PR c++/91706
            * name-lookup.c (get_class_binding): Keep a BASELINK.
            (set_inherited_value_binding_p): Adjust.
            * lambda.c (is_lambda_ignored_entity): Adjust.
            * pt.c (lookup_template_function): Copy a BASELINK before
            modifying it.

  parent reply	other threads:[~2021-06-08  3:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-91706-4@http.gcc.gnu.org/bugzilla/>
2020-04-24 14:56 ` [Bug c++/91706] [8/9/10 " ppalka at gcc dot gnu.org
2021-04-16 14:12 ` [Bug c++/91706] [8/9/10/11 " jason at gcc dot gnu.org
2021-04-16 16:07 ` jason at gcc dot gnu.org
2021-04-20  4:40 ` jason at gcc dot gnu.org
2021-05-14  9:52 ` [Bug c++/91706] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:15 ` rguenth at gcc dot gnu.org
2021-06-08  3:56 ` cvs-commit at gcc dot gnu.org
2021-06-08  3:56 ` cvs-commit at gcc dot gnu.org [this message]
2021-06-08 13:24 ` cvs-commit at gcc dot gnu.org
2021-06-08 21:20 ` [Bug c++/91706] [9/10 " jason at gcc dot gnu.org
2021-06-16 21:29 ` cvs-commit at gcc dot gnu.org
2022-05-13 20:11 ` jason at gcc dot gnu.org
2022-05-27  9:41 ` [Bug c++/91706] [10 " rguenth at gcc dot gnu.org
2022-06-28 10:38 ` jakub at gcc dot gnu.org
2023-07-07  8:34 ` rguenth 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-91706-4-YBkoSxymtd@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).