
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
531 B
LLVM
15 lines
531 B
LLVM
; RUN: not opt -S -dxil-op-lower -mtriple=dxil-pc-shadermodel6.3-library %s 2>&1 | FileCheck %s
|
|
|
|
; This test is expected to fail with the following error
|
|
; CHECK: in function round_double
|
|
; CHECK-SAME: Cannot create Round operation: Invalid overload type
|
|
|
|
define noundef double @round_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.roundeven = call double @llvm.roundeven.f64(double %0)
|
|
ret double %elt.roundeven
|
|
}
|