llvm-project.git/mlir/lib/Dialect/Vector/Transforms/LowerVectorScan.cpp, branch main Unnamed repository; edit this file 'description' to name the repository. [mlir][Vector] Add support for scalable vectors to `ScanToArithOps` (#123117) 2025-11-20T13:39:52+00:00 Andrzej Warzyński andrzej.warzynski@arm.com 2025-11-20T13:39:52+00:00 cfda27d0fbda65de4a7f482d46231933c9f2c678 Note, scalable reductions dims are left as a TODO. 
Note, scalable reductions dims are left as a TODO.
 [mlir][vector] Simplify op rewrite pattern inheriting constructors. NFC. (#161670) 2025-10-02T23:07:25+00:00 Jakub Kuderski jakub@nod-labs.com 2025-10-02T23:07:25+00:00 3960ff6ca03b0441087f9042850199583d9e11d2 Use the `Base` type alias from https://github.com/llvm/llvm-project/pull/158433. 
Use the `Base` type alias from
https://github.com/llvm/llvm-project/pull/158433.
 [mlir][NFC] update `mlir/Dialect` create APIs (24/n) (#149931) 2025-07-22T12:16:15+00:00 Maksim Levental maksim.levental@gmail.com 2025-07-22T12:16:15+00:00 f904cdd6c3049e605d24ed17680e80e7133908a0 See https://github.com/llvm/llvm-project/pull/147168 for more info. 
See https://github.com/llvm/llvm-project/pull/147168 for more info.
 [mlir] Remove unused includes (NFC) (#148769) 2025-07-15T05:19:23+00:00 Kazu Hirata kazu@google.com 2025-07-15T05:19:23+00:00 c06d3a7b728293cbc53ff91239d6cd87c0982ffb These are identified by misc-include-cleaner. I've filtered out those that break builds. Also, I'm staying away from llvm-config.h, config.h, and Compiler.h, which likely cause platform- or compiler-specific build failures. 
These are identified by misc-include-cleaner.  I've filtered out those
that break builds.  Also, I'm staying away from llvm-config.h,
config.h, and Compiler.h, which likely cause platform- or
compiler-specific build failures.
 [mlir] Construct SmallVector with ArrayRef (NFC) (#101896) 2024-08-04T18:43:05+00:00 Kazu Hirata kazu@google.com 2024-08-04T18:43:05+00:00 5262865aac683b72f3e66de7a122e0c455ab6b9b 






mlir/LogicalResult: move into llvm (#97309)
2024-07-02T09:42:33+00:00

Ramkumar Ramachandra
ramkumar.ramachandra@codasip.com

2024-07-02T09:42:33+00:00

db791b278a414fb6df1acc1799adcf11d8fb9169

This patch is part of a project to move the Presburger library into
LLVM.




This patch is part of a project to move the Presburger library into
LLVM.






[mlir][vector][gpu] Align minf/maxf reduction kind names with arith (#75901)
2023-12-20T05:14:43+00:00

Jakub Kuderski
jakub@nod-labs.com

2023-12-20T05:14:43+00:00

560564f51c626cf89920f13b6cea96684bac5848

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




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






[mlir][vector][gpu] Use `makeArithReduction` in lowering patterns. NFC. (#75952)
2023-12-20T00:04:27+00:00

Jakub Kuderski
jakub@nod-labs.com

2023-12-20T00:04:27+00:00

9f74e6e6157bc4d63a28385c7c0a50506bb8a737

Use the `vector::makeArithReduction` helper as the source-of-truth of
reduction to arith ops lowering.




Use the `vector::makeArithReduction` helper as the source-of-truth of
reduction to arith ops lowering.






[mlir][vector] Rename vector reductions: `maxf` → `maximumf`, `minf` → `minimumf`
2023-09-13T22:49:07+00:00

Daniil Dudkin
unterumarmung@yandex.ru

2023-09-13T22:17:52+00:00

4a831250b871d5fbd5c6923fec4a492ec35f4b12

This patch is part of a larger initiative aimed at fixing floating-point `max` and `min` operations in MLIR: https://discourse.llvm.org/t/rfc-fix-floating-point-max-and-min-operations-in-mlir/72671.

Here, we are addressing task 2.1 from the plan, which involves renaming the vector reductions to align with the semantics of the corresponding LLVM intrinsics.

Reviewed By: dcaballe

Differential Revision: https://reviews.llvm.org/D158618





This patch is part of a larger initiative aimed at fixing floating-point `max` and `min` operations in MLIR: https://discourse.llvm.org/t/rfc-fix-floating-point-max-and-min-operations-in-mlir/72671.

Here, we are addressing task 2.1 from the plan, which involves renaming the vector reductions to align with the semantics of the corresponding LLVM intrinsics.

Reviewed By: dcaballe

Differential Revision: https://reviews.llvm.org/D158618







[mlir][arith] Rename operations: `maxf` → `maximumf`, `minf` → `minimumf` (#65800)
2023-09-12T05:02:19+00:00

Daniil Dudkin
39276703+unterumarmung@users.noreply.github.com

2023-09-12T05:02:19+00:00

8a6e54c9b3080f1b8e1a925bf1a39730223b99f9

This patch is part of a larger initiative aimed at fixing floating-point `max` and `min` operations in MLIR: https://discourse.llvm.org/t/rfc-fix-floating-point-max-and-min-operations-in-mlir/72671.

This commit addresses Task 1.2 of the mentioned RFC. By renaming these operations, we align their names with LLVM intrinsics that have corresponding semantics.




This patch is part of a larger initiative aimed at fixing floating-point `max` and `min` operations in MLIR: https://discourse.llvm.org/t/rfc-fix-floating-point-max-and-min-operations-in-mlir/72671.

This commit addresses Task 1.2 of the mentioned RFC. By renaming these operations, we align their names with LLVM intrinsics that have corresponding semantics.