[X86][Clang] VectorExprEvaluator::VisitCallExpr / InterpretBuiltin - add AVX512 kunpck intrinsics to be used in constexp

[RKSimon]

__mmask16 _mm512_kunpackb (__mmask16 a, __mmask16 b)
__mmask64 _mm512_kunpackd (__mmask64 a, __mmask64 b)
__mmask32 _mm512_kunpackw (__mmask32 a, __mmask32 b)

Hopefully these can be implemented as a binop callback

[llvmbot]

@llvm/issue-subscribers-backend-x86

Author: Simon Pilgrim (RKSimon)

``` __mmask16 _mm512_kunpackb (__mmask16 a, __mmask16 b) __mmask64 _mm512_kunpackd (__mmask64 a, __mmask64 b) __mmask32 _mm512_kunpackw (__mmask32 a, __mmask32 b) ``` Hopefully these can be implemented as a binop callback

[llvmbot]

Hi!

This issue may be a good introductory issue for people new to working on LLVM. If you would like to work on this issue, your first steps are:

1. Check that no other contributor is working on this issue. If someone is assigned to the issue or claimed to be working on it, ping the person. After one week without a response, the assignee may be changed.
2. Leave a comment indicating that you are working on the issue, or just create a pull request after following the steps below. Mention this issue in the description of the pull request.
3. Fix the issue locally.
4. Run the test suite locally. Remember that the subdirectories under test/ create fine-grained testing targets, so you can e.g. use make check-clang-ast to only run Clang's AST tests.
5. Create a Git commit.
6. Run git clang-format HEAD~1 to format your changes.
7. Open a pull request to the upstream repository on GitHub. Detailed instructions can be found in GitHub's documentation. Mention this issue in the description of the pull request.

If you have any further questions about this issue, don't hesitate to ask via a comment in the thread below.

[llvmbot]

@llvm/issue-subscribers-good-first-issue

Author: Simon Pilgrim (RKSimon)

``` __mmask16 _mm512_kunpackb (__mmask16 a, __mmask16 b) __mmask64 _mm512_kunpackd (__mmask64 a, __mmask64 b) __mmask32 _mm512_kunpackw (__mmask32 a, __mmask32 b) ``` Hopefully these can be implemented as a binop callback

[ahmednoursphinx]

Hey @RKSimon i would like to work on this issue if possible