public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
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 15:46:00 -0000	[thread overview]
Message-ID: <20021226234601.28049.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/9058; it has been noted by GNATS.

From: Manfred Spraul <manfred@colorfullife.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Subject: Re: c/9058: structure with flexible array member: offsetof() != sizeof()
Date: Fri, 27 Dec 2002 00:37:54 +0100

 Joseph S. Myers wrote:
 
 >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).
 >  
 >
 No, I meant what I wrote - is that valid? It would be less error prone, 
 e.g. if the type of the flexible array member is changed.
 linux kernel, i.e gcc portability across platforms.
 
 --
     Manfred
 


             reply	other threads:[~2002-12-26 23:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-26 15:46 Manfred Spraul [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 14:26 Joseph S. Myers
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=20021226234601.28049.qmail@sources.redhat.com \
    --to=manfred@colorfullife.com \
    --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: link
Be 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).