public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Meissner <meissner@cygnus.com>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: dje@watson.ibm.com, gcc@gcc.gnu.org
Subject: Re: *more* alignment problems
Date: Thu, 30 Mar 2000 13:48:00 -0000	[thread overview]
Message-ID: <20000330164803.16818@cse.cygnus.com> (raw)
In-Reply-To: <10003302126.AA05670@vlsi1.ultra.nyu.edu>

On Mon, Mar 30, 1970 at 04:26:33PM -0500, Richard Kenner wrote:
>     Because all of those bitfield functions were manipulating alignment in
>     bytes, the SLOW_UNALIGNED_ACCESS macro expects the alignment to be
>     bytes.  The primary question for SLOW_UNALIGNED_ACCESS is whether the
>     alignment is less than the natural alignment for the type, usually in
>     granularity of bytes, not bits.
> 
> Why does it matter which way it's defined?  I changed the macro in
> rs6000.h to accept bits.

As long as the macro in question will never need to deal with anything that is
larger than 1/8 of the address space.

-- 
Michael Meissner, Cygnus Solutions, a Red Hat company.
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work:	  meissner@redhat.com		phone: +1 978-486-9304
Non-work: meissner@spectacle-pond.org	fax:   +1 978-692-4482

  parent reply	other threads:[~2000-03-30 13:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-30 13:16 Richard Kenner
2000-03-30 13:21 ` David Edelsohn
2000-03-30 13:48 ` Michael Meissner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-30 13:40 Richard Kenner
2000-03-30 13:49 ` Chip Salzenberg
2000-03-30 13:06 Richard Kenner
2000-03-30 13:14 ` David Edelsohn
2000-03-30 13:22 ` Chip Salzenberg
2000-03-30 12:48 Jeffrey A Law

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=20000330164803.16818@cse.cygnus.com \
    --to=meissner@cygnus.com \
    --cc=dje@watson.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    /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).