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++/102740] [10/11/12 Regression] Data member not found in struct inside an unnamed union Date: Tue, 16 Nov 2021 21:57:33 +0000 [thread overview] Message-ID: <bug-102740-4-ENBklsGO0C@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102740-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102740 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roland at gnu dot org --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- *** Bug 103290 has been marked as a duplicate of this bug. ***
next prev parent reply other threads:[~2021-11-16 21:57 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-14 7:05 [Bug c++/102740] New: [11.2/12 " curdeius at gmail dot com 2021-10-14 7:13 ` [Bug c++/102740] [10/11/12 " curdeius at gmail dot com 2021-10-14 7:14 ` pinskia at gcc dot gnu.org 2021-10-14 7:16 ` rguenth at gcc dot gnu.org 2021-10-14 7:56 ` curdeius at gmail dot com 2021-11-16 21:57 ` pinskia at gcc dot gnu.org [this message] 2021-11-16 22:21 ` mpolacek at gcc dot gnu.org 2021-11-19 17:18 ` ppalka at gcc dot gnu.org 2022-01-20 17:33 ` ppalka at gcc dot gnu.org 2022-01-20 17:42 ` ppalka at gcc dot gnu.org 2022-03-18 19:15 ` jason at gcc dot gnu.org 2022-03-21 20:47 ` cvs-commit at gcc dot gnu.org 2022-03-21 21:00 ` [Bug c++/102740] [11 " jason at gcc dot gnu.org 2022-03-22 5:18 ` cvs-commit at gcc dot gnu.org 2022-03-26 23:28 ` jason 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-102740-4-ENBklsGO0C@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).