Re: [PATCH 1/3] hvc_dcc: Fix bad code generation by marking assembly volatile

From: Arnaud Lacombe
Date: Mon Dec 20 2010 - 16:49:59 EST


Hi,

On Mon, Dec 20, 2010 at 3:08 PM, Stephen Boyd <sboyd@xxxxxxxxxxxxxx> 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.

Thanks,
- Arnaud
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/