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: Mon, 20 Dec 2010 13:52:46 -0800 From: Stephen Boyd <sboyd@...eaurora.org> To: Arnaud Lacombe <lacombar@...il.com> CC: Greg Kroah-Hartman <gregkh@...e.de>, linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, Tony Lindgren <tony@...mide.com>, Arnd Bergmann <arnd@...db.de>, Nicolas Pitre <nicolas.pitre@...aro.org>, Daniel Walker <dwalker@...eaurora.org> Subject: Re: [PATCH 1/3] hvc_dcc: Fix bad code generation by marking assembly volatile On 12/20/2010 01:49 PM, Arnaud Lacombe wrote: > Hi, > > On Mon, Dec 20, 2010 at 3:08 PM, Stephen Boyd <sboyd@...eaurora.org> wrote: >> Without marking the asm __dcc_getstatus() volatile my compiler >> decides [...] > What compiler ? That might be a usefull information to know, > espectially 5 years from now when tracing code history. There has been > similar issue with gcc 4.5 recently. AFAIK, in the same idea, the > final change has been to mark the asm volatile. Sure, we can replace "my compiler" with "my compiler (arm-eabi-gcc (GCC) 4.4.0)". -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- 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