Closed
Bug 734415
Opened 13 years ago
Closed 13 years ago
IonMonkey: Specialize phis with int32 and double operands as double
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: jandem, Assigned: jandem)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
2.92 KB,
patch
|
dvander
:
review+
|
Details | Diff | Splinter Review |
With this patch Kraken gaussian-blur drops from 290 ms to 185 ms.
Attachment #604442 -
Flags: review?(dvander)
Comment on attachment 604442 [details] [diff] [review]
Patch
Review of attachment 604442 [details] [diff] [review]:
-----------------------------------------------------------------
Nice.
Attachment #604442 -
Flags: review?(dvander) → review+
Assignee | ||
Comment 2•13 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 3•13 years ago
|
||
If I'm reading this diff right.
Among other things you changed the following:
for (...) {
if (type == MIRType_None) {
...
} else if (type != in->type()) {
...
}
}
into
for (...) {
if (type == MIRType_None) {
...
continue;
}
if (type != in->type()) {
...
}
}
Also with changes on the "..." lines.
But I'm curious why altering "else if" into a "continue".
Is there a specific reason for doing this?
Assignee | ||
Comment 4•13 years ago
|
||
(In reply to Hannes Verschore from comment #3)
>
> But I'm curious why altering "else if" into a "continue".
> Is there a specific reason for doing this?
No important reason, it just seemed a bit more readable and it matched the other "if .. continue;" before it.
Comment 5•13 years ago
|
||
(In reply to Jan de Mooij (:jandem) from comment #4)
> No important reason, it just seemed a bit more readable and it matched the
> other "if .. continue;" before it.
Ah ... I was thinking there were some style rules unknown to me involved.
Nice win on kraken btw.
You need to log in
before you can comment on or make changes to this bug.
Description
•