[Headers][X86] Allow AVX512 _mm512_set* intrinsics to be used in constexpr

[RKSimon]

Similar to #152173 - we need the AVX512F/BW/FP16 set intrinsics to be usable in constexpr:

_mm512_set1_pd
_mm512_set1_ps
_mm512_set1_epi8
_mm512_set1_epi16
_mm512_set1_epi32
_mm512_set1_epi64

_mm512_set4_pd
_mm512_set4_ps
_mm512_set4_epi32
_mm512_set4_epi64

_mm512_set_pd
_mm512_set_ps
_mm512_set_epi8
_mm512_set_epi16
_mm512_set_epi32
_mm512_set_epi64

_mm512_setr_pd
_mm512_setr_ps
_mm512_setr_epi8
_mm512_setr_epi16
_mm512_setr_epi32
_mm512_setr_epi64

_mm512_set1_ph
_mm512_set_ph
_mm512_setr_ph

_mm_setzero_ph
_mm256_setzero_ph
_mm512_setzero_ph

(ignore the mask/maskz variants for now)

[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)

Similar to #152173 - we need the AVX512F/BW/FP16 set intrinsics to be usable in constexpr: ``` _mm512_set1_pd _mm512_set1_ps _mm512_set1_epi8 _mm512_set1_epi16 _mm512_set1_epi32 _mm512_set1_epi64

_mm512_set4_pd
_mm512_set4_ps
_mm512_set4_epi32
_mm512_set4_epi64

_mm512_set_pd
_mm512_set_ps
_mm512_set_epi8
_mm512_set_epi16
_mm512_set_epi32
_mm512_set_epi64

_mm512_setr_pd
_mm512_setr_ps
_mm512_setr_epi8
_mm512_setr_epi16
_mm512_setr_epi32
_mm512_setr_epi64

_mm512_set1_ph
_mm512_set_ph
_mm512_setr_ph

_mm_setzero_ph
_mm256_setzero_ph
_mm512_setzero_ph

(ignore the mask/maskz variants for now)
</details>

[llvmbot]

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

Author: Simon Pilgrim (RKSimon)

Similar to #152173 - we need the AVX512F/BW/FP16 set intrinsics to be usable in constexpr: ``` _mm512_set1_pd _mm512_set1_ps _mm512_set1_epi8 _mm512_set1_epi16 _mm512_set1_epi32 _mm512_set1_epi64

_mm512_set4_pd
_mm512_set4_ps
_mm512_set4_epi32
_mm512_set4_epi64

_mm512_set_pd
_mm512_set_ps
_mm512_set_epi8
_mm512_set_epi16
_mm512_set_epi32
_mm512_set_epi64

_mm512_setr_pd
_mm512_setr_ps
_mm512_setr_epi8
_mm512_setr_epi16
_mm512_setr_epi32
_mm512_setr_epi64

_mm512_set1_ph
_mm512_set_ph
_mm512_setr_ph

_mm_setzero_ph
_mm256_setzero_ph
_mm512_setzero_ph

(ignore the mask/maskz variants for now)
</details>

[markbhasawut]

Hi, I would like to work on this issue. Could you assign to me? @RKSimon