mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-12-25 17:43:44 +00:00
a261b8dc01
Because the return address cannot be used to uniquely identify script/pc, this is unfortunately quite different from what we do for Baseline/Ion code. The strategy is as follows: * When the profiler is enabled, ensure each JitScript has a pointer to the profile string (released when the script is finalized). * The BaselineInterpreter code is registered with the JitcodeMap. * The profiler code treats interpreter frames like C++ Interpreter frames, instead of doing the return address based mapping. Differential Revision: https://phabricator.services.mozilla.com/D31052 --HG-- extra : moz-landing-system : lando |
||
---|---|---|
.. | ||
vtune | ||
EHABIStackWalk.cpp | ||
EHABIStackWalk.h | ||
memory_hooks.cpp | ||
memory_hooks.h | ||
PageInformation.cpp | ||
PageInformation.h | ||
platform-linux-android.cpp | ||
platform-macos.cpp | ||
platform-win32.cpp | ||
platform.cpp | ||
platform.h | ||
PlatformMacros.h | ||
ProfileBuffer.cpp | ||
ProfileBuffer.h | ||
ProfileBufferEntry.cpp | ||
ProfileBufferEntry.h | ||
ProfiledThreadData.cpp | ||
ProfiledThreadData.h | ||
ProfileJSONWriter.cpp | ||
ProfilerBacktrace.cpp | ||
ProfilerBacktrace.h | ||
ProfilerMarker.h | ||
ProfilerMarkerPayload.cpp | ||
RegisteredThread.cpp | ||
RegisteredThread.h | ||
shared-libraries-linux.cc | ||
shared-libraries-macos.cc | ||
shared-libraries-win32.cc | ||
ThreadInfo.h | ||
VTuneProfiler.cpp | ||
VTuneProfiler.h |