Open
Bug 1337812
Opened 9 years ago
Updated 4 months ago
CacheIR: consider passing GetElem/SetElem key as argument
Categories
(Core :: JavaScript Engine: JIT, defect, P3)
Core
JavaScript Engine: JIT
Tracking
()
NEW
| Performance Impact | none |
People
(Reporter: jandem, Unassigned)
References
(Blocks 1 open bug)
Details
GetPropIRGenerator and SetPropIRGenerator currently call {g,s}etElemKeyValueId to get the key's OperandId.
It might be nicer to pass it explicitly to the try* methods as Maybe<ValOperandId> and then pass it to maybeEmitIdGuard. Maybe<> because we don't have a key id when it's a GetProp/SetProp IC.
|
||
Updated•9 years ago
|
Priority: -- → P3
|
||
Updated•9 years ago
|
Whiteboard: [qf-]
|
||
Comment 1•8 years ago
|
||
Bug 1169745 adds similar get/set for super receiver and should be cleaned up at same time.
|
||
Updated•4 years ago
|
Performance Impact: --- → -
Whiteboard: [qf-]
|
||
Updated•3 years ago
|
Severity: normal → S3
|
||
Comment 2•4 months ago
|
||
Still relevant?
You need to log in
before you can comment on or make changes to this bug.
Description
•