Closed Bug 2023676 Opened 7 months ago Closed 7 months ago

Consider adding an "Any" type to MIROps.yaml

Categories

(Core :: JavaScript Engine: JIT, task, P3)

task

Tracking

()

RESOLVED FIXED
151 Branch
Tracking Status
firefox151 --- fixed

People

(Reporter: anba, Assigned: anba)

References

(Blocks 1 open bug)

Details

Attachments

(1 external file)

https://phabricator.services.mozilla.com/D287160 (bug 2022580) adds new assertions to ensure operands of MIR instructions without a type policy are constructed with the correct type. The assertions are applied for all types except MIRType::Value, because instructions like IsNullOrUndefined currently have MIRType::Value typed operands which can actually be any type, including unboxed types. We should consider adding a separate Any type to MIROps.yaml to support the IsNullOrUndefined use case. The Any type is internal to MIROps.yaml, there won't be a corresponding MIRType::Any type added.

Blocks: sm-jits
Severity: -- → N/A
Priority: -- → P3
Blocks: sm-opt-jits
No longer blocks: sm-jits
Assignee: nobody → andrebargull
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 7 months ago
Resolution: --- → FIXED
Target Milestone: --- → 151 Branch
QA Whiteboard: [qa-triage-done-c152/b151]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: