| 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: <AANLkTimk3dfOBoPhGQ8NeOYY5rKdsefPm8gTJ-75vg3-@mail.gmail.com> Date: Tue, 15 Mar 2011 21:51:37 -0700 From: "H.J. Lu" <hjl.tools@...il.com> To: Mike Frysinger <vapier@...too.org> Cc: libc-alpha@...rceware.org, GCC Development <gcc@....gnu.org>, LKML <linux-kernel@...r.kernel.org>, x32-abi@...glegroups.com Subject: Re: X32 psABI status update On Tue, Mar 15, 2011 at 9:30 PM, Mike Frysinger <vapier@...too.org> wrote: > On Wednesday, March 16, 2011 00:17:04 H.J. Lu wrote: >> On Mon, Mar 7, 2011 at 1:33 PM, Mike Frysinger wrote: >> > On Saturday, March 05, 2011 14:08:04 H.J. Lu wrote: >> >> Many x32 bugs are fixed in kernel, glibc, binutils and GCC: >> >> >> >> https://sites.google.com/site/x32abi/ >> >> >> >> The major remaining issues are glibc/gcc testsuite failures, >> >> kernel core dump and signal handler unwind. >> > >> > are you getting a unique host tuple for this ? or are you extending >> > x86_64- linux-gnu ? so the only way of knowing which ABI is to check >> > for the output of the compiler+compiler flags ? >> >> x32 requires x32 enabled x86-64 kernel. > > ok, but that doesnt answer my question. what are you passing to --target ? See: https://sites.google.com/site/x32abi/ You configure it as CC="gcc -mx32" ...../configure x86_64- linux-gnu -- 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