public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "muecker at gwdg dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/109956] GCC reserves 9 bytes for struct s { int a; char b; char t[]; } x = {1, 2, 3}; Date: Wed, 24 May 2023 16:28:21 +0000 [thread overview] Message-ID: <bug-109956-4-3sOO8o9rKu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109956-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109956 Martin Uecker <muecker at gwdg dot de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |muecker at gwdg dot de --- Comment #2 from Martin Uecker <muecker at gwdg dot de> --- To me it seems that the C standard requires that the object has size sizeof(struct s) + n * sizeof(struct t) if you want to store n elements even when the array then starts at a smaller offset.
next prev parent reply other threads:[~2023-05-24 16:28 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-24 16:09 [Bug c/109956] New: " pascal_cuoq at hotmail dot com 2023-05-24 16:20 ` [Bug c/109956] " pinskia at gcc dot gnu.org 2023-05-24 16:28 ` muecker at gwdg dot de [this message] 2023-05-24 18:30 ` pascal_cuoq at hotmail dot com 2023-05-24 19:18 ` muecker at gwdg dot de 2023-05-24 20:25 ` muecker at gwdg dot de 2023-05-24 21:50 ` joseph at codesourcery dot com 2023-05-24 21:55 ` joseph at codesourcery dot com 2023-05-25 5:23 ` amonakov at gcc dot gnu.org 2023-05-25 5:29 ` muecker at gwdg dot de 2023-05-25 5:30 ` pinskia at gcc dot gnu.org 2023-05-25 7:53 ` rguenth at gcc dot gnu.org 2023-05-25 16:42 ` muecker at gwdg dot de 2023-05-26 12:03 ` pascal_cuoq at hotmail dot com 2023-05-26 16:24 ` muecker at gwdg dot de 2023-08-08 14:57 ` muecker at gwdg dot de 2024-03-14 20:17 ` 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-109956-4-3sOO8o9rKu@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).