IC. The optimization in TurboFan is likely going to stick. Keep in mind that this does not mean that try/catch magically gets faster though. Do you have performance comparisons for AMP for try/catch? That would be highly interesting.
Cheers, Michael On Monday, July 18, 2016 at 5:36:02 PM UTC+2, Ali Ghassemi wrote: > > Performance is fairly important in AMP (https://www.ampproject.org/) and > we try to optimize the JS code as much as possible. Currently we have > externed multiple try-catch statements out of busy functions and have a > small Closure compiler customization so it does not inline them again. > Having this optimization ship will mean one less thing to worry about when > writing code. > > Thanks! > -Ali > On Monday, July 18, 2016 at 7:55:17 AM UTC-7, Michael Hablich wrote: >> >> What is the reason the optimization is important to you? >> >> On Monday, July 18, 2016 at 3:14:29 PM UTC+2, Ali Ghassemi wrote: >>> >>> Hi V8 team, >>> >>> I am just wondering how I can find out when/if Try-Catch optimization >>> will ship with Turbofan/V8/Chrome. I know there has been a few attempts to >>> ship it and the latest is https://codereview.chromium.org/1996373002 >>> but I can't tell ultimately what version of Chrome is planned to have that >>> change. >>> >>> Thanks, >>> Ali >>> >> -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" 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/d/optout.
