public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "james.hilliard1 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108189] New: anonymous struct declared inside parameter list will not be visible outside of this definition or declaration Date: Tue, 20 Dec 2022 20:27:02 +0000 [thread overview] Message-ID: <bug-108189-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108189 Bug ID: 108189 Summary: anonymous struct declared inside parameter list will not be visible outside of this definition or declaration Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: james.hilliard1 at gmail dot com Target Milestone: --- I'm seeing this error which does not occur in llvm for a bpf test(btf_dump_test_case_bitfields.c) in bpf-next: progs/btf_dump_test_case_bitfields.c:85:7: error: anonymous struct declared inside parameter list will not be visible outside of this definition or declaration [-Werror] 85 | int f(struct { | ^~~~~~
next reply other threads:[~2022-12-20 20:27 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-20 20:27 james.hilliard1 at gmail dot com [this message] 2022-12-20 20:30 ` [Bug target/108189] " pinskia at gcc dot gnu.org 2022-12-20 20:40 ` james.hilliard1 at gmail dot com 2022-12-20 20:41 ` pinskia at gcc dot gnu.org 2022-12-20 20:46 ` pinskia at gcc dot gnu.org 2022-12-20 20:46 ` pinskia at gcc dot gnu.org 2022-12-20 20:48 ` pinskia at gcc dot gnu.org 2022-12-20 20:56 ` pinskia at gcc dot gnu.org 2022-12-20 21:09 ` james.hilliard1 at gmail dot com 2022-12-20 21:15 ` james.hilliard1 at gmail dot com 2022-12-20 21:18 ` pinskia at gcc dot gnu.org 2022-12-22 19:09 ` james.hilliard1 at gmail dot com 2024-05-07 2:08 ` dxu at dxuuu dot xyz 2024-05-07 6:34 ` jemarch at gcc dot gnu.org 2024-05-07 14:44 ` dxu at dxuuu dot xyz
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-108189-4@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).