From: "H. Peter Anvin" <hpa@zytor.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Paul Mackerras <paulus@samba.org>, klibc list <klibc@zytor.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [klibc] Re: long long on 32-bit machines
Date: Sat, 31 Jan 2004 11:41:33 -0800 [thread overview]
Message-ID: <401C04ED.4010109@zytor.com> (raw)
In-Reply-To: <200401311323.40399.arnd@arndb.de>
Arnd Bergmann wrote:
> On Saturday 31 January 2004 07:08, H. Peter Anvin wrote:
>
>>Does system calls follow the same convention?
>
>
> I have just looked up in glibc what architectures need this kind
> of handling and found that there is no easy rule. The good news
> is that none of (hppa m68k s390 sparc x86_64 alpha cris i386 sparc64
> arm ia64) are doing this.
>
> AFAICS, the padding is done for exactly these system calls:
>
> ppc: truncate64, ftruncate64, pread64, pwrite64
> mips: truncate64, ftruncate64, pread64, pwrite64
> sh: pread64, pwrite64
>
> fadvise64_64 is another story:
> mips does no padding, ppc32 reorders the arguments (int fd, int advise,
> off64_t offset, off64_t len) and s390 passes a struct, for the
> reason Uli already explained.
>
<BARF>
I hate ad hockery :( Yet more evidence for the need of a formal
description of the ABI in the kernel.
-hpa
next prev parent reply other threads:[~2004-01-31 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 18:04 long long on 32-bit machines H. Peter Anvin
2004-01-28 19:12 ` Timothy Miller
2004-01-28 19:15 ` David S. Miller
2004-01-29 11:02 ` Paul Mackerras
2004-01-31 6:08 ` H. Peter Anvin
2004-01-31 12:23 ` [klibc] " Arnd Bergmann
2004-01-31 19:41 ` H. Peter Anvin [this message]
2004-02-01 0:41 ` Paul Mackerras
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=401C04ED.4010109@zytor.com \
--to=hpa@zytor.com \
--cc=arnd@arndb.de \
--cc=klibc@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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