aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h
diff options
context:
space:
mode:
authorKrzysztof Drewniak <Krzysztof.Drewniak@amd.com>2023-01-02 21:24:39 +0000
committerKrzysztof Drewniak <Krzysztof.Drewniak@amd.com>2023-01-06 20:32:29 +0000
commite502f4fc2e25eedaca6bd8c1eacc6e0365ef403a (patch)
tree209e9730c94563d1f2b64f6a5d4275ce76e98098 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h
parent87fe37d9f8b668f537006a2bf6921cf2ad3fb2a2 (diff)
downloadllvm-e502f4fc2e25eedaca6bd8c1eacc6e0365ef403a.zip
llvm-e502f4fc2e25eedaca6bd8c1eacc6e0365ef403a.tar.gz
llvm-e502f4fc2e25eedaca6bd8c1eacc6e0365ef403a.tar.bz2
[mlir][Arith] Remove expansions of integer min and max ops
As of several months ago, both ArithToLLVM and ArithToSPIRV have native support for integer min and max operations. Since these are all the targets available in MLIR core, the need to "expand" arith.minui, arith.minsi, arith,maxsi, and arith.manxui to more primitive operations is to longer present. Therefore, the expanding of integer min and max operations in Arith, while correct, is likely to lead to performance loss by way of misoptimization further down the line, and is no longer needed for anyone's correctness. This change may break downstream tests, but will not affect the semantics of MLIR programs. arith.minf and arith.maxf have a lot of underlying complexity due to the many different possible NaN and signed zero semantics available on various platforms, and so removing their expansion is left to a future commit. Reviewed By: ThomasRaoux, Mogball Differential Revision: https://reviews.llvm.org/D140856
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h')
0 files changed, 0 insertions, 0 deletions