Re: [PATCH 1/9] remove volatile keyword from clflush.

Glauber de Oliveira Costa wrote: > the p parameter is an explicit memory reference, and is > enough to prevent gcc to being nasty here. The volatile > seems completely not needed. > The usual reason for these types of "volatiles" is to make type checking happier, since "volatile void *" is

Re: [PATCH 1/9] remove volatile keyword from clflush.

Glauber de Oliveira Costa wrote: the p parameter is an explicit memory reference, and is enough to prevent gcc to being nasty here. The volatile seems completely not needed. The usual reason for these types of volatiles is to make type checking happier, since volatile void * is compatible

[PATCH 1/9] remove volatile keyword from clflush.

the p parameter is an explicit memory reference, and is enough to prevent gcc to being nasty here. The volatile seems completely not needed. Signed-off-by: Glauber de Oliveira Costa <[EMAIL PROTECTED]> --- include/asm-x86/system_32.h |2 +- 1 files changed, 1 insertions(+), 1 deletions(-)

[PATCH 1/9] remove volatile keyword from clflush.

the p parameter is an explicit memory reference, and is enough to prevent gcc to being nasty here. The volatile seems completely not needed. Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED] --- include/asm-x86/system_32.h |2 +- 1 files changed, 1 insertions(+), 1 deletions(-)