summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorThomas Lively <tlively@google.com>2018-11-09 22:04:37 +0000
committerThomas Lively <tlively@google.com>2018-11-09 22:04:37 +0000
commit97bef83690f716ef1b1cb94ef0a1ff62ec3741b3 (patch)
treed383cd3b53754bbc2453557452134b59d2b6d0af
parent771d6d37cad492a16538e6339d1cafeb80a4e7c0 (diff)
downloadbcm5719-llvm-97bef83690f716ef1b1cb94ef0a1ff62ec3741b3.tar.gz
bcm5719-llvm-97bef83690f716ef1b1cb94ef0a1ff62ec3741b3.zip
[WebAssembly] Disable custom NaN payload tests
Summary: These tests fail on 32-bit builds because NaN payload bits in floating point immediates are not necessarily preserved through compilation. This is because the MC layer uses native doubles to store these values. The tests will be reenabled once this problem has been fixed or deleted if we decide we don't care about lowering payload bits. Reviewers: aheejin, dschuff Subscribers: sbc100, jgravelle-google, sunfish, llvm-commits Differential Revision: https://reviews.llvm.org/D54353 llvm-svn: 346558
-rw-r--r--llvm/test/CodeGen/WebAssembly/immediates.ll34
1 files changed, 19 insertions, 15 deletions
diff --git a/llvm/test/CodeGen/WebAssembly/immediates.ll b/llvm/test/CodeGen/WebAssembly/immediates.ll
index fdb7df7d21c..0c96365102d 100644
--- a/llvm/test/CodeGen/WebAssembly/immediates.ll
+++ b/llvm/test/CodeGen/WebAssembly/immediates.ll
@@ -216,18 +216,22 @@ define double @neginf_f64() {
ret double 0xFFF0000000000000
}
-; CHECK-LABEL: custom_nan_f64:
-; CHECK-NEXT: .result f64{{$}}
-; CHECK-NEXT: f64.const $push[[NUM:[0-9]+]]=, -nan:0xabcdef0123456{{$}}
-; CHECK-NEXT: return $pop[[NUM]]{{$}}
-define double @custom_nan_f64() {
- ret double 0xFFFABCDEF0123456
-}
-
-; CHECK-LABEL: custom_nans_f64:
-; CHECK-NEXT: .result f64{{$}}
-; CHECK-NEXT: f64.const $push[[NUM:[0-9]+]]=, -nan:0x2bcdef0123456{{$}}
-; CHECK-NEXT: return $pop[[NUM]]{{$}}
-define double @custom_nans_f64() {
- ret double 0xFFF2BCDEF0123456
-}
+;; Custom NaN playloads are currently not always preserved because of the use of
+;; native doubles in the MC layer. TODO: fix this problem or decide we don't
+;; care about preserving NaN payloads.
+
+; XXX-CHECK-LABEL: custom_nan_f64:
+; XXX-CHECK-NEXT: .result f64{{$}}
+; XXX-CHECK-NEXT: f64.const $push[[NUM:[0-9]+]]=, -nan:0xabcdef0123456{{$}}
+; XXX-CHECK-NEXT: return $pop[[NUM]]{{$}}
+; define double @custom_nan_f64() {
+; ret double 0xFFFABCDEF0123456
+; }
+
+; XXX-CHECK-LABEL: custom_nans_f64:
+; XXX-CHECK-NEXT: .result f64{{$}}
+; XXX-CHECK-NEXT: f64.const $push[[NUM:[0-9]+]]=, -nan:0x2bcdef0123456{{$}}
+; XXX-CHECK-NEXT: return $pop[[NUM]]{{$}}
+; define double @custom_nans_f64() {
+; ret double 0xFFF2BCDEF0123456
+; }
OpenPOWER on IntegriCloud