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 with any argument you might pass. IOW, if you pass a plain "char *" then the compiler will promote it to "volatile char *" and not complain, and passing an already volatile pointer will be OK too. The volatile isn't there to modify the generated code in any way. J -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/