public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/101869] [9/10/11/12 Regression] &enumclass::enumvalue is rejected
Date: Wed, 30 Mar 2022 21:50:57 +0000 [thread overview]
Message-ID: <bug-101869-4-ozRyoTJufG@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
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2022-03-30
Ever confirmed|0 |1
CC| |mpolacek at gcc dot gnu.org
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed.
Started working with r139611:
commit adf2edec3cd9b9002b7096744b627e4ea3b0d9d4
Author: Douglas Gregor <doug.gregor@gmail.com>
Date: Tue Aug 26 22:33:10 2008 +0000
c-common.c (do_switch_warnings): Look through the CONST_DECLs in the
enumerators of an ENUMERAL_TYPE.
2008-08-26 Douglas Gregor <doug.gregor@gmail.com>
* c-common.c (do_switch_warnings): Look through the CONST_DECLs in
the enumerators of an ENUMERAL_TYPE.
* dbxout.c (dbxout_type): Ditto.
and stopped with r190829:
commit e467c9d25782edea98d2cd66956d5abb82e847e9
Author: Jason Merrill <jason@redhat.com>
Date: Thu Aug 30 22:50:18 2012 -0400
semantics.c (finish_qualified_id_expr): Handle building up a non-dependent
SCOPE_REF here.
* semantics.c (finish_qualified_id_expr): Handle building up a
non-dependent SCOPE_REF here.
(finish_id_expression): Not here.
* error.c (dump_decl) [SCOPE_REF]: Only pass TFF_UNQUALIFIED_NAME.
next prev parent reply other threads:[~2022-03-30 21:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 1:07 [Bug c++/101869] New: " 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 [this message]
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
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-ozRyoTJufG@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).