"J.A. Magallón" <[EMAIL PROTECTED]> writes: > That's what __attribute__ ((pure)) is for, but if none of the > functions is pure, the compiler can not be sure about side effects > and can not reorder things. Don't forget that functions can do > anything apart from mangling with their arguments.
Though it seems it could legally transform: void kfree(const int *x); { int v, *ptr = malloc(sizeof(int)); *ptr = 51; v = *ptr; kfree(ptr); printf("%d", v); into: { int v, *ptr = malloc(sizeof(int)); *ptr = 51; kfree(ptr); v = *ptr; printf("%d", v); } if it knows that malloc generates unaliased pointers, which seems reasonable in general. -- Krzysztof Halasa -- 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/