…all conv (llvm#778)

This PR follows OG CodeGen to use SPIR ABI info whatever the target is
when analysing the function info of SPIR-V kernels (identified by its
calling convention).

For example, when compiling OpenCL kernels to x86-64 target, the kernel
should still use SPIR-V's ABIInfo.

As we haven't implemented SPIR-V ABI handling for complex constructs,
there should be no functional changes. There is a test for this logic in
OG CodeGen:
`clang/test/CodeGenOpenCL/kernels-have-spir-cc-by-default.cl`. It mainly
involves structs, which is beyond the progress of CIR ABI stuff.

…all conv (llvm#778)

This PR follows OG CodeGen to use SPIR ABI info whatever the target is
when analysing the function info of SPIR-V kernels (identified by its
calling convention).

For example, when compiling OpenCL kernels to x86-64 target, the kernel
should still use SPIR-V's ABIInfo.

As we haven't implemented SPIR-V ABI handling for complex constructs,
there should be no functional changes. There is a test for this logic in
OG CodeGen:
`clang/test/CodeGenOpenCL/kernels-have-spir-cc-by-default.cl`. It mainly
involves structs, which is beyond the progress of CIR ABI stuff.

…all conv (llvm#778)

This PR follows OG CodeGen to use SPIR ABI info whatever the target is
when analysing the function info of SPIR-V kernels (identified by its
calling convention).

For example, when compiling OpenCL kernels to x86-64 target, the kernel
should still use SPIR-V's ABIInfo.

As we haven't implemented SPIR-V ABI handling for complex constructs,
there should be no functional changes. There is a test for this logic in
OG CodeGen:
`clang/test/CodeGenOpenCL/kernels-have-spir-cc-by-default.cl`. It mainly
involves structs, which is beyond the progress of CIR ABI stuff.