On 2/14/25 04:58, Jeff Law wrote: > I'd guess it more work than it'd be worth. We're just not seeing > vsetvls being all that problematical on our design. I do see a lot of > seemingly gratutious changes in the vector config, but when we make > changes to fix that we generally end up with worse performing code.
To be clear the VSETVL on their own are not problematic for us either. It causing VL=0 is. I have a change in works which could introduce additional VSETVLs ;-) -Vineet
