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 target/108189] anonymous struct declared inside parameter list will not be visible outside of this definition or declaration
Date: Tue, 20 Dec 2022 21:18:12 +0000	[thread overview]
Message-ID: <bug-108189-4-lBg8mpX9ov@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108189-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108189

--- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to James Hilliard from comment #8) 
> Yeah, clang with -std=gnu17 -pedantic doesn't even complain at all from the
> looks of it. Does it make sense to allow disabling this specific warning in
> GCC?

No it does not make sense at all to disable this specific warning; maybe
request clang implement the warning too.

> What would be the correct way to fix these in bpf-next?

Move the struct definition outside of the function definition? You could ask
the bpf mailing list of what is the fix they would like to see for this
questionable code.

  parent reply	other threads:[~2022-12-20 21:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 20:27 [Bug target/108189] New: " james.hilliard1 at gmail dot com
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 [this message]
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-lBg8mpX9ov@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).