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: Fri, 17 Mar 2017 13:08:55 +0100 From: Peter Zijlstra <peterz@...radead.org> To: Michael Davidson <md@...gle.com> Cc: Michal Marek <mmarek@...e.com>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, Herbert Xu <herbert@...dor.apana.org.au>, "David S. Miller" <davem@...emloft.net>, Shaohua Li <shli@...nel.org>, Alexander Potapenko <glider@...gle.com>, Dmitry Vyukov <dvyukov@...gle.com>, Matthias Kaehlcke <mka@...omium.org>, x86@...nel.org, linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org, linux-raid@...r.kernel.org Subject: Re: [PATCH 5/7] x86, boot, LLVM: Use regparm=0 for memcpy and memset On Thu, Mar 16, 2017 at 05:15:18PM -0700, Michael Davidson wrote: > Use the standard regparm=0 calling convention for memcpy and > memset when building with clang. > > This is a work around for a long standing clang bug > (see https://llvm.org/bugs/show_bug.cgi?id=3997) where > clang always uses the standard regparm=0 calling convention > for any implcit calls to memcpy and memset that it generates > (eg for structure assignments and initialization) even if an > alternate calling convention such as regparm=3 has been specified. Seriously, fix LLVM already.
Powered by blists - more mailing lists