-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Describe PGO kind in JitDisasm #73529
Conversation
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue Details@AndyAyersMS you asked to leave a mark in JitDisasm whether PGO is Static or Dynamic. With this PR it's now:
And since JitDisasm will be available in Release this is how users will be able to diagnose whether Dynamic PGO was kicked in or not
|
Co-authored-by: Jakob Botsch Nielsen <Jakob.botsch.nielsen@gmail.com>
CI failure is unrelated (#73247) |
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.
Thanks. For end users, relying on this still might be a challenge, if there's no easy access to the process stdout.
Also see #72056 which added support in ETW. |
@AndyAyersMS you asked to leave a mark in JitDisasm whether PGO is Static or Dynamic. With this PR it's now:
And since JitDisasm will be available in Release this is how users will be able to diagnose whether Dynamic PGO was kicked in or not