From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net, oliver@neukum.org
Subject: Re: need for packed attribute
Date: Thu, 12 Jan 2006 16:46:21 +0000 [thread overview]
Message-ID: <20060112164621.GA9288@flint.arm.linux.org.uk> (raw)
In-Reply-To: <17350.33811.433595.750615@alkaid.it.uu.se>
On Thu, Jan 12, 2006 at 05:30:11PM +0100, Mikael Pettersson wrote:
> OK, thanks for this info. It means that GCC is the definitive authority
> on calling conventions and data layouts, not the AAPCS; I wasn't aware of
> that before.
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. Hence:
long sys_foo(int a, long long b, int c, long long d);
will result in the following register layouts:
EABI Current
r0 a a
r1 unused \_ b
r2 \_ b /
r3 / c
r4 c \_ d
r5 /
r6 ... out of space for 'd' ... room for one other int.
r7 syscall number
and as such will be uncallable with this argument ordering for EABI.
We've already had to sanitise sys_fadvise64_64() because of this.
So, I forsee more problems appearing with EABI, not less. ;(
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-01-12 16:46 UTC|newest]
Thread overview: 14+ 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 [this message]
2006-01-12 17:22 ` [linux-usb-devel] " David Vrabel
2006-01-12 17:34 ` Russell King
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
-- strict thread matches above, loose matches on Subject: below --
2006-01-06 18:15 Oliver Neukum
2006-01-06 18:38 ` Russell King
2006-01-12 18:32 ` Benjamin LaHaise
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=20060112164621.GA9288@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--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