Closed Bug 1150654 Opened 8 years ago Closed 8 years ago

new JIT optimizations display claims CantInlineNativeBadType for all DOM natives

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla40
Tracking Flags:
Tracking Status
firefox40 --- fixed

People

(Reporter: bzbarsky, Unassigned)

Details

Attachments

(1 file)

Add CantInlineUnknownNative reason to distinguish natives for which there is no Ion inline.
2.59 KB, patch
jandem
: review+
Details | Diff | Splinter Review 
Testcase:

  function f() { for (var i = 0; i < 100000; ++i) performance.now(); }
  f();
Comment on attachment 8588853 [details] [diff] [review]
Add CantInlineUnknownNative reason to distinguish natives for which there is no Ion inline.

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

Nice.
Attachment #8588853 - Flags: review?(jdemooij) → review+
https://hg.mozilla.org/mozilla-central/rev/c758e5c97a6c
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox40: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla40
You need to log in before you can comment on or make changes to this bug.