Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
Maintained by go/gitwatcher - Please do not modify manually [ID: 530458]
Maintained by go/gitwatcher - Please do not modify manually [ID: 530406]
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
Profiling is currently complicated by most hotspots being in dynamically generated code. Since there's no static debug info for Reactor routines, profilers don't know the calling convention and thus can't (or won't) reconstruct the call stack. Even if we had the call stacks, it would not discern between routines that are called from the same location.
Reactor used to support the AMD CodeAnalyst profiler, which featured JIT profiling, but that product has been discontinued and the AMD μProf replacement doesn't appear to support JIT.
Intel's