diff options
| author | Chandler Carruth <chandlerc@gmail.com> | 2019-01-22 10:29:58 +0000 |
|---|---|---|
| committer | Chandler Carruth <chandlerc@gmail.com> | 2019-01-22 10:29:58 +0000 |
| commit | 285fe716c54caf8c12018365fc3657851ff7d1e3 (patch) | |
| tree | 224746a253ab1176ccf619dc2650550d05750a8c /llvm/test/Bitcode | |
| parent | 33c16a3f16fa56ad945e086af669760e0b80d8c7 (diff) | |
| download | bcm5719-llvm-285fe716c54caf8c12018365fc3657851ff7d1e3.tar.gz bcm5719-llvm-285fe716c54caf8c12018365fc3657851ff7d1e3.zip | |
Revert r351778: IR: Add fp operations to atomicrmw
This broke the RISCV build, and even with that fixed, one of the RISCV
tests behaves surprisingly differently with asserts than without,
leaving there no clear test pattern to use. Generally it seems bad for
hte IR to differ substantially due to asserts (as in, an alloca is used
with asserts that isn't needed without!) and nothing I did simply would
fix it so I'm reverting back to green.
This also required reverting the RISCV build fix in r351782.
llvm-svn: 351796
Diffstat (limited to 'llvm/test/Bitcode')
| -rw-r--r-- | llvm/test/Bitcode/compatibility.ll | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/llvm/test/Bitcode/compatibility.ll b/llvm/test/Bitcode/compatibility.ll index 3c5e86eee01..320ed831db3 100644 --- a/llvm/test/Bitcode/compatibility.ll +++ b/llvm/test/Bitcode/compatibility.ll @@ -764,13 +764,6 @@ define void @atomics(i32* %word) { define void @fp_atomics(float* %word) { ; CHECK: %atomicrmw.xchg = atomicrmw xchg float* %word, float 1.000000e+00 monotonic %atomicrmw.xchg = atomicrmw xchg float* %word, float 1.0 monotonic - -; CHECK: %atomicrmw.fadd = atomicrmw fadd float* %word, float 1.000000e+00 monotonic - %atomicrmw.fadd = atomicrmw fadd float* %word, float 1.0 monotonic - -; CHECK: %atomicrmw.fsub = atomicrmw fsub float* %word, float 1.000000e+00 monotonic - %atomicrmw.fsub = atomicrmw fsub float* %word, float 1.0 monotonic - ret void } |
