RFR: 8323582: C2 SuperWord AlignVector: misaligned vector memory access with unaligned native memory

Vladimir Kozlov kvn at openjdk.org
Tue Feb 25 17:32:02 UTC 2025


On Tue, 25 Feb 2025 07:09:24 GMT, Emanuel Peter <epeter at openjdk.org> wrote:

> > PS: "slow" path implies that it is not taking frequently and it should not affect general performance of application.
> 
> For me "slow" just means less optimized, because some assumption does not hold. The "fast" path is faster, because it has more assumptions and can optimize more (i.e. vectorize in this case, or vectorize more instructions). Do you have a better name than "fast/slow"?

I think I nit-picked here. I see your good comments in `loopTransform.cpp` and loop `node.hpp` explaining mutiversioning fast_loop/slow_loop. I think it is fine to keep "slow/fast". We can use "uncommon" to indicate unfrequent path.

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

PR Comment: https://git.openjdk.org/jdk/pull/22016#issuecomment-2682745643


More information about the hotspot-dev mailing list