[llvm-dev] [RFC][VECLIB] how should we legalize VECLIB calls?

[Renato Golin via llvm-dev]

On Tue, 3 Jul 2018 at 00:35, Hal Finkel via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> I completely agree. We need a solution to handle 'declare simd' calls, or to put it another way, arbitrary user-defined functions. To me, this really looks like an ABI issue. If we have a function, __foo__computeit8(<8 x float> %x), then if our lowering of <8 x float> doesn't match the required register assignments, then we have the wrong ABI. Will https://reviews.llvm.org/D47188 fix this?

FYI, Arm has published a draft of a similar proposal:

https://developer.arm.com/products/software-development-tools/hpc/arm-compiler-for-hpc/vector-function-abi

They directly mention OpenMP declare simd, but there's no reason we
can't apply something similar to Clang (and GCC) pragmas as well.

cheers,
--renato