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++/101869] [10/11 Regression] &enumclass::enumvalue is rejected
Date: Sat, 22 Apr 2023 00:22:53 +0000	[thread overview]
Message-ID: <bug-101869-4-V8DLP4KwAo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101869-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:691e385b354482f3379bba471774873ca7179b79

commit r11-10643-g691e385b354482f3379bba471774873ca7179b79
Author: Jason Merrill <jason@redhat.com>
Date:   Thu Mar 16 13:11:32 2023 -0400

    c++: &enum::enumerator [PR101869]

    We don't want to call build_offset_ref with an enum.

            PR c++/101869

    gcc/cp/ChangeLog:

            * semantics.c (finish_qualified_id_expr): Don't try to build a
            pointer-to-member if the scope is an enumeration.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/enum43.C: New test.

  parent reply	other threads:[~2023-04-22  0:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12  1:07 [Bug c++/101869] New: [9/10/11/12 " pinskia at gcc dot gnu.org
2021-08-12  1:08 ` [Bug c++/101869] " pinskia at gcc dot gnu.org
2021-08-16  8:52 ` rguenth at gcc dot gnu.org
2022-03-30 21:50 ` mpolacek at gcc dot gnu.org
2022-05-27  9:45 ` [Bug c++/101869] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:45 ` jakub at gcc dot gnu.org
2023-03-16 17:14 ` jason at gcc dot gnu.org
2023-03-16 22:10 ` cvs-commit at gcc dot gnu.org
2023-04-18 20:46 ` [Bug c++/101869] [10/11/12 " cvs-commit at gcc dot gnu.org
2023-04-21 20:28 ` [Bug c++/101869] [10/11 " cvs-commit at gcc dot gnu.org
2023-04-22  0:22 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-07 10:40 ` [Bug c++/101869] [11 " 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-101869-4-V8DLP4KwAo@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).