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/PowerPC/i1-to-double.ll

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

79 lines
2.5 KiB
LLVM
Raw Normal View History

[NFC] [PowerPC] Move i1-to-fp tests and use script
2020-12-08 15:20:15 +08:00
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
PowerPC: Do not use llc -march in tests. `llc -march` is problematic because it only switches the target architecture, but leaves the operating system unchanged. This occasionally leads to indeterministic tests because the OS from LLVM_DEFAULT_TARGET_TRIPLE is used. However we can simply always use `llc -mtriple` instead. This changes all the tests to do this to avoid people using -march when they copy and paste parts of tests. This patch: - Removes -march if the .ll file already has a matching `target triple` directive or -mtriple argument. - In all other cases changes -march=ppc32/-march=ppc64 to -mtriple=ppc32--/-mtriple=ppc64-- See also the discussion in https://reviews.llvm.org/D35287 llvm-svn: 309754
2017-08-02 06:20:41 +08:00
; RUN: llc -verify-machineinstrs -mcpu=ppc32 -mtriple=powerpc-unknown-linux-gnu < %s | FileCheck %s
[NFC] [PowerPC] Move i1-to-fp tests and use script
2020-12-08 15:20:15 +08:00
With PPC CR bit registers, handle int_to_fp on older cores On cores without fpcvt support, we cannot promote int_to_fp i1 operations, because there is nothing to promote them to. The most straightforward implementation of this uses a select to choose between the two possible resulting floating-point values (and that's what is done here). llvm-svn: 203015
2014-03-06 06:14:00 +08:00
define double @test(i1 %X) {
[NFC] [PowerPC] Move i1-to-fp tests and use script
2020-12-08 15:20:15 +08:00
; CHECK-LABEL: test:
; CHECK: # %bb.0:
; CHECK-NEXT: li 4, .LCPI0_0@l
; CHECK-NEXT: andi. 3, 3, 1
; CHECK-NEXT: addis 3, 4, .LCPI0_0@ha
; CHECK-NEXT: li 4, .LCPI0_1@l
; CHECK-NEXT: addis 4, 4, .LCPI0_1@ha
; CHECK-NEXT: bc 12, 1, .LBB0_1
; CHECK-NEXT: b .LBB0_2
; CHECK-NEXT: .LBB0_1:
; CHECK-NEXT: addi 3, 4, 0
; CHECK-NEXT: .LBB0_2:
; CHECK-NEXT: lfs 1, 0(3)
; CHECK-NEXT: blr
%Y = uitofp i1 %X to double
ret double %Y
}
; Verify the cases won't crash because of missing chains
@foo = dso_local global double 0.000000e+00, align 8
define double @u1tofp(i1 %i, double %d) #0 {
; CHECK-LABEL: u1tofp:
; CHECK: # %bb.0: # %entry
; CHECK-NEXT: li 4, .LCPI1_0@l
; CHECK-NEXT: andi. 3, 3, 1
; CHECK-NEXT: addis 3, 4, .LCPI1_0@ha
; CHECK-NEXT: li 4, .LCPI1_1@l
; CHECK-NEXT: addis 4, 4, .LCPI1_1@ha
; CHECK-NEXT: bc 12, 1, .LBB1_1
; CHECK-NEXT: b .LBB1_2
; CHECK-NEXT: .LBB1_1: # %entry
; CHECK-NEXT: addi 3, 4, 0
; CHECK-NEXT: .LBB1_2: # %entry
; CHECK-NEXT: fmr 0, 1
; CHECK-NEXT: lfs 1, 0(3)
; CHECK-NEXT: lis 3, foo@ha
; CHECK-NEXT: stfd 0, foo@l(3)
; CHECK-NEXT: blr
entry:
%conv = tail call double @llvm.experimental.constrained.uitofp.f64.i1(i1 %i, metadata !"round.dynamic", metadata !"fpexcept.strict") #0
store volatile double %d, double* @foo, align 8
ret double %conv
}
define double @s1tofp(i1 %i, double %d) #0 {
; CHECK-LABEL: s1tofp:
; CHECK: # %bb.0: # %entry
; CHECK-NEXT: li 4, .LCPI2_0@l
; CHECK-NEXT: andi. 3, 3, 1
; CHECK-NEXT: addis 3, 4, .LCPI2_0@ha
; CHECK-NEXT: li 4, .LCPI2_1@l
; CHECK-NEXT: addis 4, 4, .LCPI2_1@ha
; CHECK-NEXT: bc 12, 1, .LBB2_1
; CHECK-NEXT: b .LBB2_2
; CHECK-NEXT: .LBB2_1: # %entry
; CHECK-NEXT: addi 3, 4, 0
; CHECK-NEXT: .LBB2_2: # %entry
; CHECK-NEXT: fmr 0, 1
; CHECK-NEXT: lfs 1, 0(3)
; CHECK-NEXT: lis 3, foo@ha
; CHECK-NEXT: stfd 0, foo@l(3)
; CHECK-NEXT: blr
entry:
%conv = tail call double @llvm.experimental.constrained.sitofp.f64.i1(i1 %i, metadata !"round.dynamic", metadata !"fpexcept.strict") #0
store volatile double %d, double* @foo, align 8
ret double %conv
With PPC CR bit registers, handle int_to_fp on older cores On cores without fpcvt support, we cannot promote int_to_fp i1 operations, because there is nothing to promote them to. The most straightforward implementation of this uses a select to choose between the two possible resulting floating-point values (and that's what is done here). llvm-svn: 203015
2014-03-06 06:14:00 +08:00
}
[NFC] [PowerPC] Move i1-to-fp tests and use script
2020-12-08 15:20:15 +08:00
declare double @llvm.experimental.constrained.uitofp.f64.i1(i1, metadata, metadata)
declare double @llvm.experimental.constrained.sitofp.f64.i1(i1, metadata, metadata)
attributes #0 = { strictfp }