On 05/20/2015 04:46 PM, Will Deacon wrote: > I'm not sure... you'd require the compiler to perform static analysis of > loops to determine the state of the machine when they exit (if they exit!) > in order to show whether or not a dependency is carried to subsequent > operations. If it can't prove otherwise, it would have to assume that a > dependency *is* carried, and it's not clear to me how it would use this > information to restrict any subsequent dependency removing optimisations. It'd just convert consume to acquire. Andrew. -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
