lkml.org 
[lkml]   [2010]   [Dec]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [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.



    \
     
     \ /
      Last update: 2010-12-20 22:55    [W:0.018 / U:1.276 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site