{"push_id":556528276,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"a1d976341c007cfb51e2d82111f1facce9912f82","before":"2f791e071304cfbaab4512d7ae93daa47c43703c","commits":[{"sha":"a1d976341c007cfb51e2d82111f1facce9912f82","author":{"email":"1a6d70c497b881333962fb40612e3f3827d7c1cd@philipreames.com","name":"Philip Reames"},"message":"Refine memory dependence's notion of volatile semantics\n\nAccording to my reading of the LangRef, volatiles are only ordered with respect to other volatiles. It is entirely legal and profitable to forward unrelated loads over the volatile load. This patch implements this for GVN by refining the transition rules MemoryDependenceAnalysis uses when encountering a volatile.\n\nThe added test cases show where the extra flexibility is profitable for local dependence optimizations. I have a related change (227110) which will extend this to non-local dependence (i.e. PRE), but that's essentially orthogonal to the semantic change in this patch. I have tested the two together and can confirm that PRE works over a volatile load with both changes.  I will be submitting a PRE w/volatiles test case seperately in the near future.\n\nDifferential Revision: http://reviews.llvm.org/D6901","distinct":true,"url":"https://api.github.com/repos/llvm-project/llvm-project/commits/a1d976341c007cfb51e2d82111f1facce9912f82"}]}