
This adjusts the DXILOpBuilder API in a couple of ways: 1. Remove the need to call `getOverloadTy` before creating Ops 2. Introduce `tryCreateOp` to parallel `createOp` but propagate errors 3. Introduce specialized createOp methods for each DXIL Op This will simplify usage of the builder in upcoming changes, and also allows us to propagate errors via DiagnosticInfo rather than using fatal errors. Pull Request: https://github.com/llvm/llvm-project/pull/101250
15 lines
516 B
LLVM
15 lines
516 B
LLVM
; RUN: not opt -S -dxil-op-lower -mtriple=dxil-pc-shadermodel6.3-library %s 2>&1 | FileCheck %s
|
|
|
|
; DXIL operation exp2 does not support double overload type
|
|
; CHECK: in function exp2_double
|
|
; CHECK-SAME: Cannot create Exp2 operation: Invalid overload type
|
|
|
|
define noundef double @exp2_double(double noundef %a) #0 {
|
|
entry:
|
|
%a.addr = alloca double, align 8
|
|
store double %a, ptr %a.addr, align 8
|
|
%0 = load double, ptr %a.addr, align 8
|
|
%elt.exp2 = call double @llvm.exp2.f64(double %0)
|
|
ret double %elt.exp2
|
|
}
|