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++/99248] [modules] ICE expected binding_vector, have overload in lookup_elaborated_type_1, at cp/name-lookup.c:8013
Date: Thu, 11 Mar 2021 21:13:17 +0000	[thread overview]
Message-ID: <bug-99248-4-fOctkeiQpX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99248-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 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:5f27a9f90d4eadadf937f1a5d0bfccf39261f330

commit r11-7632-g5f27a9f90d4eadadf937f1a5d0bfccf39261f330
Author: Nathan Sidwell <nathan@acm.org>
Date:   Thu Mar 11 13:06:36 2021 -0800

    c++: Fix unhiding friend with imports [PR 99248]

    This was a simple thinko about which object held the reference to the
    binding vector.  I also noticed stale code in the tree dumper, as I
    recently removed the flags from a lazy number.

            PR c++/99248
            gcc/cp/
            * name-lookup.c (lookup_elaborated_type_1): Access slot not bind
            when there's a binding vector.
            * ptree.c (cxx_print_xnode): Lazy flags are no longer a thing.
            gcc/testsuite/
            * g++.dg/modules/pr99248.h: New.
            * g++.dg/modules/pr99248_a.H: New.
            * g++.dg/modules/pr99248_b.H: New.

  parent reply	other threads:[~2021-03-11 21:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24  8:51 [Bug c++/99248] New: internal compiler error: tree check: " alexander.lelyakin at googlemail dot com
2021-02-28 21:00 ` [Bug c++/99248] [modules] ICE " alexander.lelyakin at googlemail dot com
2021-03-11  8:12 ` alexander.lelyakin at googlemail dot com
2021-03-11 19:52 ` nathan at gcc dot gnu.org
2021-03-11 21:13 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-11 21:13 ` 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-99248-4-fOctkeiQpX@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).