As a security precaution, we have turned on the setting "Require API key authentication for API requests" for everyone. If this has broken something, please contact
Last Comment Bug 762887 - IonMonkey: Add infallible MUnbox after known-object type barrier
: IonMonkey: Add infallible MUnbox after known-object type barrier
Product: Core
Classification: Components
Component: JavaScript Engine (show other bugs)
: unspecified
: All All
: -- normal (vote)
: ---
Assigned To: Jan de Mooij [:jandem]
: Jason Orendorff [:jorendorff]
Depends on:
Blocks: IonSpeed
  Show dependency treegraph
Reported: 2012-06-08 06:45 PDT by Jan de Mooij [:jandem]
Modified: 2012-06-09 02:10 PDT (History)
2 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

Patch (1.69 KB, patch)
2012-06-08 06:45 PDT, Jan de Mooij [:jandem]
dvander: review+
Details | Diff | Splinter Review

Description User image Jan de Mooij [:jandem] 2012-06-08 06:45:59 PDT
Created attachment 631370 [details] [diff] [review]

If a type barrier has type "object" (but not "any object") we have to use MTypeBarrier instead of MUnbox because we have to test the object types. This patch adds an infallible unbox after the type barrier to avoid a bunch of fallible unbox instructions inside a hot loop on SS-fannkuch.
Comment 1 User image Jan de Mooij [:jandem] 2012-06-09 02:10:06 PDT

Note You need to log in before you can comment on or make changes to this bug.