[NFC] Clear C33010 Warning (#7603) (#7604)
Cherry-picked to release-1.8.2505 from
#7603
Resolves `C33010` which is currently blocking the release pipeline.
Addresses #7605
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Update Release notes for 1.8.2505 (#7481)
This change updates release notes with notable changes for release
1.8.2505.

Update 1.8.2502 release notes (#7147)
An internal fix has changed the way PDB files are packaged on release.
This change is worth noting in the release notes for 1.8.2502.

Fix warning when use implicit launch type. (#6837) (#6841)
By default, the launch type should be set to ‘Broadcast’ when diagnosing
barriers. However, the current behavior sets the default launch type to
‘Invalid,’ resulting in warnings when the launch type is not explicitly
specified as an attribute.
To address this issue, we’ll adjust the default setting to ‘Broadcast’
and thereby resolve the problem.
Fixes #6836
---------
Co-authored-by: Damyan Pepper <damyanp@microsoft.com>
(cherry picked from commit ef043e9)

Add tests for literal overloads of fmod, length, and normalize (#6437) (
#6799)
Certain HL ops with no double overload will generate double overloads
for literal types. These are lowered to double DXIL overloads, some of
which are not legal for these ops. We currently rely on illegal
intermediate DXIL op overloads for constant evaluation. If constant
evaluation fails, we end up with illegal DXIL overloads in final DXIL,
which is caught by the validator.
The prior revert restored the ability to run these scenarios (with
asserts disabled).
This change adds tests for #6419 so automated testing will test across
configurations and prevent regressions of this scenario in this branch.
(cherry picked from commit 9c2b828)
Co-authored-by: Tex Riddell <texr@microsoft.com>

Pix: Cope with group shared AS->MS payload (#6619)
This change copes with the AS->MS payload being placed in group-shared
by the application (and MSFT's samples do indeed do this). (TIL, thanks
to pow2clk, that the spec says that the payload counts against the
group-shared total, implying, if not explicitly stating, that at least
on some platforms, the payload will be in group-shared anyway.)
The MS pass needs to be given data from the AS about the AS's thread
group topology, and this is done by extending the payload struct to add
three uints. This can't be done when the payload is resident in
group-shared, of course, because that would change the layout of
group-shared memory.
So the new approach here is to copy the payload to a new alloca (in the
default address space) struct with the members of the base struct plus
the extended data the MS needs, and then to copy piece-wise because
llvm.memcpy isn't appropriate for group-shared-to-normal address space
copies.

[Sema] Check FunctionDecl has identifier before getName. (#6439) (#6457)
Use identifier name without check the identifier exists will cause
crash.
Fixes #6426
---------
Co-authored-by: Tex Riddell <texr@microsoft.com>
Co-authored-by: github-actions[bot]
<github-actions[bot]@users.noreply.github.com>
(cherry picked from commit 7581ff4)

Add tests for literal overloads of fmod, length, and normalize (#6437)
Certain HL ops with no double overload will generate double overloads
for literal types. These are lowered to double DXIL overloads, some of
which are not legal for these ops. We currently rely on illegal
intermediate DXIL op overloads for constant evaluation. If constant
evaluation fails, we end up with illegal DXIL overloads in final DXIL,
which is caught by the validator.
The prior revert restored the ability to run these scenarios (with
asserts disabled).
This change adds tests for #6419 so automated testing will test across
configurations and prevent regressions of this scenario in this branch.

CP: Use git rev-parse to get last commit sha (#6366) (#6375)
Do not use `git describe`, it is using tags which might be out of date
and unrelated to the current build and version.
(cherry picked from commit aaab2a7)

Fix attribute collision for HL intrinsics (#5451) (#5543)
HL Intrinsic functions share declarations with those that match group
and function signature, regardless of the original intrinsic name. This
means that intrinsics with differing attributes can be collapsed into
the same HL functions, leading to incorrect attributes for some HL
intrinsics.
This fixes this issue by adding the attributes to the HL operation
mangling, the same way this issue was fixed for the HLWaveSensitive
attribute before.
Fixes #3505
---------
Co-authored-by: Joshua Batista <jbatista@microsoft.com>
(cherry picked from commit d9c07e9)
Co-authored-by: Tex Riddell <texr@microsoft.com>