aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Commands/CommandObjectProcess.cpp
diff options
context:
space:
mode:
authorJakub Kuderski <jakub@nod-labs.com>2023-11-27 11:19:20 -0500
committerGitHub <noreply@github.com>2023-11-27 11:19:20 -0500
commite0aac8c88d0d30e8da0f8a240ad1e6b4d88782e0 (patch)
tree99400ed288c55191155f46639ce0d51fdf9dd57c /lldb/source/Commands/CommandObjectProcess.cpp
parent6b9c186b2d4c8bd315034a9655a28d32bcf745ab (diff)
downloadllvm-e0aac8c88d0d30e8da0f8a240ad1e6b4d88782e0.zip
llvm-e0aac8c88d0d30e8da0f8a240ad1e6b4d88782e0.tar.gz
llvm-e0aac8c88d0d30e8da0f8a240ad1e6b4d88782e0.tar.bz2
[mlir][gpu] Align reduction operations with vector combining kinds (#73423)
The motivation for this change is explained in https://github.com/llvm/llvm-project/issues/72354. Before this change, we could not tell between signed/unsigned minimum/maximum and NaN treatment for floating point values. The mapping of old reduction operations to the new ones is as follows: * `min` --> `minsi` for ints, `minf` for floats * `max` --> `maxsi` for ints, `maxf` for floats New reduction kinds not represented in the old enum: `minui`, `maxui`, `minimumf`, `maximumf`. As a next step, I would like to have a common definition of combining kinds used by the `vector` and `gpu` dialects. Separately, the GPU to SPIR-V lowering does not yet properly handle zero and NaN values -- the behavior of floating point min/max group reductions is not specified by the SPIR-V spec, see https://github.com/llvm/llvm-project/issues/73459. Issue: https://github.com/llvm/llvm-project/issues/72354
Diffstat (limited to 'lldb/source/Commands/CommandObjectProcess.cpp')
0 files changed, 0 insertions, 0 deletions