Closed
Bug 474829
Opened 17 years ago
Closed 14 years ago
Add internal profiling support to TraceMonkey
Categories
(Core :: JavaScript Engine, enhancement)
Core
JavaScript Engine
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: dmandelin, Assigned: dmandelin)
Details
Attachments
(3 files)
|
5.13 KB,
patch
|
Details | Diff | Splinter Review | |
|
2.55 KB,
patch
|
Details | Diff | Splinter Review | |
|
4.60 KB,
patch
|
Details | Diff | Splinter Review |
For understanding perf and perf problems, I've found it incredibly useful to be able to know things like how much time is spent on trace, how many ops are executed on trace, etc. I have some personal patches for this. They aren't clean enough to be landed but I can put them here now and work on that after the 3.1 bug fix push is done.
By the way, this kind of instrumentation should be available in opt builds and not just debug builds.
There are some other useful things we could do using the same basic infrastructure like record the stream of JSOP codes that are executed, which would help delta debug semantic bugs.
| Assignee | ||
Comment 1•17 years ago
|
||
| Assignee | ||
Comment 2•17 years ago
|
||
| Assignee | ||
Comment 3•17 years ago
|
||
Comment 4•14 years ago
|
||
Obsolete with the removal of tracejit.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•