public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: David Vrabel <dvrabel@arcom.com>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net, oliver@neukum.org
Subject: Re: [linux-usb-devel] Re: need for packed attribute
Date: Thu, 12 Jan 2006 17:34:13 +0000	[thread overview]
Message-ID: <20060112173413.GD9288@flint.arm.linux.org.uk> (raw)
In-Reply-To: <43C69067.9040206@arcom.com>

On Thu, Jan 12, 2006 at 05:22:47PM +0000, David Vrabel wrote:
> Russell King wrote:
> > BTW, it's worth noting that the new EABI stuff has it's own set of
> > problems.  We have r0 to r6 to pass 32-bit or 64-bit arguments.
> > With EABI, 64-bit arguments will be aligned to an _even_ numbered
> > register.
> 
> Is there a reason for this alignment requirement?

I think it comes from the 64-bit accessing instructions (ldrd/strd)
having the restriction that they only take an even numbered 32-bit
register.  The immediately consecutive higher numbered 32-bit 
egister is used as the other half of the number.

Think about it as the x86 32-bit eax register being made up of
16-bit ah and al registers.  Only we call then r0, r1 etc not
eax, ah and al (and they're twice the size.)

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2006-01-12 17:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12 12:27 need for packed attribute Mikael Pettersson
2006-01-12 13:47 ` Russell King
2006-01-12 13:53   ` Russell King
2006-01-12 16:30   ` Mikael Pettersson
2006-01-12 16:46     ` Russell King
2006-01-12 17:22       ` [linux-usb-devel] " David Vrabel
2006-01-12 17:34         ` Russell King [this message]
2006-01-12 17:20 ` Pete Zaitcev
2006-01-12 17:26   ` Russell King
2006-01-12 17:36     ` Pete Zaitcev
2006-01-12 19:35   ` [linux-usb-devel] " David Brownell

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=20060112173413.GD9288@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=dvrabel@arcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=mikpe@csd.uu.se \
    --cc=oliver@neukum.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