[PATCH] D118979: [AArch64] Set maximum VF with shouldMaximizeVectorBandwidth

Wed Apr 13 08:56:10 PDT 2022

jaykang10 added a comment.

In D118979#3448560 <https://reviews.llvm.org/D118979#3448560>, @fhahn wrote:

> In D118979#3448556 <https://reviews.llvm.org/D118979#3448556>, @jaykang10 wrote:
>
>> um... I have tried to reproduce it on a64fx machine. It looks it is failed with the big number of parallel tasks of ninja build. When I run the failed command manually, it is passed... If I reduce the number of the parallel tasks with ninja build like `ninja -j16`, the build is also passed... it could be memory allocation error from the bigger memory allocation than before...
>> The stage2 build and check-all are passed on Cortex-A72 machine...
>> To be safe, for now, I would like to disable `shouldMaximizeVectorBandwidth` for SVE...
>> Let me update this patch with it.
>
> I think it would be best to figure out if there's actually an issue/miscompile before re-landing. As is, the patch should only enable `shouldMaximizeVectorBandwidth` already, right?

um... To be honest, I am not expert of the SVE arch. Initially, I aimed to enable it for only neon arch.
@paulwalker-arm If possible, can you help me to investigate the build error from the buildbot for clang-aarch64-sve-vls-2stage please?

Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D118979/new/

https://reviews.llvm.org/D118979