Bug 1150654 - Add CantInlineNoSpecialization to distinguish natives for which there is no Ion specialization. (r=jandem)

This commit is contained in:
Shu-yu Guo 2015-04-08 20:36:20 -07:00
parent f0a35a775e
commit 80fbf5e7e0
2 changed files with 5 additions and 0 deletions

View File

@ -125,6 +125,7 @@ namespace JS {
_(CantInlineNativeBadType) \
_(CantInlineNativeNoTemplateObj) \
_(CantInlineBound) \
_(CantInlineNativeNoSpecialization) \
\
_(GenericSuccess) \
_(Inlined) \

View File

@ -398,6 +398,10 @@ IonBuilder::inlineNativeCall(CallInfo& callInfo, JSFunction* target)
if (native == js::simd_float32x4_storeXYZ)
return inlineSimdStore(callInfo, native, SimdTypeDescr::Float32x4, 3);
// Reaching here means we tried to inline a native for which there is no
// Ion specialization.
trackOptimizationOutcome(TrackedOutcome::CantInlineNativeNoSpecialization);
return InliningStatus_NotInlined;
}