JSStackFrame Evisceration: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 43: Line 43:
|-
|-
| [https://bugzilla.mozilla.org/show_bug.cgi?id=546848 annotation]
| [https://bugzilla.mozilla.org/show_bug.cgi?id=546848 annotation]
| 0
| 3
| sayrer
| sayrer
| Trivial if we can remove callers in nsScriptSecurityManager.
| Trivial if we can remove callers in nsScriptSecurityManager. Alas, that is not trivial, so this is going to take a while.
|-
|-
| [https://bugzilla.mozilla.org/show_bug.cgi?id=540675 callerVersion]
| [https://bugzilla.mozilla.org/show_bug.cgi?id=540675 callerVersion]

Revision as of 16:21, 15 July 2010

This would leave sizeof(JSStackFrame) == 6 words.

Members to remove

Sorted in estimated order of benefit / difficulty:

Task Size (wks) Assignee Note
argc/argv 1.5 lw Requires CallSegment (CallStack) changes, educate decompiler
thisv .5 lw Depends on argv/argc
fun, script .5 lw Depends on thisv
ncode .1 dvander Merge it with savedPC in method-jit
displaySave 1 cdleary Remove display optimization for great justice!
hookData .2 lw Just use js::Invoke and use a local variable
annotation 3 sayrer Trivial if we can remove callers in nsScriptSecurityManager. Alas, that is not trivial, so this is going to take a while.
callerVersion .5 Mostly the challenge is just understanding the actual use case.
blockChain 1 lw A bit tricky
rval 1 Tricky
imacpc 1 Perhaps push on the expression stack like JSOP_GOSUB does

Method-jit changes

  • PIC for fast natives calls
  • PIC/fast path for interpreted inline call