public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/9058: structure with flexible array member: offsetof() != sizeof() Date: Thu, 26 Dec 2002 14:26:00 -0000 [thread overview] Message-ID: <20021226222602.11680.qmail@sources.redhat.com> (raw) The following reply was made to PR c/9058; it has been noted by GNATS. From: "Joseph S. Myers" <jsm28@cam.ac.uk> To: Manfred Spraul <manfred@colorfullife.com> Cc: <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org> Subject: Re: c/9058: structure with flexible array member: offsetof() != sizeof() Date: Thu, 26 Dec 2002 22:24:11 +0000 (GMT) On Thu, 26 Dec 2002, Manfred Spraul wrote: > Thanks, I found the thread "C99 conformance bug in gcc-3.1" after filing > the bug report. > What's the recommended approach to calculate the size for malloc calls? Is > > struct a {int a; char b; short c[]; }; > > len = offsetof(struct a, c[nr_entries]); You mean offsetof(struct a, c) + nr_entries * sizeof(short). > > valid and portable? > > sizeof(struct a)+nr_entries*sizeof(short); > > would waste 2 bytes. Those would be the bytes of padding (that might or might not nominally be needed, depending on the size of the array). I don't believe their absence can cause problems unless you directly assign structures for which less memory than the size of the original structure has been allocated (in which case you'll lose the flexible array members anyway) but you'll need to study the detailed wording of the standard (as proposed to be amended) to work out what is guaranteed portable. -- Joseph S. Myers jsm28@cam.ac.uk
next reply other threads:[~2002-12-26 22:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-26 14:26 Joseph S. Myers [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-13 21:13 bangerth 2003-01-13 0:20 bangerth 2002-12-26 15:46 Manfred Spraul 2002-12-26 13:46 Manfred Spraul 2002-12-26 12:26 Joseph S. Myers 2002-12-26 4:36 manfred
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=20021226222602.11680.qmail@sources.redhat.com \ --to=jsm28@cam.ac.uk \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).