public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "luigighiron at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/114723] New: ICE when checking for type compatibility with structure that contains flexible array member Date: Mon, 15 Apr 2024 15:33:07 +0000 [thread overview] Message-ID: <bug-114723-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114723 Bug ID: 114723 Summary: ICE when checking for type compatibility with structure that contains flexible array member Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: luigighiron at gmail dot com Target Milestone: --- The following code causes an internal compiler error on GCC 14: #include<stdio.h> struct S{int x,y[1];}*a; int main(void){ struct S{int x,y[];}; puts(_Generic( a, struct S*:"compatible", default:"incompatible" )); } If I understand the type compatibility rules, these types should be compatible? The types "int[1]" and "int[]" are compatible and everything else seems to match exactly. Interestingly, it seems to also crash when checking if the type of a is compatible with struct S (instead of struct S*).
next reply other threads:[~2024-04-15 15:33 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-15 15:33 luigighiron at gmail dot com [this message] 2024-04-16 7:30 ` [Bug c/114723] ICE when checking for type compatibility with structure that contains flexible array member (C23) rguenth at gcc dot gnu.org 2024-04-16 17:18 ` luigighiron at gmail dot com 2024-04-24 2:10 ` luigighiron at gmail dot com 2024-04-24 2:21 ` pinskia at gcc dot gnu.org 2024-04-24 2:22 ` pinskia at gcc dot gnu.org 2024-04-24 3:01 ` luigighiron at gmail dot com 2024-04-24 3:04 ` pinskia 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-114723-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).