From: Jakub Jelinek <jakub@redhat.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
binutils@sourceware.org, gcc@gcc.gnu.org,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: RFC: Add 32bit x86-64 support to binutils
Date: Thu, 30 Dec 2010 20:02:00 -0000 [thread overview]
Message-ID: <20101230195759.GU16156@tyan-ft48-01.lab.bos.redhat.com> (raw)
In-Reply-To: <AANLkTikpMu3vyYBrsk_r0aHF5_O_xeshbdSfu+igjjpn@mail.gmail.com>
On Thu, Dec 30, 2010 at 08:53:32PM +0100, Richard Guenther wrote:
> > Syscalls sometimes need three different versions in the kernel; sometimes
> > the wrong version gets put in the n32 syscall table. Â Special syscall
> > wrappers are often needed in glibc; although for most purposes the glibc
> > port is a 32-bit one, including having separate functions for 32-bit and
> > 64-bit off_t, syscalls tend to need to be called in the 64-bit way (long
> > long values as single arguments, in particular).
>
> Would be nice if LFS would be mandatory on the new ABI, thus
> off_t being 64bits.
And avoid ambiguous cases that x86-64 ABI has, e.g. whether
caller or callee is responsible for sign/zero extension of arguments, to
avoid the need to sign/zero extend twice, etc.
Jakub
next prev parent reply other threads:[~2010-12-30 19:58 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 18:42 H.J. Lu
2010-12-30 18:59 ` Joseph S. Myers
2010-12-30 19:04 ` H.J. Lu
2010-12-30 19:31 ` H. Peter Anvin
2010-12-30 19:34 ` Joseph S. Myers
2010-12-30 19:53 ` H.J. Lu
2010-12-30 20:12 ` H.J. Lu
2010-12-30 20:27 ` H.J. Lu
2011-01-03 10:41 ` Jan Beulich
2011-01-04 17:57 ` H.J. Lu
2011-01-04 18:35 ` H. Peter Anvin
2011-01-04 20:03 ` Jakub Jelinek
2011-01-05 7:46 ` Jan Beulich
2011-01-05 8:01 ` H. Peter Anvin
2011-01-05 8:20 ` Jan Beulich
2010-12-30 19:58 ` Richard Guenther
2010-12-30 20:02 ` Jakub Jelinek [this message]
2010-12-30 22:19 ` H. Peter Anvin
2010-12-31 11:01 ` Jakub Jelinek
2010-12-31 14:51 ` H.J. Lu
2010-12-31 17:03 ` H.J. Lu
2010-12-31 18:43 ` H.J. Lu
2010-12-31 22:31 ` H. Peter Anvin
2010-12-30 20:13 ` H. Peter Anvin
2010-12-30 20:39 ` Joseph S. Myers
2010-12-30 22:23 ` Robert Millan
2010-12-30 23:00 ` H. Peter Anvin
2010-12-31 0:26 ` Joseph S. Myers
2010-12-31 0:37 ` H.J. Lu
2010-12-31 0:42 ` H.J. Lu
2010-12-30 21:17 ` Robert Millan
2010-12-30 21:33 ` H. Peter Anvin
2010-12-30 21:41 ` H.J. Lu
2010-12-30 22:21 ` Robert Millan
2010-12-30 22:26 ` H.J. Lu
2010-12-30 22:27 ` H. Peter Anvin
2010-12-31 0:48 ` H. Peter Anvin
2010-12-31 1:11 ` H.J. Lu
2010-12-31 15:00 ` H.J. Lu
2011-01-14 23:47 ` H.J. Lu
2011-01-15 21:01 ` H.J. Lu
2010-12-30 19:40 ` David Daney
2010-12-30 20:27 ` H. Peter Anvin
2010-12-30 20:29 ` David Daney
2010-12-30 20:31 ` H.J. Lu
2010-12-30 21:08 ` David Daney
2010-12-30 21:42 ` H. Peter Anvin
2010-12-30 21:32 ` H. Peter Anvin
2010-12-31 1:16 ` Hans-Peter Nilsson
2010-12-31 2:44 ` Hans-Peter Nilsson
2010-12-31 10:04 ` H.J. Lu
2011-01-05 19:52 ` Jonathan Wakely
2011-01-05 21:36 ` H.J. Lu
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=20101230195759.GU16156@tyan-ft48-01.lab.bos.redhat.com \
--to=jakub@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=joseph@codesourcery.com \
--cc=richard.guenther@gmail.com \
/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).