public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Frederic De Jaeger <dejaeger@free.fr> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/10360: __alignof__(double) answer 8 Date: Wed, 09 Apr 2003 22:06:00 -0000 [thread overview] Message-ID: <20030409220601.10973.qmail@sources.redhat.com> (raw) The following reply was made to PR c/10360; it has been noted by GNATS. From: Frederic De Jaeger <dejaeger@free.fr> To: rth@gcc.gnu.org, discuss-gnustep@gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, richard@brainstorm.co.uk, thoran@free.fr, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c/10360: __alignof__(double) answer 8 Date: 09 Apr 2003 23:59:58 +0200 rth> Synopsis: __alignof__(double) answer 8 rth> State-Changed-From-To: open->closed rth> State-Changed-By: rth rth> State-Changed-When: Wed Apr 9 17:29:53 2003 rth> State-Changed-Why: rth> Not a bug. __alignof__ returns the *preferred* alignment. rth> You're seeing other SVr4 ABI rules concerning structures. Thus, why gcc does not align fields with respect to this *preferred* alignment? How can I compute the address of a field in a record? I need to do this uniformly on all the types. That means I cannot use the trick : offset = (char *)&foo.bla - (char *)&foo. or the "offsetof" macro. because I don't know, statically, the type of the record from which I need to compute offsets. The type information comes from the @encode directive of objective-C (ie: it's a characters string that describe a type). Actually, we are using "objc_alignof_type" (from the objective-c API) and we expect it to return the alignment used by the compiler (and not the *preferred* alignment). Thanks for your help, Frederic De Jaeger
next reply other threads:[~2003-04-09 22:06 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-09 22:06 Frederic De Jaeger [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-10 8:06 Richard Henderson 2003-04-10 5:16 Richard Frith-Macdonald 2003-04-09 22:46 Richard Henderson 2003-04-09 17:29 rth 2003-04-09 9:06 thoran
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=20030409220601.10973.qmail@sources.redhat.com \ --to=dejaeger@free.fr \ --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).