| Value | Meaning |
|---|---|
| GCC_JIT_BOOL_OPTION_DEBUGINFO | If true, gcc_jit_context_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 gcc_jit_location instances). |
| GCC_JIT_BOOL_OPTION_DUMP_INITIAL_TREE | If true, gcc_jit_context_compile will dump its initial "tree" representation of your code to stderr (before any optimizations). |
| GCC_JIT_BOOL_OPTION_DUMP_INITIAL_GIMPLE | If true, gcc_jit_context_compile will dump the "gimple" representation of your code to stderr, before any optimizations are performed. The dump resembles C code. |
| GCC_JIT_BOOL_OPTION_DUMP_GENERATED_CODE | If true, gcc_jit_context_compile will dump the final generated code to stderr, in the form of assembly language. |
| GCC_JIT_BOOL_OPTION_DUMP_SUMMARY | If true, gcc_jit_context_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. |
| GCC_JIT_BOOL_OPTION_DUMP_EVERYTHING | If true, gcc_jit_context_compile will dump copious amount of information on what it's doing to various files within a temporary directory. Use GCC_JIT_BOOL_OPTION_KEEP_INTERMEDIATES (see below) to see the results. The files are intended to be human-readable, but the exact files and their formats are subject to change. |
| GCC_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. It is used when running the selftest suite. |
| GCC_JIT_BOOL_OPTION_KEEP_INTERMEDIATES | If true, gcc_jit_context_release will not clean up intermediate files written to the filesystem, and will display their location on stderr. |
| GCC_JIT_NUM_BOOL_OPTIONS |