-
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
[Arm64] Crossgen fails to compile some methods with NGenDump enabled #40354
Comments
One more issue like this while compiling these methods
The call stack
points at runtime/src/coreclr/src/jit/emitarm64.cpp Lines 12306 to 12309 in 646cfa3
that suggests that GTF_ICON_FTN_ADDR does not necessarily correspond to CORINFO_METHOD_HANDLE
|
Marking this as 5.0 for now, although since it appears to only be for display, not a Release mode functionality issue, we can easily move it to Future. |
Thanks for the analysis. Looks like it got introduced by my change in #38671. We can move it to Future because I want to make sure we still catch |
GTF_ICON_STATIC_HDL and GTF_ICON_FTN_ADDR can't be converted to names using eeGetFieldName and eeGetMethodFullName, respectively. So, just print out the type of the target. Fixes dotnet#40354
GTF_ICON_STATIC_HDL and GTF_ICON_FTN_ADDR can't be converted to names using eeGetFieldName and eeGetMethodFullName, respectively. So, just print out the type of the target. Fixes #40354
When running jit-diff with Hostx64/arm64 crossgen with
COMPlus_NGenDump=*
the following appears in the crossgen outputUnder debugger the following call stack
suggests that in
the assumption that
GTF_ICON_STATIC_HDL
refers to static fields is incorrect.In this particular case (
System.Char.get_Latin1CharInfo
), the static handle is address of the following byte array in(Note: there's some kind of GitHub bug where if you don't quote the above source links, it's impossible to update this comment)
category:correctness
theme:debug-dumps
skill-level:beginner
cost:small
The text was updated successfully, but these errors were encountered: