public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/90107] [9/10/11/12 Regression] rejects-valid on global-namespace-qualified variable declared after class definition Date: Tue, 07 Dec 2021 05:05:35 +0000 [thread overview] Message-ID: <bug-90107-4-D6PHIJTAoy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-90107-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90107 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |4.6.4 Summary|rejects-valid on |[9/10/11/12 Regression] |global-namespace-qualified |rejects-valid on |variable declared after |global-namespace-qualified |class definition |variable declared after | |class definition Known to work| |4.1.2, 4.4.7, 4.5.3 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Full valid testcase (instead of 2 sources combined together): struct A; namespace N { extern A a; } struct A {} ::N::a; struct A1; struct B { static A1 a1; }; struct A1 {} ::B::a1;
next parent reply other threads:[~2021-12-07 5:05 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-90107-4@http.gcc.gnu.org/bugzilla/> 2021-12-07 5:05 ` pinskia at gcc dot gnu.org [this message] 2021-12-07 5:05 ` pinskia at gcc dot gnu.org 2021-12-08 17:24 ` marxin at gcc dot gnu.org 2022-01-17 15:11 ` rguenth at gcc dot gnu.org 2022-04-27 19:18 ` mpolacek at gcc dot gnu.org 2022-04-27 21:51 ` mpolacek at gcc dot gnu.org 2022-04-28 12:41 ` cvs-commit at gcc dot gnu.org 2022-04-28 12:42 ` cvs-commit at gcc dot gnu.org 2022-04-28 12:48 ` [Bug c++/90107] [9/10 " mpolacek 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-90107-4-D6PHIJTAoy@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: linkBe 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).