Closed
Bug 993071
Opened 9 years ago
Closed 7 years ago
Add JIT-Optimization info to JS profiler
Categories
(Core :: JavaScript Engine: JIT, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: djvj, Unassigned)
Details
(Whiteboard: [leave open])
Attachments
(2 files, 1 obsolete file)
19.17 KB,
patch
|
luke
:
review+
|
Details | Diff | Splinter Review |
4.53 KB,
patch
|
luke
:
review+
|
Details | Diff | Splinter Review |
Add JIT optimization info to JS profiler. To start off, we want the profiler to identify traces which go through slow-paths in the scripts on stack. The implementation is pretty simple: push pseudostack entries before starting a slowpath, and pop after ending the slowpath.
Reporter | ||
Comment 1•9 years ago
|
||
Preparatory patch: rename MFunctionBoundary in Ion to MProfilerStackOp. FunctionBoundary doesn't make sense for annotating slowpaths within functions. Try run: https://tbpl.mozilla.org/?tree=Try&rev=925abe474e90
Attachment #8402853 -
Flags: review?(luke)
Reporter | ||
Comment 2•9 years ago
|
||
This patch modifies the usage of the pseudostack to allow js pseudostack entries to indicate if they are for optimized code or not. It uses the fact that for js entries, the |sp| field is expected to be null. The patch modifies this to allow |sp| to be either null or (void*)1, where a (void*)1 value indicates that it is for an optimized JS frame. Try run: https://tbpl.mozilla.org/?tree=Try&rev=439e69c25d2a
Attachment #8403347 -
Flags: review?(luke)
Reporter | ||
Comment 3•9 years ago
|
||
Comment on attachment 8403347 [details] [diff] [review] add-optimization-tier-to-profiler-pseudostack.patch Canceling review request on this as I just noticed some relevant try failures.
Attachment #8403347 -
Flags: review?(luke)
![]() |
||
Updated•9 years ago
|
Attachment #8402853 -
Flags: review?(luke) → review+
Reporter | ||
Comment 4•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/22a4fae1f56a
Whiteboard: [leave open]
Reporter | ||
Comment 5•9 years ago
|
||
Fixed version of previous patch. Minor change to sp() method to get this to pass. Same basic idea. Copying description from previous patch post: This patch modifies the usage of the pseudostack to allow js pseudostack entries to indicate if they are for optimized code or not. It uses the fact that for js entries, the |sp| field is expected to be null. The patch modifies this to allow |sp| to be either null or (void*)1, where a (void*)1 value indicates that it is for an optimized JS frame. Now passes try: https://tbpl.mozilla.org/?tree=Try&rev=841f374c2bff
Attachment #8403347 -
Attachment is obsolete: true
Attachment #8403530 -
Flags: review?(luke)
![]() |
||
Updated•9 years ago
|
Attachment #8403530 -
Flags: review?(luke) → review+
Reporter | ||
Comment 7•9 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/b7fd2d587e14
Comment 9•7 years ago
|
||
This has long landed.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•