On Mon, 16 Nov 2026 01:58:08 GMT, Xiaohong Gong <[email protected]> wrote:

> Does it have the same opportunity for other reduction operations for integer 
> types, or maybe other ops like min/max and the logic ones?

Yes, I believe so. We’re also planning to propose some optimizations for 
min/max reductions in the near future.

> BTW, do you think it's better to separate the reduction IRs for Vector API 
> and auto-vectorization. Looks like the last scalar operation for each 
> reduction from Vector API is not needed for all architectures, is it?

That sounds like a good idea. For add reductions, we can easily distinguish 
between Vector API and auto-vectorization using `requires_strict_order()`, but 
it’s not as straightforward for other reduction opcodes.

I’m wondering whether we should add a field to the existing reduction IR nodes, 
similar to what we did for add reductions, or introduce a separate set of IR 
nodes for Vector API reductions. Both approaches would allow us to distinguish 
between the two and optimize them independently.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/33319#issuecomment-6914423076

Reply via email to