maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/CodeGen/X86/pr30511.ll

25 lines
893 B
LLVM
Raw Normal View History

[X86] Regenerate test. llvm-svn: 289438
2016-12-12 23:47:53 +08:00
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
[X86] Add test case for PR30511 and r282341. llvm-svn: 282473
2016-09-27 14:44:30 +08:00
; 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) {
[X86] Regenerate test. llvm-svn: 289438
2016-12-12 23:47:53 +08:00
; CHECK-LABEL: PR30511:
[CodeGen] Unify MBB reference format in both MIR and debug output As part of the unification of the debug format and the MIR format, print MBB references as '%bb.5'. The MIR printer prints the IR name of a MBB only for block definitions. * find . \( -name "*.mir" -o -name "*.cpp" -o -name "*.h" -o -name "*.ll" \) -type f -print0 | xargs -0 sed -i '' -E 's/BB#" << ([a-zA-Z0-9_]+)->getNumber\(\)/" << printMBBReference(*\1)/g' * find . \( -name "*.mir" -o -name "*.cpp" -o -name "*.h" -o -name "*.ll" \) -type f -print0 | xargs -0 sed -i '' -E 's/BB#" << ([a-zA-Z0-9_]+)\.getNumber\(\)/" << printMBBReference(\1)/g' * find . \( -name "*.txt" -o -name "*.s" -o -name "*.mir" -o -name "*.cpp" -o -name "*.h" -o -name "*.ll" \) -type f -print0 | xargs -0 sed -i '' -E 's/BB#([0-9]+)/%bb.\1/g' * grep -nr 'BB#' and fix Differential Revision: https://reviews.llvm.org/D40422 llvm-svn: 319665
2017-12-05 01:18:51 +08:00
; CHECK: # %bb.0:
[X86] Add test case for PR30511 and r282341. llvm-svn: 282473
2016-09-27 14:44:30 +08:00
; CHECK-NEXT: addpd {{.*}}(%rip), %xmm0
; CHECK-NEXT: cvtdq2pd %xmm0, %xmm0
[DAGCombiner][x86] scalarize binop followed by extractelement As noted in PR39973 and D55558: https://bugs.llvm.org/show_bug.cgi?id=39973 ...this is a partial implementation of a fold that we do as an IR canonicalization in instcombine: // extelt (binop X, Y), Index --> binop (extelt X, Index), (extelt Y, Index) We want to have this in the DAG too because as we can see in some of the test diffs (reductions), the pattern may not be visible in IR. Given that this is already an IR canonicalization, any backend that would prefer a vector op over a scalar op is expected to already have the reverse transform in DAG lowering (not sure if that's a realistic expectation though). The transform is limited with a TLI hook because there's an existing transform in CodeGenPrepare that tries to do the opposite transform. Differential Revision: https://reviews.llvm.org/D55722 llvm-svn: 350354
2019-01-04 05:31:16 +08:00
; CHECK-NEXT: mulsd {{.*}}(%rip), %xmm0
[X86][SSE2] Fix asm string for movq (Move Quadword) instruction. Replace "mov{d|q}" with "movq". Differential Revision: https://reviews.llvm.org/D32220 llvm-svn: 301386
2017-04-26 15:08:44 +08:00
; CHECK-NEXT: movq %xmm0, %rax
[X86] Add test case for PR30511 and r282341. llvm-svn: 282473
2016-09-27 14:44:30 +08:00
; 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
}