-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Avoiding printing twice variable live range #77447
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
Conversation
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsBefore this PR we dumped the information reported to the vm followed by all the variables live ranges. These are practically the same information, so I am adding information to what is being reported, and removing the print of the variable live ranges. Leaving Before: After:
|
jakobbotsch
left a comment
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.
LGTM but looks like the formatting job isn't happy.
|
@jakobbotsch I can't understand the problem. The error I find is: But it is not happening in my other PRs. |
|
I ran |
Ah, looks like you got caught in the jitutils TFM update (dotnet/jitutils#357). The problem in the pipeline was fixed by #77511 |
|
@BrianBohe looks like this broke JITDUMP, it fails for me with for a simple program: unsafe class Proga
{
static void Main()
{
for (int i = 0; i < 100; i++)
{
new Proga().Test1();
Thread.Sleep(16);
}
}
static Guid g = Guid.NewGuid();
[MethodImpl(MethodImplOptions.NoInlining)]
Guid Test1() => g;
}
Does not repro if I revert your changes by hands. |
I took this code out of PR77289.
Before this PR we dumped the information reported to the vm followed by all the variables live ranges. These are practically the same information, so I am adding information to what is being reported, and removing the print of the variable live ranges. Leaving
dumpLvaVariableLiveRangesfor debug purposes.Before:
After: