| Value | Meaning |
|---|---|
| DEBUGINFOGCC_JIT_BOOL_OPTION_DEBUGINFO | If true, JITContext.compile() will attempt to do the right thing so that if you attach a debugger to the process, it will be able to inspect variables and step through your code. Note that you can’t step through code unless you set up source location information for the code (by creating and passing in JITLocation instances). |
| DUMP_INITIAL_TREEGCC_JIT_BOOL_OPTION_DUMP_INITIAL_TREE | If true, JITContext.compile() will dump its initial "tree" representation of your code to stderr, before any optimizations. |
| DUMP_INITIAL_GIMPLEGCC_JIT_BOOL_OPTION_DUMP_INITIAL_GIMPLE | If true, JITContext.compile() will dump its initial "gimple" representation of your code to stderr, before any optimizations are performed. The dump resembles C code. |
| DUMP_GENERATED_CODEGCC_JIT_BOOL_OPTION_DUMP_GENERATED_CODE | If true, JITContext.compile() will dump the final generated code to stderr, in the form of assembly language. |
| DUMP_SUMMARYGCC_JIT_BOOL_OPTION_DUMP_SUMMARY | If true, JITContext.compile() will print information to stderr on the actions it is performing, followed by a profile showing the time taken and memory usage of each phase. |
| DUMP_EVERYTHINGGCC_JIT_BOOL_OPTION_DUMP_EVERYTHING | If true, JITContext.compile() will dump copious amounts of information on what it’s doing to various files within a temporary directory. Use JITBoolOption.KEEP_INTERMEDIATES to see the results. The files are intended to be human-readable, but the exact files and their formats are subject to change. |
| SELFCHECK_GCGCC_JIT_BOOL_OPTION_SELFCHECK_GC | If true, libgccjit will aggressively run its garbage collector, to shake out bugs (greatly slowing down the compile). This is likely to only be of interest to developers of the library. |
| KEEP_INTERMEDIATESGCC_JIT_BOOL_OPTION_KEEP_INTERMEDIATES | If true, the JITContext will not clean up intermediate files written to the filesystem, and will display their location on stderr. |
Boolean options