Richard Sandiford 086791eca2 Add TargetLowering::prepareVolatileOrAtomicLoad ... One unusual feature of the z architecture is that the result of a previous load can be reused indefinitely for subsequent loads, even if a cache-coherent store to that location is performed by another CPU. A special serializing instruction must be used if you want to force a load to be reattempted. Since volatile loads are not supposed to be omitted in this way, we should insert a serializing instruction before each such load. The same goes for atomic loads. The patch implements this at the IR->DAG boundary, in a similar way to atomic fences. It is a no-op for targets other than SystemZ. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@196905 91177308-0d34-0410-b5e6-96231b3b80d8		2013-12-10 10:36:34 +00:00
..
branch-range-01.py	Add TargetLowering::prepareVolatileOrAtomicLoad	2013-12-10 10:36:34 +00:00
branch-range-02.py	Add TargetLowering::prepareVolatileOrAtomicLoad	2013-12-10 10:36:34 +00:00
branch-range-03.py	Add TargetLowering::prepareVolatileOrAtomicLoad	2013-12-10 10:36:34 +00:00
branch-range-04.py	Add TargetLowering::prepareVolatileOrAtomicLoad	2013-12-10 10:36:34 +00:00
branch-range-05.py	Add TargetLowering::prepareVolatileOrAtomicLoad	2013-12-10 10:36:34 +00:00
branch-range-06.py	Add TargetLowering::prepareVolatileOrAtomicLoad	2013-12-10 10:36:34 +00:00
branch-range-07.py
branch-range-08.py
branch-range-09.py	Add TargetLowering::prepareVolatileOrAtomicLoad	2013-12-10 10:36:34 +00:00
branch-range-10.py	Add TargetLowering::prepareVolatileOrAtomicLoad	2013-12-10 10:36:34 +00:00
branch-range-11.py	Add TargetLowering::prepareVolatileOrAtomicLoad	2013-12-10 10:36:34 +00:00
branch-range-12.py	Add TargetLowering::prepareVolatileOrAtomicLoad	2013-12-10 10:36:34 +00:00
lit.local.cfg
spill-01.py
spill-02.py