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++/109621] [10/11/12/13/14 Regression] GCC accepts invalid program with multiple using declarations Date: Tue, 25 Apr 2023 15:29:13 +0000 [thread overview] Message-ID: <bug-109621-4-Dtmw1nnhtx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109621-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109621 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|GCC accepts invalid program |[10/11/12/13/14 Regression] |with multiple using |GCC accepts invalid program |declarations |with multiple using | |declarations Known to fail| |4.4.7 Target Milestone|--- |10.5 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Known to work| |4.1.2 Last reconfirmed| |2023-04-25 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- C++98 version which shows it is a regression and it started to fail between GCC 4.1.2 and 4.4.7: ``` namespace X { struct type {}; } namespace Y { typedef int type; } using Y::type; using X::type; int i = sizeof(type); //gcc and msvc accepts this but clang rejects this ```
next prev parent reply other threads:[~2023-04-25 15:29 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-25 10:05 [Bug c++/109621] New: " jlame646 at gmail dot com 2023-04-25 15:29 ` pinskia at gcc dot gnu.org [this message] 2023-04-25 17:24 ` [Bug c++/109621] [10/11/12/13/14 Regression] " redi at gcc dot gnu.org 2023-04-25 17:25 ` redi at gcc dot gnu.org 2023-07-07 10:45 ` [Bug c++/109621] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-01-12 10:36 ` 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-109621-4-Dtmw1nnhtx@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).