A gcc_jit_param represents a parameter to a function.
In preparation for creating a function, create a new parameter of the given type and name.
Parameters are lvalues, and thus are also rvalues (and objects), so the following upcasts are available:
Upcasting from param to lvalue.
Upcasting from param to rvalue.
Upcasting from param to object.
A gcc_jit_function represents a function - either one that we’re creating ourselves, or one that we’re referencing.
Create a gcc_jit_function with the given name and parameters.
This enum controls the kind of function created, and has the following values:
- GCC_JIT_FUNCTION_EXPORTED¶
Function is defined by the client code and visible by name outside of the JIT.
- GCC_JIT_FUNCTION_INTERNAL¶
Function is defined by the client code, but is invisible outside of the JIT. Analogous to a “static” function.
- GCC_JIT_FUNCTION_IMPORTED¶
Function is not defined by the client code; we’re merely referring to it. Analogous to using an “extern” function from a header file.
- GCC_JIT_FUNCTION_ALWAYS_INLINE¶
Function is only ever inlined into other functions, and is invisible outside of the JIT.
Analogous to prefixing with inline and adding __attribute__((always_inline))
Inlining will only occur when the optimization level is above 0; when optimization is off, this is essentially the same as GCC_JIT_FUNCTION_INTERNAL.
Upcasting from function to object.
Get the param of the given index (0-based).
Emit the function in graphviz format to the given path.
Create a new local variable within the function, of the given type and name.
A gcc_jit_block represents a basic block within a function i.e. a sequence of statements with a single entry point and a single exit point.
The first basic block that you create within a function will be the entrypoint.
Each basic block that you create within a function must be terminated, either with a conditional, a jump, or a return.
It’s legal to have multiple basic blocks that return within one function.
Create a basic block of the given name. The name may be NULL, but providing meaningful names is often helpful when debugging: it may show up in dumps of the internal representation, and in error messages.
Upcast from block to object.
Which function is this block within?
Add evaluation of an rvalue, discarding the result (e.g. a function call that “returns” void).
This is equivalent to this C code:
(void)expression;
Add evaluation of an rvalue, assigning the result to the given lvalue.
This is roughly equivalent to this C code:
lvalue = rvalue;
Add evaluation of an rvalue, using the result to modify an lvalue.
This is analogous to “+=” and friends:
lvalue += rvalue;
lvalue *= rvalue;
lvalue /= rvalue;
etc. For example:
/* "i++" */
gcc_jit_block_add_assignment_op (
loop_body, NULL,
i,
GCC_JIT_BINARY_OP_PLUS,
gcc_jit_context_one (ctxt, int_type));
Add a no-op textual comment to the internal representation of the code. It will be optimized away, but will be visible in the dumps seen via GCC_JIT_BOOL_OPTION_DUMP_INITIAL_TREE and GCC_JIT_BOOL_OPTION_DUMP_INITIAL_GIMPLE, and thus may be of use when debugging how your project’s internal representation gets converted to the libgccjit IR.
Terminate a block by adding evaluation of an rvalue, branching on the result to the appropriate successor block.
This is roughly equivalent to this C code:
if (boolval)
goto on_true;
else
goto on_false;
block, boolval, on_true, and on_false must be non-NULL.
Terminate a block by adding a jump to the given target block.
This is roughly equivalent to this C code:
goto target;
Terminate a block by adding evaluation of an rvalue, returning the value.
This is roughly equivalent to this C code:
return expression;
Terminate a block by adding a valueless return, for use within a function with “void” return type.
This is equivalent to this C code:
return;