[Headers][X86] Allow AVX/AVX512 float/double add/sub/mul/div/unpck intrinsics to be used in constexpr

[RKSimon]

We already do this for SSE1/SSE2 intrinsics, but are missing the AVX1/AVX512F intrinsics:

_mm256_add_pd / _mm256_add_ps
_mm256_sub_pd / _mm256_sub_ps
_mm256_mul_pd / _mm256_mul_ps
_mm256_div_pd / _mm256_div_ps
_mm256_unpackhi_pd / _mm256_unpackhi_ps
_mm256_unpacklo_pd / _mm256_unpacklo_ps

_mm512_add_pd / _mm512_add_ps
_mm512_sub_pd / _mm512_sub_ps
_mm512_mul_pd / _mm512_mul_ps
_mm512_div_pd / _mm512_div_ps
_mm512_unpackhi_pd / _mm512_unpackhi_ps
_mm512_unpacklo_pd / _mm512_unpacklo_ps

(ignore the AVX512 mask/maskz variants for now)

You can use #152305 as reference.

[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-backend-x86

Author: Simon Pilgrim (RKSimon)

We already do this for SSE1/SSE2 intrinsics, but are missing the AVX1/AVX512F intrinsics: ``` _mm256_add_pd / _mm256_add_ps _mm256_sub_pd / _mm256_sub_ps _mm256_mul_pd / _mm256_mul_ps _mm256_div_pd / _mm256_div_ps _mm256_unpackhi_pd / _mm256_unpackhi_ps _mm256_unpacklo_pd / _mm256_unpacklo_ps

_mm512_add_pd / _mm512_add_ps
_mm512_sub_pd / _mm512_sub_ps
_mm512_mul_pd / _mm512_mul_ps
_mm512_div_pd / _mm512_div_ps
_mm512_unpackhi_pd / _mm512_unpackhi_ps
_mm512_unpacklo_pd / _mm512_unpacklo_ps

(ignore the AVX512 mask/maskz variants for now)

You can use #<!-- -->152305 as reference.
</details>

[llvmbot]

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

Author: Simon Pilgrim (RKSimon)

We already do this for SSE1/SSE2 intrinsics, but are missing the AVX1/AVX512F intrinsics: ``` _mm256_add_pd / _mm256_add_ps _mm256_sub_pd / _mm256_sub_ps _mm256_mul_pd / _mm256_mul_ps _mm256_div_pd / _mm256_div_ps _mm256_unpackhi_pd / _mm256_unpackhi_ps _mm256_unpacklo_pd / _mm256_unpacklo_ps

_mm512_add_pd / _mm512_add_ps
_mm512_sub_pd / _mm512_sub_ps
_mm512_mul_pd / _mm512_mul_ps
_mm512_div_pd / _mm512_div_ps
_mm512_unpackhi_pd / _mm512_unpackhi_ps
_mm512_unpacklo_pd / _mm512_unpacklo_ps

(ignore the AVX512 mask/maskz variants for now)

You can use #<!-- -->152305 as reference.
</details>

[yichi170]

@RKSimon I'd like to work on this! Can you assign it to me?