This change will trigger OSR faster and most of all, it will trigger OSR for big functions: on ARM, with the LUA benchmark, a function is very big and, when ticks equals 255, the function is still not optimized (and on IA32, it is optimized just before ticks equals 255). We explored several ways to change that: - modify the kOSRCodeSizeAllowancePerTick (as you did), - modify the kCodeSizeMultiplier from 142 to 162, - allow ticks to be greater than 255.
It seems that the third solution is better because it removes the limit to do OSR. It can be linked to the other solutions (and the 3 solutions can be done together). -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
