-
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: System.Xml.Tests.SameInstanceXslTransformWriter.Variations(param0: \"xslt_mutith_attribute_sets.xsl\", param1: \"xslt_mutith_attribute_sets.xml\") #40607
Comments
This has been failing in runtime-coreclr libraries-jitstress since last Sunday build 20200809.1 and it seems like a codegen issue to me. I am going to take a look and see if there were any changes between 51ad8e4 and 4a58c28 that affected this test. Marking as 5.0 for now |
These failures are causing considerable noise in the test runs (failing every configuration, AFAICT), so we should consider temporarily disabling them if a fix isn't available soon. |
The underlying issue is identified and it's due to the following transformation in morph:
while before #40535 such tree would be morphed in the following way
As a consequence, the upper 3 bytes of local have arbitrary values as it was demonstrated in #40871. The approach when we set The potential solution could be (as in 47a9b263998fb9d69523e45f7a98cb26249aaf47):
@dotnet/jit-contrib |
…40871) * Add regression test for #40607 * Add Runtime_40607.tt * Add more extensive tests for loads in Runtime_40607.tt Runtime_40607.il * Enable back failing test in System.Private.Xml.dll * Fold *(typ*)&lclVar tree when: 1) it is *definitely load* and types of both indirection and local variable have the same signedness (e.g. bool and byte) 2) otherwise, fold the tree and mark the local node with GTF_VAR_FOLDED_IND and call fgDoNormalizeOnStore() on such nodes' parents in post-order morph.
RC2 merge was done. |
failed in job: runtime-coreclr libraries-jitstress 20200809.1
Error message
The text was updated successfully, but these errors were encountered: