File: arm64-regress-f128csel-flags.ll

package info (click to toggle)
llvm-toolchain-19 1%3A19.1.7-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,998,520 kB
  • sloc: cpp: 6,951,680; ansic: 1,486,157; asm: 913,598; python: 232,024; f90: 80,126; objc: 75,281; lisp: 37,276; pascal: 16,990; sh: 10,009; ml: 5,058; perl: 4,724; awk: 3,523; makefile: 3,167; javascript: 2,504; xml: 892; fortran: 664; cs: 573
file content (27 lines) | stat: -rw-r--r-- 950 bytes parent folder | download | duplicates (28)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
; RUN: llc < %s -mtriple=arm64-eabi -verify-machineinstrs | 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, double %l, double %r) 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 %l, double %r

    ; 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
}