Philip Reames d2d22a2dd9 Allow value forwarding past release fences in EarlyCSE ... A release fence acts as a publication barrier for stores within the current thread to become visible to other threads which might observe the release fence. It does not require the current thread to observe stores performed on other threads. As a result, we can allow store-load and load-store forwarding across a release fence. We do need to make sure that stores before the fence can't be eliminated even if there's another store to the same location after the fence. In theory, we could reorder the second store above the fence and *then* eliminate the former, but we can't do this if the stores are on opposite sides of the fence. Note: While more aggressive then what's there, this patch is still implementing a really conservative ordering. In particular, I'm not trying to exploit undefined behavior via races, or the fact that the LangRef says only 'atomic' accesses are ordered w.r.t. fences. Differential Revision: http://reviews.llvm.org/D11434 llvm-svn: 246134		2015-08-27 01:32:33 +00:00
..
Hello
InstCombine	Re-apply r245635, "[InstCombine] Transform A & (L - 1) u< L --> L != 0"	2015-08-21 22:22:37 +00:00
Instrumentation	Make variable argument intrinsics behave correctly in a Win64 CC function.	2015-08-25 23:27:41 +00:00
IPO	Fix memory leak in sample profile pass.	2015-08-26 20:00:27 +00:00
ObjCARC	[ARC] Pull the ObjC ARC components that really serve the role of	2015-08-20 08:06:03 +00:00
Scalar	Allow value forwarding past release fences in EarlyCSE	2015-08-27 01:32:33 +00:00
Utils	[SimplifyCFG] Prune code from a provably unreachable switch default	2015-08-26 23:56:46 +00:00
Vectorize	Improved printing of analysis diagnostics in the loop vectorizer.	2015-08-27 01:02:04 +00:00
CMakeLists.txt
LLVMBuild.txt
Makefile