-
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
Test failure: ilasm round-trip HugeField2 #38529
Comments
Dotnet-GitSync-Bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Jun 29, 2020
JulieLeeMSFT
removed
the
untriaged
New issue has not been triaged by the area owner
label
Jun 29, 2020
BruceForstall
added a commit
to BruceForstall/runtime
that referenced
this issue
Jun 30, 2020
BruceForstall
added a commit
that referenced
this issue
Jul 2, 2020
* Enable ilasm/ildasm round trip testing in new AzDO pipeline Pipeline is `runtime-coreclr ilasm`. Also, add an optional `IlasmRoundTripIncompatible` msbuild property to allow disabling tests for the IlasmRoundTrip test. * Disable tests for ilasm round-trip testing Tracking issues: #11412 #38515 #38506 #38507 #38508 #38529
markples
added a commit
that referenced
this issue
Oct 5, 2022
Indx256 is a trie (or prefix tree) used to map labels to instructions. It is very space-intensive because it allocates 256-element arrays for child nodes. This is a localized fix to lazily allocate the child arrays and to split them into two 128-element arrays to handle common cases such as ildasm's output (IL_<hex>). A more aggressive change to a different data structure would save much more memory but should probably include an analysis of why a trie was originally used. Fixes #38515, #38529, #43818, and #73139. I don't think hugeExpr1 (#38515) is going to get picked up by our current testing since the ilasmroundtrip run doesn't turn off tiered compilation, but I did check its behavior on x86 locally.
Fixed in #76590 |
ghost
locked as resolved and limited conversation to collaborators
Nov 4, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With:
From Windows x86:
https://dev.azure.com/dnceng/public/_build/results?buildId=708755&view=ms.vss-test-web.build-test-results-tab&runId=21956288&resultId=103873&paneView=debug
The text was updated successfully, but these errors were encountered: