-
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
Change debug info default variable tracking system #2107
Conversation
I will open an issue to develop a baseline/contract/protocol so we can check no one downgrade/reduce/break debug info on optimize code with future changes. |
/azp list |
Commenter does not have sufficient privileges for PR 2107 in repo dotnet/runtime |
@dotnet/jit-contrib |
@dotnet-bot Test runtime |
/azp list |
/azp run runtime |
Commenter does not have sufficient privileges for PR 2107 in repo dotnet/runtime |
/azp run runtime |
Commenter does not have sufficient privileges for PR 2107 in repo dotnet/runtime |
/azp run runtime |
Commenter does not have sufficient privileges for PR 2107 in repo dotnet/runtime |
/azp run runtime |
Commenter does not have sufficient privileges for PR 2107 in repo dotnet/runtime |
/azp list |
Commenter does not have sufficient privileges for PR 2107 in repo dotnet/runtime |
/azp list |
Commenter does not have sufficient privileges for PR 2107 in repo dotnet/runtime |
/azp list |
Commenter does not have sufficient privileges for PR 2107 in repo dotnet/runtime |
/azp list |
Commenter does not have sufficient privileges for PR 2107 in repo dotnet/runtime |
/azp list |
These were the previous variable ranges
and these are new ones
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few comments that should be changed, but otherwise LGTM
Thanks @jkotas and @CarolEidt for the suggestions, I have applied them all. How do we proceed now? |
What is this growth with these fixes? LGTM otherwise. |
|
@briansull Can you please review this from the JIT perspective? |
/azp help |
Supported commands
See additional documentation. |
/azp run runtime |
Azure Pipelines successfully started running 1 pipeline(s). |
I reviewed the older code (under And I give my approval for checkin. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks Good.
@BruceForstall What should we do with the instances failing? |
You mean: what about test failures? What kind of failures? It looks like you set them to rerun? In general, I would rerun until they pass. Unless there are known problems such as documented in #702. |
@BruceForstall |
@BrianBohe Looks like only crossgen-comparison failed due to infra error. I'd go ahead and merge. |
Reverts dotnet#33021, which was a reversion of dotnet#2107. Fix the IG boundary sensitivity for debug emission. Allow debug info to be summarized in a way that makes it amenable to analyze with our jitutils tooling (namely, `jit-analyze`).
Varible Scope info is being disabled. Variable
Live Range is being enabled. Debug info generated
for debug code is the same, changes only impact on
optimized code.
Variable Live Range updates variable's location
each time something happens to variable's
liveness. For more information see
https://github.com/dotnet/runtime/blob/master/docs/design/features/variabletracking.md