diff options
| author | Richard Sandiford <rsandifo@linux.vnet.ibm.com> | 2013-05-31 13:25:22 +0000 |
|---|---|---|
| committer | Richard Sandiford <rsandifo@linux.vnet.ibm.com> | 2013-05-31 13:25:22 +0000 |
| commit | b6606e46abad12a112a57048caec2142522bc67d (patch) | |
| tree | 1f4b77d559242b7a3b7a40cd31bf7726206e71bc /test/TableGen/Include.inc | |
| parent | 5443e7d79044f3198f2da044f1b389b40d9bea6f (diff) | |
| download | external_llvm-b6606e46abad12a112a57048caec2142522bc67d.zip external_llvm-b6606e46abad12a112a57048caec2142522bc67d.tar.gz external_llvm-b6606e46abad12a112a57048caec2142522bc67d.tar.bz2 | |
[SystemZ] Don't use LOAD and STORE REVERSED for volatile accesses
Unlike most -- hopefully "all other", but I'm still checking -- memory
instructions we support, LOAD REVERSED and STORE REVERSED may access
the memory location several times. This means that they are not suitable
for volatile loads and stores.
This patch is a prerequisite for better atomic load and store support.
The same principle applies there: almost all memory instructions we
support are inherently atomic ("block concurrent"), but LOAD REVERSED
and STORE REVERSED are exceptions.
Other instructions continue to allow volatile operands. I will add
positive "allows volatile" tests at the same time as the "allows atomic
load or store" tests.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@183002 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'test/TableGen/Include.inc')
0 files changed, 0 insertions, 0 deletions