mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2024-08-28 22:29:56 +00:00
7474c171e1
This particular DAG combine is designed to kick in when both ConstantFPs will end up being loaded via a litpool, however those nodes have a semi-legal status, dictated by isFPImmLegal so in some cases there wouldn't have been a litpool in the first place. Don't try to be clever in those circumstances. Picked up while merging some AArch64 tests. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@206365 91177308-0d34-0410-b5e6-96231b3b80d8
29 lines
1017 B
LLVM
29 lines
1017 B
LLVM
; RUN: llc -mtriple=aarch64-none-linux-gnu -verify-machineinstrs < %s | FileCheck %s
|
|
; RUN: llc -mtriple=arm64-none-linux-gnu -verify-machineinstrs -o - %s | FileCheck %s
|
|
|
|
; We used to not mark NZCV as being used in the continuation basic-block
|
|
; when lowering a 128-bit "select" to branches. This meant a subsequent use
|
|
; of the same flags gave an internal fault here.
|
|
|
|
declare void @foo(fp128)
|
|
|
|
define double @test_f128csel_flags(i32 %lhs, fp128 %a, fp128 %b) nounwind {
|
|
; CHECK: test_f128csel_flags
|
|
|
|
%tst = icmp ne i32 %lhs, 42
|
|
%val = select i1 %tst, fp128 %a, fp128 %b
|
|
; CHECK: cmp w0, #42
|
|
; CHECK: b.eq .LBB0
|
|
|
|
call void @foo(fp128 %val)
|
|
%retval = select i1 %tst, double 4.0, double 5.0
|
|
|
|
; It's also reasonably important that the actual fcsel comes before the
|
|
; function call since bl may corrupt NZCV. We were doing the right thing anyway,
|
|
; but just as well test it while we're here.
|
|
; CHECK: fcsel {{d[0-9]+}}, {{d[0-9]+}}, {{d[0-9]+}}, ne
|
|
; CHECK: bl foo
|
|
|
|
ret double %retval
|
|
}
|