Skip to content

Conversation

@SwapnilGaikwad
Copy link
Contributor

@SwapnilGaikwad SwapnilGaikwad commented Nov 17, 2025

Contribute towards #121659

This PR fixes the NaN comparisons that were incorrectly handled in ConvertTo* tests as highlighted in the following screenshot.

Failure output.
image

@dotnet/arm64-contrib @a74nh @EgorBo

@github-actions github-actions bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Nov 17, 2025
@dotnet-policy-service dotnet-policy-service bot added the community-contribution Indicates that the PR has been added by a community member label Nov 17, 2025
@EgorBo
Copy link
Member

EgorBo commented Nov 17, 2025

@SwapnilGaikwad do you need to run runtime-coreclr outerloop?

@SwapnilGaikwad SwapnilGaikwad changed the title Fix failing NaN comparisons in Sve2.ConvertTo* tests Arm64: [SVE] Fix failing NaN comparisons in Sve2.ConvertTo* tests Nov 17, 2025
@SwapnilGaikwad
Copy link
Contributor Author

runtime-coreclr outerloop

It would be useful, cheers. However, the other Sve2_ShiftArithmeticSaturate* tests would still fail. Up to you if you want to wait until those are fixed.

@EgorBo
Copy link
Member

EgorBo commented Nov 17, 2025

/azp run runtime-coreclr outerloop

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@EgorBo
Copy link
Member

EgorBo commented Nov 17, 2025

@SwapnilGaikwad it looks like this change introduced a lot more new failures from 40-50 to 800+

@SwapnilGaikwad
Copy link
Contributor Author

@SwapnilGaikwad it looks like this change introduced a lot more new failures from 40-50 to 800+

Apologies. Now limited the changes to only ConvertTo* tests using separate templates. Let's see how this goes, didn't show any failures locally.

@SwapnilGaikwad
Copy link
Contributor Author

Hi @EgorBo, should we run runtime-coreclr outerloop tests on this?

@EgorBo
Copy link
Member

EgorBo commented Nov 19, 2025

/azp run runtime-coreclr outerloop

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@SwapnilGaikwad SwapnilGaikwad added area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Nov 19, 2025
@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

@SwapnilGaikwad
Copy link
Contributor Author

Seems majority of the failures are related to ShiftArithmeticSaturate that are tracked in #121659

@a74nh
Copy link
Contributor

a74nh commented Nov 20, 2025

/azp run runtime-coreclr outerloop

I though that the changes made here for eng/pipelines/coreclr/hardware-intrinsics.yml meant that the hardware instrinsic tests would all automatically be run for any PR that touches eng/pipelines/**, src/coreclr/jit/**, src/tests/Common/GenerateHWIntrinsicTests/**, src/tests/JIT/HardwareIntrinsics/**

@EgorBo
Copy link
Member

EgorBo commented Nov 20, 2025

/azp run runtime-coreclr outerloop

I though that the changes made here for eng/pipelines/coreclr/hardware-intrinsics.yml meant that the hardware instrinsic tests would all automatically be run for any PR that touches eng/pipelines/**, src/coreclr/jit/**, src/tests/Common/GenerateHWIntrinsicTests/**, src/tests/JIT/HardwareIntrinsics/**

@jkoritzinsky @dotnet/jit-contrib any YML experts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI community-contribution Indicates that the PR has been added by a community member

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants