Closed Bug 1009899 Opened 10 years ago Closed 10 years ago

Don't unnecessarily freeze inlining done during definite properties analysis

Categories

(Core :: JavaScript Engine: JIT, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla32

People

(Reporter: bhackett1024, Assigned: bhackett1024)

References

Details

Attachments

(1 file)

Attached patch patchSplinter Review
Bug 1008339 regressed octane-deltablue because some of the constraints it added caused definite property information to be invalidated on some important scripts.  These constraints aren't actually necessary though, as they are accounting for inlining done in the definite properties analysis which happens after all of the definite properties have been added.
Attachment #8422053 - Flags: review?(jdemooij)
Comment on attachment 8422053 [details] [diff] [review]
patch

Review of attachment 8422053 [details] [diff] [review]:
-----------------------------------------------------------------

r=me with the assert below added.

::: js/src/jit/IonAnalysis.cpp
@@ +2375,5 @@
>          if (!handled)
>              break;
> +
> +        if (slotSpan != baseobj->slotSpan())
> +            lastAddedBlock = ins->block()->id();

Assert ins->block()->id() >= lastAddedBlock before this line.
Attachment #8422053 - Flags: review?(jdemooij) → review+
https://hg.mozilla.org/mozilla-central/rev/59ba25ff5a10
Assignee: nobody → bhackett1024
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla32
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: