PPC/s390: interpreter: make interpreted frames distinguishable in the native stack
Port ada64b58 Original Commit Message: Before Turbofan/Ignition it was possible to use external profilers to sample running V8/Node.js processes and generate reports/FlameGraphs from that. It's still possible to do so, but non-optimized JavaScript functions appear in the stack as InterpreterEntryTrampoline. This commit adds a runtime flag which makes interpreted frames visible on the process' native stack as distinguishable functions, making the sampled data gathered by external profilers such as Linux perf and DTrace more useful. R=matheus@sthima.com.br, joransiu@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Change-Id: I0416b53c53248a5624061d0155712a3e2396c725 Reviewed-on: https://chromium-review.googlesource.com/1008045Reviewed-by: Joran Siu <joransiu@ca.ibm.com> Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#52551}
Showing
Please
register
or
sign in
to comment