-
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
[wasm] Failures in System.Numerics.Vectors and System.Runtime.Intrinsics tests #83792
Comments
Tagging subscribers to this area: @BrzVlad, @kotlarmilos Issue DetailsThese are happening in AOT only. Bisecting the issue revealed 3fec686 to be 1rst commit with that problem. It was not catched by CI as these tests are only part of runtime-wasm pipeline. It can be replicated with (some of the props might not be needed)
System.Numerics.Vectors
System.Runtime.Intrinsics
Discussed it with @kg on discord. @kg and @BrzVlad come with an idea how to fix it.
|
The inlining changes have caused us to run some stuff in the interpreter in AOT configuration that used to run in AOT, which is somehow causing some floating point tests to fail that pass in interp-only mode. This workaround makes the tests work again.
Reverting 3fec686 does seem to fix the problem. |
This seems to fix the problem for me:
|
These are happening in AOT only. Bisecting the issue revealed 3fec686 to be 1st commit with that problem. It was not catched by CI as these tests are only part of runtime-wasm pipeline.
It can be replicated with (some of the props might not be needed)
System.Numerics.Vectors
System.Runtime.Intrinsics
Discussed it with @kg on discord. @kg and @BrzVlad come with an idea how to fix it.
The text was updated successfully, but these errors were encountered: