summaryrefslogtreecommitdiff
path: root/lldb/test/API/python_api/global_module_cache/TestGlobalModuleCache.py
diff options
context:
space:
mode:
authorJakub Kuderski <jakub@nod-labs.com>2023-12-20 00:14:43 -0500
committerGitHub <noreply@github.com>2023-12-20 00:14:43 -0500
commit560564f51c626cf89920f13b6cea96684bac5848 (patch)
tree1306caabc20b5edbb10fabf845eb908d0e22990c /lldb/test/API/python_api/global_module_cache/TestGlobalModuleCache.py
parent5136c167a2573fbd05179849cb41b198c4862b12 (diff)
[mlir][vector][gpu] Align minf/maxf reduction kind names with arith (#75901)
This is to avoid confusion when dealing with reduction/combining kinds. For example, see a recent PR comment: https://github.com/llvm/llvm-project/pull/75846#discussion_r1430722175. Previously, they were picked to mostly mirror the names of the llvm vector reduction intrinsics: https://llvm.org/docs/LangRef.html#llvm-vector-reduce-fmin-intrinsic. In isolation, it was not clear if `<maxf>` has `arith.maxnumf` or `arith.maximumf` semantics. The new reduction kind names map 1:1 to arith ops, which makes it easier to tell/look up their semantics. Because both the vector and the gpu dialect depend on the arith dialect, it's more natural to align names with those in arith than with the lowering to llvm intrinsics. Issue: https://github.com/llvm/llvm-project/issues/72354
Diffstat (limited to 'lldb/test/API/python_api/global_module_cache/TestGlobalModuleCache.py')
0 files changed, 0 insertions, 0 deletions