Closed Bug 659941 Opened 14 years ago Closed 13 years ago

Function() functions should be compileAndGo

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 646597

People

(Reporter: bhackett1024, Unassigned)

References

Details

Functions created by Function() always run against the active top level scope at the point they were created, so should always be compileAndGo. Currenty, we never make them into compileAndGo scripts, which inhibits type inference and JIT optimizations.
Blocks: 619423
Note the patch in bug 639720 (though that bug seems to have somewhat wider scope).
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Reopened to spin this problem off from bug 639720, which is more about why certain NAME accesses are slow in the mjit rather than why those NAME accesses are being generated in the first place.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Requesting tracking for Fx9. With TI landed the compiler is much more sensitive to whether code is compileAndGo --- global accesses have sped up, generic name accesses have slowed down some, and type information is much more precise in compileAndGo scripts. This should be a simple fix.
tracking-firefox9: --- → ?
Status: REOPENED → RESOLVED
Closed: 14 years ago → 13 years ago
Resolution: --- → DUPLICATE
Removing tracking as we were tracking the original (bug 646597) but no longer need to (see that bug).
tracking-firefox9: + → ---
You need to log in before you can comment on or make changes to this bug.