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/114731] -Wincompatible-pointer-types false positive in combination with _Generic(3) Date: Tue, 16 Apr 2024 03:03:24 +0000 [thread overview] Message-ID: <bug-114731-4-KRPP5cLQ2h@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114731-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114731 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Because the inner _Generic gets selected first and then outter one is selected. Also note clang has the same behavior . Note the syntax error is just a2i should not have a comma in it.
next prev parent reply other threads:[~2024-04-16 3:03 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-16 2:37 [Bug c/114731] New: " alx at kernel dot org 2024-04-16 2:49 ` [Bug c/114731] " sjames at gcc dot gnu.org 2024-04-16 2:56 ` alx at kernel dot org 2024-04-16 2:58 ` alx at kernel dot org 2024-04-16 2:59 ` sjames at gcc dot gnu.org 2024-04-16 3:02 ` alx at kernel dot org 2024-04-16 3:03 ` pinskia at gcc dot gnu.org [this message] 2024-04-16 3:05 ` pinskia at gcc dot gnu.org 2024-04-16 3:10 ` pinskia at gcc dot gnu.org 2024-04-16 3:11 ` alx at kernel dot org 2024-04-16 3:15 ` pinskia at gcc dot gnu.org 2024-04-16 3:17 ` alx at kernel dot org 2024-04-16 10:52 ` alx at kernel dot org 2024-04-16 10:55 ` uecker at gcc dot gnu.org 2024-04-16 11:01 ` alx at kernel dot org 2024-04-16 11:07 ` alx at kernel dot org 2024-04-16 11:17 ` uecker at gcc dot gnu.org 2024-04-16 11:26 ` alx at kernel dot org 2024-04-16 12:01 ` muecker at gwdg dot de 2024-04-16 12:05 ` muecker at gwdg dot de 2024-04-16 12:25 ` alx at kernel dot org 2024-04-16 12:32 ` alx at kernel dot 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-114731-4-KRPP5cLQ2h@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).