| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <AANLkTimu_VtGnNO-ySeCCE9A0fuof6GkMPUYJ65T2sCR@mail.gmail.com> Date: Sat, 12 Feb 2011 13:29:00 -0800 From: "H.J. Lu" <hjl.tools@...il.com> To: Florian Weimer <fw@...eb.enyo.de> Cc: GCC Development <gcc@....gnu.org>, GNU C Library <libc-alpha@...rceware.org>, LKML <linux-kernel@...r.kernel.org>, x32-abi@...glegroups.com Subject: Re: X32 psABI status On Sat, Feb 12, 2011 at 1:10 PM, Florian Weimer <fw@...eb.enyo.de> wrote: > * H. J. Lu: > >> We made lots of progresses on x32 pABI: >> >> https://sites.google.com/site/x32abi/ >> >> 1. Kernel interface with syscall is close to be finalized. >> 2. GCC x32 branch is stabilizing. >> 3. The Bionic C library works with the syscall kernel interface. >> >> The next major milestone will be x32 glibc port. > > It is a bit difficult to extract useful information from these > resources. That is true. Contributions are more than welcome. > Is off_t 32 bits? Why is the ia32 compatiblity kernel interface used? Yes. > I'm sure a lot of people want to get rid of that in cases where they > control the whole software stack. That is debatable. The current thought is the x32 user space API is the same as is ia32. time_t is also an issue. > Is stack alignment to 16 bytes beneficial for X32? > Even ia32 uses 16byte stack alignment and we will make it official soon via an amendment to the i386 psABI. -- H.J. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists