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
| ||
|
Date: Thu, 06 Mar 2008 09:06:50 -0800 From: "H. Peter Anvin" <hpa@...or.com> To: "H.J. Lu" <hjl.tools@...il.com> CC: Jakub Jelinek <jakub@...hat.com>, NightStrike <nightstrike@...il.com>, Olivier Galibert <galibert@...ox.com>, Chris Lattner <clattner@...le.com>, Michael Matz <matz@...e.de>, Richard Guenther <richard.guenther@...il.com>, Joe Buck <Joe.Buck@...opsys.com>, Jan Hubicka <hubicka@....cz>, Aurelien Jarno <aurelien@...el32.net>, linux-kernel@...r.kernel.org, gcc@....gnu.org Subject: Re: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI wrt direction flag H.J. Lu wrote: > On Thu, Mar 6, 2008 at 8:23 AM, Jakub Jelinek <jakub@...hat.com> wrote: >> On Thu, Mar 06, 2008 at 07:50:12AM -0800, H. Peter Anvin wrote: >> > H.J. Lu wrote: >> > >I agree with it. There is no right or wrong here Let's start from >> > >scratch and figure out >> > >what is the best way to handle this, assuming we are defining a new psABI. >> >> BTW, just tested icc and icc doesn't generate cld either (so it matches the >> new gcc behavior). >> char buf1[32], buf2[32]; >> void bar (void); >> void foo (void) >> { >> __builtin_memset (buf1, 0, 32); >> bar (); >> __builtin_memset (buf2, 0, 32); >> } >> > > Icc follows the psABI. If we are saying icc/gcc 4.3 need a fix, we'd > better define > a new psABI first. > Not a fix, an (optional) workaround for a system bug. -hpa -- 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