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++/100362] [11/12 Regression] ICE with Boost.Asio async_initiate
Date: Mon, 03 May 2021 19:15:25 +0000	[thread overview]
Message-ID: <bug-100362-4-ct7eQncoPC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100362-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Patrick Palka
<ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:a32b7d03210f1763a5ccd017181ad88bd95b07d1

commit r11-8344-ga32b7d03210f1763a5ccd017181ad88bd95b07d1
Author: Patrick Palka <ppalka@redhat.com>
Date:   Mon May 3 13:35:37 2021 -0400

    c++: base-clause parsing and implicit 'this' [PR100362]

    My r11-6815 change to defer access checking when processing a
    base-clause removed a pair of pushclass / popclass calls that seemed to
    be unnecessary now that we'd also defer access checking while parsing
    the base-clause.

    But it turns out these calls make a difference in the below testcase,
    where we have a local class whose base-clause implicitly uses the 'this'
    of the enclosing class.  Before r11-6815, while parsing the base-clause
    of the local class, maybe_resolve_dummy would fail to resolve the dummy
    'this' object because the current scope would be the local class.  Now,
    since the current scope is the lambda, maybe_resolve_dummy succeeds and
    returns the 'this' for the enclosing class Qux.  Later, during deferred
    instantiation of the local class, we get confused trying to resolve the
    access of 'a_' through this non-dummy 'this'.

    So this patch just reinstates the calls to pushclass / popclass that
    were removed in r11-6815.

    gcc/cp/ChangeLog:

            PR c++/100362
            * parser.c (cp_parser_class_head): Reinstate calls to pushclass
            and popclass when parsing the base-clause that were removed in
            r11-6815.

    gcc/testsuite/ChangeLog:

            PR c++/100362
            * g++.dg/cpp1y/lambda-generic-100362.C: New test.

    (cherry picked from commit 2a6fc19e655e696bf0df9b7aaedf9848b23f07f3)

  parent reply	other threads:[~2021-05-03 19:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 18:54 [Bug c++/100362] New: " enolan at alumni dot cmu.edu
2021-04-30 21:32 ` [Bug c++/100362] " mpolacek at gcc dot gnu.org
2021-04-30 22:37 ` [Bug c++/100362] [11/12 Regression] " mpolacek at gcc dot gnu.org
2021-05-03  7:34 ` rguenth at gcc dot gnu.org
2021-05-03 14:32 ` ppalka at gcc dot gnu.org
2021-05-03 15:44 ` ppalka at gcc dot gnu.org
2021-05-03 17:36 ` cvs-commit at gcc dot gnu.org
2021-05-03 19:15 ` cvs-commit at gcc dot gnu.org [this message]
2021-05-03 19:16 ` ppalka 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-100362-4-ct7eQncoPC@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).