Thanks! Another question: what is the difference between using --no-opt and --minimal (the latter implies --no-opt and --no-use-ic)? Isn't inline caching incompatible with interpreter execution anyway?
On Tuesday, July 3, 2018 at 7:22:03 PM UTC+3, Leszek Swirski wrote: > > Hi Andrey, > > --no-opt is what you're looking for (a JS flag, so passed by --js-flags in > Chrome). > > Cheers, > Leszek > > On Tue, Jul 3, 2018 at 5:18 PM Andrey Logvinov <[email protected] > <javascript:>> wrote: > >> Is there a way (perhaps using --js-flags) to force interpreter-only >> execution of Ignition bytecode, i.e. without ever attempting to JIT-compile >> it to optimized version with Turbofan? >> >> -- >> -- >> v8-dev mailing list >> [email protected] <javascript:> >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- -- 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/d/optout.
