Closed
Bug 679180
Opened 14 years ago
Closed 13 years ago
IonMonkey: add infallible method in LIR
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: h4writer, Assigned: h4writer)
Details
Attachments
(2 files)
|
4.62 KB,
patch
|
Details | Diff | Splinter Review | |
|
8.43 KB,
patch
|
Details | Diff | Splinter Review |
During talk in irc with dvander we decided it would be better to have sort of an abstraction for deciding when a bailout should get created.
1) add function "infallible" returning if a bailout is needed
2) adjust LAddI to reflect those changes
I would lean toward "fallible" instead, because usually we'll check:
if (ins->fallible())
Which looks better than:
if (!ins->infallible())
| Assignee | ||
Comment 2•14 years ago
|
||
Implementing adjustements.
Tomorrow I'll post the patch to adjust LUnbox/LDoubleUnbox/... to this.
(In reply to David Anderson [:dvander] from comment #1)
> I would lean toward "fallible" instead, because usually we'll check:
> if (ins->fallible())
>
> Which looks better than:
> if (!ins->infallible())
Did meant fallible, but didn't saw I made infallible of it until after posting.
Assignee: general → hv1989
Attachment #553403 -
Flags: review?(dvander)
| Assignee | ||
Comment 3•14 years ago
|
||
small nits:
- LAddI(true) instead of LAddI(1)
- Move JS_ASSERT(snapshot) into bailoutIf function
Implement LIR's:
- Unbox*
Attachment #553511 -
Flags: review?(dvander)
Updated•14 years ago
|
Attachment #553403 -
Flags: review?(dvander)
Updated•14 years ago
|
Attachment #553511 -
Flags: review?(dvander)
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•