mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-25 04:02:41 +01:00
728acc9bd9
This is mostly to test the waters. I'd like to get results from FNT build bots and other bots running on non-x86 platforms. This feature has been pretty heavily tested over the last few months by me, and it fixes several of the execution time regressions caused by the inlining work by preventing inlining decisions from radically impacting block layout. I've seen very large improvements in yacr2 and ackermann benchmarks, along with the expected noise across all of the benchmark suite whenever code layout changes. I've analyzed all of the regressions and fixed them, or found them to be impossible to fix. See my email to llvmdev for more details. I'd like for this to be in 3.1 as it complements the inliner changes, but if any failures are showing up or anyone has concerns, it is just a flag flip and so can be easily turned off. I'm switching it on tonight to try and get at least one run through various folks' performance suites in case SPEC or something else has serious issues with it. I'll watch bots and revert if anything shows up. llvm-svn: 154816
23 lines
688 B
LLVM
23 lines
688 B
LLVM
; RUN: llc < %s -mcpu=generic -march=x86-64 | FileCheck %s
|
|
; Verify that we are using the efficient uitofp --> sitofp lowering illustrated
|
|
; by the compiler_rt implementation of __floatundisf.
|
|
; <rdar://problem/8493982>
|
|
|
|
target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64"
|
|
target triple = "x86_64-apple-darwin10.0.0"
|
|
|
|
; CHECK: testq %rdi, %rdi
|
|
; CHECK-NEXT: js LBB0_1
|
|
; CHECK: cvtsi2ss
|
|
; CHECK-NEXT: ret
|
|
; CHECK: LBB0_1
|
|
; CHECK: shrq
|
|
; CHECK-NEXT: andq
|
|
; CHECK-NEXT: orq
|
|
; CHECK-NEXT: cvtsi2ss
|
|
define float @test(i64 %a) {
|
|
entry:
|
|
%b = uitofp i64 %a to float
|
|
ret float %b
|
|
}
|