Open
Bug 1341789
Opened 9 years ago
Updated 7 months ago
CacheIR: Don't eagerly emit IR with maybeGuardInt32Index
Categories
(Core :: JavaScript Engine: JIT, defect, P3)
Core
JavaScript Engine: JIT
Tracking
()
NEW
| Performance Impact | none |
People
(Reporter: evilpies, Unassigned)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
|
10.86 KB,
patch
|
Details | Diff | Splinter Review |
Currently maybeGuardInt32Index will always emit a index guard when called. This is too restrictive. For example currently we can't move tryAttachProxyElement after tryAttachTypedElement. This also prevents us from optimizing indexing with a string into primitive strings or magic arguments.
|
Reporter | |
Comment 1•9 years ago
|
||
I tried this out before, but I don't like the way it turned out much. I am not sure arguments we should pass to the tryAttachXXX functions.
|
||
Updated•9 years ago
|
Whiteboard: [qf-]
|
||
Updated•9 years ago
|
Priority: -- → P3
|
||
Updated•4 years ago
|
Performance Impact: --- → -
Whiteboard: [qf-]
|
||
Updated•3 years ago
|
Severity: normal → S3
|
||
Comment 2•7 months ago
|
||
Still relevant?
You need to log in
before you can comment on or make changes to this bug.
Description
•