-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Test Failure] the Sse2.MultiplyLow
test fails for some inputs.
#9644
Comments
FYI. @4creators |
In the validation logic the test is doing: CheckMethod<short> checkInt16 = (short x, short y, short z, ref short a) =>
{
var tmp = ((int)x * y) * 0x0000ffff;
a = unchecked((short)tmp);
return -a == z;
}; @4creators, could you explain the reasoning behind the The architecture manual indicates the logic is simply: So I would think we just want to do:
|
Typo - should be |
What about the logic for |
Suspect that it could be merge problem during rebasing - I have started with > 50 commits before rebasing first to 5 and finally to 1 commit |
@tannergooding @fiigii @4creators - The fact that this test was exhibiting non-deterministic behavior is problematic. I believe that it is still the plan to change the Sse2 tests to use the new templates, but if that's not happening soon, we should change TestTableSse2.cs to not use |
Agreed.
I was planning on moving most of the tests over after dotnet/coreclr#16095 goes in. Then I was going to work on adding templates for testing commutative operations and containment tests for |
Thanks @tannergooding! |
@CarolEidt @tannergooding In such case I will speed up test conversion to common template and fix
|
@tannergooding Which part of tests should I port to common template? |
I was explicitly waiting on dotnet/coreclr#16095 in order to help prevent merge conflicts and to reduce the total number of changes, since it updates the tests to include additional scenarios.
All of it. The only thing the Sse2 tests are doing that the template is not is validating loops, which I was going to update the template to cover (one commit moves the tests over to the template, a second commit updates the template to test loops and regenerates all the tests). |
OK than I will start work once dotnet/coreclr#16095 will be in except for parts which do not have to wait. |
I already have part of this done locally (on top of my existing changes), so that might just end up duplicating work. It would be beneficial to have any new tests using the template from the get-go (if you plan on resolving the merge conflicts and continuing with dotnet/coreclr#15777, for example). |
See https://ci.dot.net/job/dotnet_coreclr/job/master/job/jitstress/job/x86_checked_windows_nt_jitx86hwintrinsicnoavx_prtest/56/, for an example.
The text was updated successfully, but these errors were encountered: