Hi Jay, A change to Ignition/TF is something that's been discussed and will be evaluated as Ignition continues next year. Lots to do before it's an option.
The lack of paths between Ignition and full-code/crankshaft goes back to the motivation for Ignition (footprint on mobile) and keeping it simple enough to make progress on. Cheers Orion On Tue, Dec 29, 2015 at 10:41 PM, <[email protected]> wrote: > Thanks for the comment. Now it prints out bytecodes, but, as you warned, > it fails to run my test script to the end. > If there is no path between ignition and Full-Code/Crankshaft, does it > mean that the long-term plan is to replace Full-Code/Crankshaft with > Ignition/Turbofan? > > Thanks, > Jay > > On Tuesday, December 29, 2015 at 3:13:19 PM UTC-6, Orion Hodson wrote: >> >> Hi Jay >> >> To pass code through Ignition, the command-line also needs to specify a >> filter to identify which function should be passed to ignition, e.g. >> >> d8 --ignition --ignition-filter=foo --print-bytecode foo.js >> >> The code also needs to call the function named in the filter. To run all >> code through Ignition, specify the --ignition-filter=*. >> >> The --print-bytecode flag works best with a debug build as it'll show the >> bytecode and constant array rather than just top-level metadata. >> >> There is a path to generate optimized code using TurboFan taking bytecode >> from Ignition as input: >> >> src/compiler/bytecode-graph-builder.{h,cc} >> >> For now, the command-line needs to include the Ignition arguments with >> --always-opt which will force optimized compilation from bytecode. >> Support for profiling interpreted code is coming and will selectively >> optimize hot code. >> >> There are no paths between ignition and full-code/crankshaft and no plans >> in this direction. >> >> Ignition is a work in progress and should fail hard when the limits of >> the implementation are hit. All effort to date has been on features, >> there's a long way to go on performance. It works on all v8 platforms >> except x87. >> >> Thanks >> Orion >> >> On Tue, Dec 29, 2015 at 5:51 PM, Jay <[email protected]> wrote: >> >>> Hi, >>> >>> I want to try Ignition interpreter and am having trouble enabling it. >>> I thought the following set of flags should print some logs, but it >>> gives me nothing. >>> >>> --ignition --print_bytecode >>> >>> I tried running on a debugger and setting a breakpoint at >>> *Interpreter::MakeBytecode()*, but it never reaches the function. >>> How can I properly enable Ignition interpreter? Does it not support x64? >>> And I was also wondering if there is any circumstance in which you want >>> to disable optimizing compilers (Crankshaft and Turbofan) and use the >>> lower-tier only (Ignition or Full Compiler). >>> >>> Thanks, >>> Jay >>> >>> -- >>> -- >>> 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. >>> >> >> -- > -- > 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. > -- -- 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.
