public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "crrodriguez at opensuse dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/111775] New: -Wstrict-flex-arrays missing diagnostics with unions Date: Wed, 11 Oct 2023 19:39:34 +0000 [thread overview] Message-ID: <bug-111775-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111775 Bug ID: 111775 Summary: -Wstrict-flex-arrays missing diagnostics with unions Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: crrodriguez at opensuse dot org Target Milestone: --- following code is not diagnosed #include <stddef.h> #include <stdlib.h> #include <stdio.h> struct foo { int dum; union { /* or [1] */ char a[0]; wchar_t b[0]; } fn; }; int main(void) { struct foo *f = malloc(sizeof(*f)); /* or really any use of the union does not matter */ printf("%p", f->fn.b); free(f); return 0; } compile options -Wall -fstrict-flex-arrays -Werror=strict-flex-arrays -O2 This test is a silly mockup of real widespread code, which goes undiagnosed until test suites run and/or is built with ubsan.
next reply other threads:[~2023-10-11 19:39 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-11 19:39 crrodriguez at opensuse dot org [this message] 2024-06-14 14:50 ` [Bug middle-end/111775] " crrodriguez at opensuse dot org 2024-06-14 15:08 ` qinzhao 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-111775-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).