[llvm-dev] LLVM 11 and trunk selecting 4 wide instead of 8 wide loop vectorization for AVX-enabled target (original) (raw)

Francesco Petrogalli via llvm-dev llvm-dev at lists.llvm.org
Fri Jul 17 07:23:45 PDT 2020

Hi all,

Thank you Florian for pointing Neil in the right direction!

I am glad this has been working for you Neil. Feel free to contact me directly if you need anything related to function vectorization again.

It might be worth calling this new behavior out in the release notes for 11.0

How can we make sure this happens? Is there a process where we could write into release notes?

Kind regards,

Francesco

From: Florian Hahn <florian_hahn at apple.com> Date: Friday, July 17, 2020 at 9:19 AM To: Neil Henning <neil.henning at unity3d.com> Cc: Sanjay Patel <spatel at rotateright.com>, llvm-dev <llvm-dev at lists.llvm.org>, Francesco Petrogalli <Francesco.Petrogalli at arm.com> Subject: Re: [llvm-dev] LLVM 11 and trunk selecting 4 wide instead of 8 wide loop vectorization for AVX-enabled target

On Jul 17, 2020, at 12:51, Neil Henning <mailto:neil.henning at unity3d.com> wrote:

Oh interesting - I hadn't even considered registering vector descriptors for the LLVM intrinsics, but right enough when I just registered that pow has a vector variant (itself of a bigger size) I got the correct 8-wide variants like I was expecting - nice!

Thanks for the help!

No worries. It might be worth calling this new behavior out in the release notes for 11.0

More information about the llvm-dev mailing list