0aef747b84
The motivation is that the update script has at least two deviations (`<...>@GOT`/`<...>@PLT`/ and not hiding pointer arithmetics) from what pretty much all the checklines were generated with, and most of the tests are still not updated, so each time one of the non-up-to-date tests is updated to see the effect of the code change, there is a lot of noise. Instead of having to deal with that each time, let's just deal with everything at once. This has been done via: ``` cd llvm-project/llvm/test/CodeGen/X86 grep -rl "; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py" | xargs -L1 <...>/llvm-project/llvm/utils/update_llc_test_checks.py --llc-binary <...>/llvm-project/build/bin/llc ``` Not all tests were regenerated, however.
25 lines
929 B
LLVM
25 lines
929 B
LLVM
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
|
|
; RUN: llc < %s -mtriple=x86_64-pc-linux-gnu | FileCheck %s
|
|
|
|
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
|
|
target triple = "x86_64-pc-linux-gnu"
|
|
|
|
define i64 @PR30511(<2 x double> %a) {
|
|
; CHECK-LABEL: PR30511:
|
|
; CHECK: # %bb.0:
|
|
; CHECK-NEXT: addpd {{\.?LCPI[0-9]+_[0-9]+}}(%rip), %xmm0
|
|
; CHECK-NEXT: cvtdq2pd %xmm0, %xmm0
|
|
; CHECK-NEXT: mulsd {{\.?LCPI[0-9]+_[0-9]+}}(%rip), %xmm0
|
|
; CHECK-NEXT: movq %xmm0, %rax
|
|
; CHECK-NEXT: retq
|
|
%1 = fadd <2 x double> %a, <double 0x4338000000000000, double 0x4338000000000000>
|
|
%2 = bitcast <2 x double> %1 to <2 x i64>
|
|
%3 = trunc <2 x i64> %2 to <2 x i32>
|
|
%4 = sitofp <2 x i32> %3 to <2 x double>
|
|
%5 = fmul <2 x double> %4, <double 0x3E76800000000000, double 0x3E76800000000000>
|
|
%6 = extractelement <2 x double> %5, i32 0
|
|
%7 = bitcast double %6 to i64
|
|
ret i64 %7
|
|
}
|
|
|