Jan de Mooij a261b8dc01 Bug 1551499 - Support Baseline Interpreter code in the profiler. r=djvj ... 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		2019-06-21 16:13:48 +00:00
..
core	Bug 1551499 - Support Baseline Interpreter code in the profiler. r=djvj	2019-06-21 16:13:48 +00:00
gecko	Bug 1540731 - Part 2: Move toplevel actors to override ActorDestroy, r=froydnj	2019-05-21 17:04:21 +00:00
lul	Bug 1549232 - Only use profiler_current_{process,thread}_id in the Gecko Profiler instead of alternatives - r=mstange	2019-05-09 18:26:15 +00:00
public	Backed out 4 changesets (bug 1545582) for causing spidermonkey bustages CLOSED TREE	2019-06-20 19:39:54 +03:00
rust-helper	Bug 1505719 - Try harder when computing breakpad IDs for Android system libraries. r=ted	2018-12-03 19:21:44 +00:00
tasktracer	Bug 1549232 - Only use profiler_current_{process,thread}_id in the Gecko Profiler instead of alternatives - r=mstange	2019-05-09 18:26:15 +00:00
tests	Backed out 4 changesets (bug 1545582) for causing spidermonkey bustages CLOSED TREE	2019-06-20 19:39:54 +03:00
moz.build	Bug 1549232 - Only use profiler_current_{process,thread}_id in the Gecko Profiler instead of alternatives - r=mstange	2019-05-09 18:26:15 +00:00