public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/10360: __alignof__(double) answer 8
Date: Thu, 10 Apr 2003 08:06:00 -0000	[thread overview]
Message-ID: <20030410080601.12168.qmail@sources.redhat.com> (raw)

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

From: Richard Henderson <rth@redhat.com>
To: Richard Frith-Macdonald <richard@brainstorm.co.uk>
Cc: gcc-gnats@gcc.gnu.org, thoran@free.fr, nobody@gcc.gnu.org,
   gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, discuss-gnustep@gnu.org,
   rth@gcc.gnu.org, Frederic De Jaeger <dejaeger@free.fr>
Subject: Re: c/10360: __alignof__(double) answer 8
Date: Thu, 10 Apr 2003 01:00:00 -0700

 On Thu, Apr 10, 2003 at 06:06:44AM +0100, Richard Frith-Macdonald wrote:
 > It would be interesting to know in what sense the alignment is 
 > 'preferred'.
 
 In that it takes one less cycle to load that way?  In that that's
 how data gets aligned which isn't constrained by the ABI?
 
 > Shouldn't this either be fixed as Frederic suggests, or the documentation
 > be changed so that instead of saying 'preferred' it says 'misleading and
 > largely useless'
 
 And indeed, that's what we ALREADY say, except you didn't read it.
 To wit:
 
 	Some machines never actually require alignment; they allow
 	reference to any data type even at an odd addresses. For
 	these machines, __alignof__ reports the recommended alignment
 	of a type.
 
 
 r~


             reply	other threads:[~2003-04-10  8:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-10  8:06 Richard Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-10  5:16 Richard Frith-Macdonald
2003-04-09 22:46 Richard Henderson
2003-04-09 22:06 Frederic De Jaeger
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=20030410080601.12168.qmail@sources.redhat.com \
    --to=rth@redhat.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).