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/fp128-extract.ll

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

29 lines
1.3 KiB
LLVM
Raw Normal View History

[X86] Regenerate fp128 test llvm-svn: 322460
2018-01-15 03:07:41 +08:00
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
; RUN: llc < %s -O2 -mtriple=x86_64-linux-android -mattr=+mmx -enable-legalize-types-checking | FileCheck %s
; RUN: llc < %s -O2 -mtriple=x86_64-linux-gnu -mattr=+mmx -enable-legalize-types-checking | FileCheck %s
[X86] Keep EXTRACT_VECTOR_ELT result type as f128 for Android x86_64. Android x86_64 target uses f128 type and stores f128 values in %xmm* registers. SoftenFloatRes_EXTRACT_VECTOR_ELT should not convert result value from f128 to i128. Differential Revision: http://reviews.llvm.org/D32102 llvm-svn: 300583
2017-04-19 04:15:18 +08:00
; Test the softened result of extractelement op code.
[X86] Regenerate fp128 test llvm-svn: 322460
2018-01-15 03:07:41 +08:00
define fp128 @TestExtract(<2 x double> %x) nounwind {
; CHECK-LABEL: TestExtract:
; CHECK: # %bb.0: # %entry
; CHECK-NEXT: subq $40, %rsp
; CHECK-NEXT: movaps %xmm0, (%rsp) # 16-byte Spill
; CHECK-NEXT: callq __extenddftf2
[X86] Change legalization action for f128 fadd/fsub/fmul/fdiv from Custom to LibCall. The custom code just emits a libcall, but we can do the same with generic code. The only difference is that the generic code can form tail calls where the custom code couldn't. This is responsible for the test changes. This avoids needing to modify the Custom handling for strict fp.
2019-11-22 03:27:04 +08:00
; CHECK-NEXT: movaps %xmm0, {{[-0-9]+}}(%r{{[sb]}}p) # 16-byte Spill
[X86] Regenerate fp128 test llvm-svn: 322460
2018-01-15 03:07:41 +08:00
; CHECK-NEXT: movaps (%rsp), %xmm0 # 16-byte Reload
; CHECK-NEXT: movhlps {{.*#+}} xmm0 = xmm0[1,1]
; CHECK-NEXT: callq __extenddftf2
; CHECK-NEXT: movaps %xmm0, %xmm1
[X86] Change legalization action for f128 fadd/fsub/fmul/fdiv from Custom to LibCall. The custom code just emits a libcall, but we can do the same with generic code. The only difference is that the generic code can form tail calls where the custom code couldn't. This is responsible for the test changes. This avoids needing to modify the Custom handling for strict fp.
2019-11-22 03:27:04 +08:00
; CHECK-NEXT: movaps {{[-0-9]+}}(%r{{[sb]}}p), %xmm0 # 16-byte Reload
[X86] Regenerate fp128 test llvm-svn: 322460
2018-01-15 03:07:41 +08:00
; CHECK-NEXT: addq $40, %rsp
[X86] Change legalization action for f128 fadd/fsub/fmul/fdiv from Custom to LibCall. The custom code just emits a libcall, but we can do the same with generic code. The only difference is that the generic code can form tail calls where the custom code couldn't. This is responsible for the test changes. This avoids needing to modify the Custom handling for strict fp.
2019-11-22 03:27:04 +08:00
; CHECK-NEXT: jmp __multf3 # TAILCALL
[X86] Keep EXTRACT_VECTOR_ELT result type as f128 for Android x86_64. Android x86_64 target uses f128 type and stores f128 values in %xmm* registers. SoftenFloatRes_EXTRACT_VECTOR_ELT should not convert result value from f128 to i128. Differential Revision: http://reviews.llvm.org/D32102 llvm-svn: 300583
2017-04-19 04:15:18 +08:00
entry:
; Simplified instruction pattern from the output of llvm before r289042,
; for a boost function ...::insert<...>::traverse<...>().
%a = fpext <2 x double> %x to <2 x fp128>
%0 = extractelement <2 x fp128> %a, i32 0
%1 = extractelement <2 x fp128> %a, i32 1
%2 = fmul fp128 %0, %1
ret fp128 %2
}