Messages in this thread | | | Date | Mon, 20 Dec 2010 13:52:46 -0800 | From | Stephen Boyd <> | 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@codeaurora.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.
| |