-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vector128 and Vector256 General purpose DotProduct tests fail #75791
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsDescriptionThese tests fail when upgraded to the new xunit based test system. This issue will be visible once #74886 is merged. Reproduction StepsRun the hardwareintrinsics_ro merged test project located in src/tests/JIT/HardwareIntrinsics/HardwareIntrinsics_ro.csproj Expected behaviorTest should reliably pass. Actual behaviorIt fails where the difference in behavior is a floating point accuracy issue. (The algorithm is ... close in result) The expected result is within a small fraction of the actual result. Console output looks like
Regression?Unlikely. Known WorkaroundsNo response ConfigurationNo response Other informationNo response
|
@kunalspathak PTAL. cc @dotnet/jit-contrib. |
I'd guess there is some subtle difference in addition ordering for the pre SSE4.1 codegen and that is causing it to be slightly off as compared to |
Why do they only fail when converted to the new test system? Are we not properly running them in the current test system? |
Is this #76280? It looks like there are numerous failure symptoms there (all zeroes, all ones, inverted max, etc.), but #76280 (comment) shows a small value change. |
Description
These tests fail when upgraded to the new xunit based test system. This issue will be visible once #74886 is merged.
Reproduction Steps
Run the hardwareintrinsics_ro merged test project located in src/tests/JIT/HardwareIntrinsics/HardwareIntrinsics_ro.csproj
Expected behavior
Test should reliably pass.
Actual behavior
It fails where the difference in behavior is a floating point accuracy issue. (The algorithm is ... close in result) The expected result is within a small fraction of the actual result.
Console output looks like
Regression?
Unlikely.
Known Workarounds
No response
Configuration
No response
Other information
No response
category:correctness
theme:vector-codegen
skill-level:beginner
cost:small
impact:small
The text was updated successfully, but these errors were encountered: