Uh oh!
There was an error while loading. Please reload this page.
Avoiding printing twice variable live range - #77447
Conversation
ghost
commented
Oct 25, 2022
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.
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. |
BrianBohe
commented
Oct 28, 2022
I ran |
jakobbotsch
commented
Oct 28, 2022
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: unsafeclassProga{staticvoidMain(){for(inti=0;i<100;i++){newProga().Test1();Thread.Sleep(16);}}staticGuidg=Guid.NewGuid();[MethodImpl(MethodImplOptions.NoInlining)]GuidTest1()=>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: