On Thu, 12 Mar 2026 16:47:34 GMT, Quan Anh Mai <[email protected]> wrote:
> I'm still not convinced with this solution. If the pattern matching method > proves itself to be not reliable, then we can proceed with an intrinsics. > Otherwise, we risk introduce a change that will eventually become redundant. Hi @merykitty , As discussed earlier your suggestions were incorporated in latest version of patch, idea here is not to hold an optimization in anticipation of future optimization. x86 backend changes will still be usable if at later point we decide to use complex pattern matching once TypeVect has constant information. What we have currently is generic handling which can inline any fallback after failed intrinsification attempts. Looking forward to your comments on backend part and any further improvement on existing handling. Hi @sviswa7 , @iwanowww , May I request you to share your views / comments ------------- PR Comment: https://git.openjdk.org/jdk/pull/24104#issuecomment-4052926175
