Add TargetLowering::prepareVolatileOrAtomicLoad
authorRichard Sandiford <rsandifo@linux.vnet.ibm.com>
Tue, 10 Dec 2013 10:49:34 +0000 (10:49 +0000)
committerRichard Sandiford <rsandifo@linux.vnet.ibm.com>
Tue, 10 Dec 2013 10:49:34 +0000 (10:49 +0000)
commitaedb288d864bf20a708cca580fa87ac848389f79
tree433a286e31fa441c4784a9d1b95ce1eb49e97032
parent086791eca2260c03c7bbdd37a53626d16656f0ca
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@196906 91177308-0d34-0410-b5e6-96231b3b80d8
15 files changed:
lib/Target/SystemZ/README.txt
lib/Target/SystemZ/SystemZISelLowering.cpp
lib/Target/SystemZ/SystemZISelLowering.h
test/CodeGen/SystemZ/atomic-load-01.ll
test/CodeGen/SystemZ/atomic-load-02.ll
test/CodeGen/SystemZ/atomic-load-03.ll
test/CodeGen/SystemZ/atomic-load-04.ll
test/CodeGen/SystemZ/atomic-store-01.ll
test/CodeGen/SystemZ/atomic-store-02.ll
test/CodeGen/SystemZ/atomic-store-03.ll
test/CodeGen/SystemZ/atomic-store-04.ll
test/CodeGen/SystemZ/cond-store-01.ll
test/CodeGen/SystemZ/cond-store-02.ll
test/CodeGen/SystemZ/cond-store-03.ll
test/CodeGen/SystemZ/cond-store-04.ll