From f51703a8f80c9935f27148bb53ec7591716fd519 Mon Sep 17 00:00:00 2001 From: David Malcolm Date: Tue, 17 May 2016 19:17:19 +0000 Subject: [PATCH] jit: document gcc_jit_context_new_call_through_ptr gcc/jit/ChangeLog: * docs/topics/expressions.rst (Function calls): Document gcc_jit_context_new_call_through_ptr. * docs/_build/texinfo/libgccjit.texi: Regenerate. From-SVN: r236341 --- gcc/jit/ChangeLog | 6 + gcc/jit/docs/_build/texinfo/libgccjit.texi | 763 +++++++++++---------- gcc/jit/docs/topics/expressions.rst | 16 + 3 files changed, 411 insertions(+), 374 deletions(-) diff --git a/gcc/jit/ChangeLog b/gcc/jit/ChangeLog index d7a06398adb..ae0a5539f39 100644 --- a/gcc/jit/ChangeLog +++ b/gcc/jit/ChangeLog @@ -1,3 +1,9 @@ +2016-05-17 David Malcolm + + * docs/topics/expressions.rst (Function calls): Document + gcc_jit_context_new_call_through_ptr. + * docs/_build/texinfo/libgccjit.texi: Regenerate. + 2016-05-13 David Malcolm * jit-playback.h: Within namespace gcc:jit::playback... diff --git a/gcc/jit/docs/_build/texinfo/libgccjit.texi b/gcc/jit/docs/_build/texinfo/libgccjit.texi index 2043d664a04..f5c35497277 100644 --- a/gcc/jit/docs/_build/texinfo/libgccjit.texi +++ b/gcc/jit/docs/_build/texinfo/libgccjit.texi @@ -19,7 +19,7 @@ @copying @quotation -libgccjit 6.0.0 (experimental 20160108), January 19, 2016 +libgccjit 7.0.0 (experimental 20160517), May 17, 2016 David Malcolm @@ -7034,13 +7034,28 @@ gcc_jit_block_add_eval ( @end cartouche @end deffn +@geindex gcc_jit_context_new_call_through_ptr (C function) +@anchor{topics/expressions gcc_jit_context_new_call_through_ptr}@anchor{ae} +@deffn {C Function} gcc_jit_rvalue * gcc_jit_context_new_call_through_ptr (gcc_jit_context@w{ }*ctxt, gcc_jit_location@w{ }*loc, gcc_jit_rvalue@w{ }*fn_ptr, int@w{ }numargs, gcc_jit_rvalue@w{ }**args) + +Given an rvalue of function pointer type, and the given table of +argument rvalues, construct a call to the function pointer, with the +result as an rvalue. + +@cartouche +@quotation Note +The same caveat as for @pxref{ac,,gcc_jit_context_new_call()} applies. +@end quotation +@end cartouche +@end deffn + @node Type-coercion,,Function calls,Rvalues -@anchor{topics/expressions type-coercion}@anchor{ae} +@anchor{topics/expressions type-coercion}@anchor{af} @subsubsection Type-coercion @geindex gcc_jit_context_new_cast (C function) -@anchor{topics/expressions gcc_jit_context_new_cast}@anchor{af} +@anchor{topics/expressions gcc_jit_context_new_cast}@anchor{b0} @deffn {C Function} gcc_jit_rvalue * gcc_jit_context_new_cast (gcc_jit_context@w{ }*ctxt, gcc_jit_location@w{ }*loc, gcc_jit_rvalue@w{ }*rvalue, gcc_jit_type@w{ }*type) Given an rvalue of T, construct another rvalue of another type. @@ -7065,7 +7080,7 @@ P* <-> Q*, for pointer types P and Q @end deffn @node Lvalues,Working with pointers structs and unions,Rvalues,Expressions -@anchor{topics/expressions lvalues}@anchor{b0} +@anchor{topics/expressions lvalues}@anchor{b1} @subsection Lvalues @@ -7079,21 +7094,21 @@ a storage area (such as a variable). It is also usable as an rvalue, where the rvalue is computed by reading from the storage area. @geindex gcc_jit_lvalue_as_object (C function) -@anchor{topics/expressions gcc_jit_lvalue_as_object}@anchor{b1} +@anchor{topics/expressions gcc_jit_lvalue_as_object}@anchor{b2} @deffn {C Function} gcc_jit_object * gcc_jit_lvalue_as_object (gcc_jit_lvalue@w{ }*lvalue) Upcast an lvalue to be an object. @end deffn @geindex gcc_jit_lvalue_as_rvalue (C function) -@anchor{topics/expressions gcc_jit_lvalue_as_rvalue}@anchor{b2} +@anchor{topics/expressions gcc_jit_lvalue_as_rvalue}@anchor{b3} @deffn {C Function} gcc_jit_rvalue * gcc_jit_lvalue_as_rvalue (gcc_jit_lvalue@w{ }*lvalue) Upcast an lvalue to be an rvalue. @end deffn @geindex gcc_jit_lvalue_get_address (C function) -@anchor{topics/expressions gcc_jit_lvalue_get_address}@anchor{b3} +@anchor{topics/expressions gcc_jit_lvalue_get_address}@anchor{b4} @deffn {C Function} gcc_jit_rvalue * gcc_jit_lvalue_get_address (gcc_jit_lvalue@w{ }*lvalue, gcc_jit_location@w{ }*loc) Take the address of an lvalue; analogous to: @@ -7113,12 +7128,12 @@ in C. @end menu @node Global variables,,,Lvalues -@anchor{topics/expressions global-variables}@anchor{b4} +@anchor{topics/expressions global-variables}@anchor{b5} @subsubsection Global variables @geindex gcc_jit_context_new_global (C function) -@anchor{topics/expressions gcc_jit_context_new_global}@anchor{b5} +@anchor{topics/expressions gcc_jit_context_new_global}@anchor{b6} @deffn {C Function} gcc_jit_lvalue * gcc_jit_context_new_global (gcc_jit_context@w{ }*ctxt, gcc_jit_location@w{ }*loc, enum gcc_jit_global_kind@w{ }kind, gcc_jit_type@w{ }*type, const char@w{ }*name) Add a new global variable of the given type and name to the context. @@ -7131,22 +7146,22 @@ The "kind" parameter determines the visibility of the "global" outside of the @pxref{16,,gcc_jit_result}: @geindex gcc_jit_global_kind (C type) -@anchor{topics/expressions gcc_jit_global_kind}@anchor{b6} +@anchor{topics/expressions gcc_jit_global_kind}@anchor{b7} @deffn {C Type} enum gcc_jit_global_kind @end deffn @geindex GCC_JIT_GLOBAL_EXPORTED (C macro) -@anchor{topics/expressions GCC_JIT_GLOBAL_EXPORTED}@anchor{b7} +@anchor{topics/expressions GCC_JIT_GLOBAL_EXPORTED}@anchor{b8} @deffn {C Macro} GCC_JIT_GLOBAL_EXPORTED Global is defined by the client code and is visible by name outside of this JIT context via -@pxref{b8,,gcc_jit_result_get_global()} (and this value is required for +@pxref{b9,,gcc_jit_result_get_global()} (and this value is required for the global to be accessible via that entrypoint). @end deffn @geindex GCC_JIT_GLOBAL_INTERNAL (C macro) -@anchor{topics/expressions GCC_JIT_GLOBAL_INTERNAL}@anchor{b9} +@anchor{topics/expressions GCC_JIT_GLOBAL_INTERNAL}@anchor{ba} @deffn {C Macro} GCC_JIT_GLOBAL_INTERNAL Global is defined by the client code, but is invisible @@ -7156,7 +7171,7 @@ context and within child contexts. @end deffn @geindex GCC_JIT_GLOBAL_IMPORTED (C macro) -@anchor{topics/expressions GCC_JIT_GLOBAL_IMPORTED}@anchor{ba} +@anchor{topics/expressions GCC_JIT_GLOBAL_IMPORTED}@anchor{bb} @deffn {C Macro} GCC_JIT_GLOBAL_IMPORTED Global is not defined by the client code; we're merely @@ -7166,12 +7181,12 @@ header file. @end deffn @node Working with pointers structs and unions,,Lvalues,Expressions -@anchor{topics/expressions working-with-pointers-structs-and-unions}@anchor{bb} +@anchor{topics/expressions working-with-pointers-structs-and-unions}@anchor{bc} @subsection Working with pointers, structs and unions @geindex gcc_jit_rvalue_dereference (C function) -@anchor{topics/expressions gcc_jit_rvalue_dereference}@anchor{bc} +@anchor{topics/expressions gcc_jit_rvalue_dereference}@anchor{bd} @deffn {C Function} gcc_jit_lvalue * gcc_jit_rvalue_dereference (gcc_jit_rvalue@w{ }*rvalue, gcc_jit_location@w{ }*loc) Given an rvalue of pointer type @code{T *}, dereferencing the pointer, @@ -7189,7 +7204,7 @@ in C. Field access is provided separately for both lvalues and rvalues. @geindex gcc_jit_lvalue_access_field (C function) -@anchor{topics/expressions gcc_jit_lvalue_access_field}@anchor{bd} +@anchor{topics/expressions gcc_jit_lvalue_access_field}@anchor{be} @deffn {C Function} gcc_jit_lvalue * gcc_jit_lvalue_access_field (gcc_jit_lvalue@w{ }*struct_, gcc_jit_location@w{ }*loc, gcc_jit_field@w{ }*field) Given an lvalue of struct or union type, access the given field, @@ -7205,7 +7220,7 @@ in C. @end deffn @geindex gcc_jit_rvalue_access_field (C function) -@anchor{topics/expressions gcc_jit_rvalue_access_field}@anchor{be} +@anchor{topics/expressions gcc_jit_rvalue_access_field}@anchor{bf} @deffn {C Function} gcc_jit_rvalue * gcc_jit_rvalue_access_field (gcc_jit_rvalue@w{ }*struct_, gcc_jit_location@w{ }*loc, gcc_jit_field@w{ }*field) Given an rvalue of struct or union type, access the given field @@ -7221,7 +7236,7 @@ in C. @end deffn @geindex gcc_jit_rvalue_dereference_field (C function) -@anchor{topics/expressions gcc_jit_rvalue_dereference_field}@anchor{bf} +@anchor{topics/expressions gcc_jit_rvalue_dereference_field}@anchor{c0} @deffn {C Function} gcc_jit_lvalue * gcc_jit_rvalue_dereference_field (gcc_jit_rvalue@w{ }*ptr, gcc_jit_location@w{ }*loc, gcc_jit_field@w{ }*field) Given an rvalue of pointer type @code{T *} where T is of struct or union @@ -7272,7 +7287,7 @@ in C (or, indeed, to @code{PTR + INDEX}). @c . @node Creating and using functions,Source Locations,Expressions,Topic Reference -@anchor{topics/functions doc}@anchor{c0}@anchor{topics/functions creating-and-using-functions}@anchor{c1} +@anchor{topics/functions doc}@anchor{c1}@anchor{topics/functions creating-and-using-functions}@anchor{c2} @section Creating and using functions @@ -7285,7 +7300,7 @@ in C (or, indeed, to @code{PTR + INDEX}). @end menu @node Params,Functions,,Creating and using functions -@anchor{topics/functions params}@anchor{c2} +@anchor{topics/functions params}@anchor{c3} @subsection Params @@ -7312,28 +7327,28 @@ Parameters are lvalues, and thus are also rvalues (and objects), so the following upcasts are available: @geindex gcc_jit_param_as_lvalue (C function) -@anchor{topics/functions gcc_jit_param_as_lvalue}@anchor{c3} +@anchor{topics/functions gcc_jit_param_as_lvalue}@anchor{c4} @deffn {C Function} gcc_jit_lvalue * gcc_jit_param_as_lvalue (gcc_jit_param@w{ }*param) Upcasting from param to lvalue. @end deffn @geindex gcc_jit_param_as_rvalue (C function) -@anchor{topics/functions gcc_jit_param_as_rvalue}@anchor{c4} +@anchor{topics/functions gcc_jit_param_as_rvalue}@anchor{c5} @deffn {C Function} gcc_jit_rvalue * gcc_jit_param_as_rvalue (gcc_jit_param@w{ }*param) Upcasting from param to rvalue. @end deffn @geindex gcc_jit_param_as_object (C function) -@anchor{topics/functions gcc_jit_param_as_object}@anchor{c5} +@anchor{topics/functions gcc_jit_param_as_object}@anchor{c6} @deffn {C Function} gcc_jit_object * gcc_jit_param_as_object (gcc_jit_param@w{ }*param) Upcasting from param to object. @end deffn @node Functions,Blocks,Params,Creating and using functions -@anchor{topics/functions functions}@anchor{c6} +@anchor{topics/functions functions}@anchor{c7} @subsection Functions @@ -7352,7 +7367,7 @@ creating ourselves, or one that we're referencing. Create a gcc_jit_function with the given name and parameters. @geindex gcc_jit_function_kind (C type) -@anchor{topics/functions gcc_jit_function_kind}@anchor{c7} +@anchor{topics/functions gcc_jit_function_kind}@anchor{c8} @deffn {C Type} enum gcc_jit_function_kind @end deffn @@ -7362,7 +7377,7 @@ values: @quotation @geindex GCC_JIT_FUNCTION_EXPORTED (C macro) -@anchor{topics/functions GCC_JIT_FUNCTION_EXPORTED}@anchor{c8} +@anchor{topics/functions GCC_JIT_FUNCTION_EXPORTED}@anchor{c9} @deffn {C Macro} GCC_JIT_FUNCTION_EXPORTED Function is defined by the client code and visible @@ -7374,7 +7389,7 @@ for this function from a @pxref{16,,gcc_jit_result} via @end deffn @geindex GCC_JIT_FUNCTION_INTERNAL (C macro) -@anchor{topics/functions GCC_JIT_FUNCTION_INTERNAL}@anchor{c9} +@anchor{topics/functions GCC_JIT_FUNCTION_INTERNAL}@anchor{ca} @deffn {C Macro} GCC_JIT_FUNCTION_INTERNAL Function is defined by the client code, but is invisible @@ -7382,7 +7397,7 @@ outside of the JIT. Analogous to a "static" function. @end deffn @geindex GCC_JIT_FUNCTION_IMPORTED (C macro) -@anchor{topics/functions GCC_JIT_FUNCTION_IMPORTED}@anchor{ca} +@anchor{topics/functions GCC_JIT_FUNCTION_IMPORTED}@anchor{cb} @deffn {C Macro} GCC_JIT_FUNCTION_IMPORTED Function is not defined by the client code; we're merely @@ -7391,7 +7406,7 @@ header file. @end deffn @geindex GCC_JIT_FUNCTION_ALWAYS_INLINE (C macro) -@anchor{topics/functions GCC_JIT_FUNCTION_ALWAYS_INLINE}@anchor{cb} +@anchor{topics/functions GCC_JIT_FUNCTION_ALWAYS_INLINE}@anchor{cc} @deffn {C Macro} GCC_JIT_FUNCTION_ALWAYS_INLINE Function is only ever inlined into other functions, and is @@ -7412,19 +7427,19 @@ buffer. @end deffn @geindex gcc_jit_context_get_builtin_function (C function) -@anchor{topics/functions gcc_jit_context_get_builtin_function}@anchor{cc} +@anchor{topics/functions gcc_jit_context_get_builtin_function}@anchor{cd} @deffn {C Function} gcc_jit_function *gcc_jit_context_get_builtin_function (gcc_jit_context@w{ }*ctxt, const char@w{ }*name) @end deffn @geindex gcc_jit_function_as_object (C function) -@anchor{topics/functions gcc_jit_function_as_object}@anchor{cd} +@anchor{topics/functions gcc_jit_function_as_object}@anchor{ce} @deffn {C Function} gcc_jit_object * gcc_jit_function_as_object (gcc_jit_function@w{ }*func) Upcasting from function to object. @end deffn @geindex gcc_jit_function_get_param (C function) -@anchor{topics/functions gcc_jit_function_get_param}@anchor{ce} +@anchor{topics/functions gcc_jit_function_get_param}@anchor{cf} @deffn {C Function} gcc_jit_param * gcc_jit_function_get_param (gcc_jit_function@w{ }*func, int@w{ }index) Get the param of the given index (0-based). @@ -7450,7 +7465,7 @@ buffer. @end deffn @node Blocks,Statements,Functions,Creating and using functions -@anchor{topics/functions blocks}@anchor{cf} +@anchor{topics/functions blocks}@anchor{d0} @subsection Blocks @@ -7474,7 +7489,7 @@ one function. @end deffn @geindex gcc_jit_function_new_block (C function) -@anchor{topics/functions gcc_jit_function_new_block}@anchor{d0} +@anchor{topics/functions gcc_jit_function_new_block}@anchor{d1} @deffn {C Function} gcc_jit_block * gcc_jit_function_new_block (gcc_jit_function@w{ }*func, const char@w{ }*name) Create a basic block of the given name. The name may be NULL, but @@ -7496,21 +7511,21 @@ for (pc = 0; pc < fn->fn_num_ops; pc++) @end deffn @geindex gcc_jit_block_as_object (C function) -@anchor{topics/functions gcc_jit_block_as_object}@anchor{d1} +@anchor{topics/functions gcc_jit_block_as_object}@anchor{d2} @deffn {C Function} gcc_jit_object * gcc_jit_block_as_object (gcc_jit_block@w{ }*block) Upcast from block to object. @end deffn @geindex gcc_jit_block_get_function (C function) -@anchor{topics/functions gcc_jit_block_get_function}@anchor{d2} +@anchor{topics/functions gcc_jit_block_get_function}@anchor{d3} @deffn {C Function} gcc_jit_function * gcc_jit_block_get_function (gcc_jit_block@w{ }*block) Which function is this block within? @end deffn @node Statements,,Blocks,Creating and using functions -@anchor{topics/functions statements}@anchor{d3} +@anchor{topics/functions statements}@anchor{d4} @subsection Statements @@ -7624,7 +7639,7 @@ block, boolval, on_true, and on_false must be non-NULL. @end deffn @geindex gcc_jit_block_end_with_jump (C function) -@anchor{topics/functions gcc_jit_block_end_with_jump}@anchor{d4} +@anchor{topics/functions gcc_jit_block_end_with_jump}@anchor{d5} @deffn {C Function} void gcc_jit_block_end_with_jump (gcc_jit_block@w{ }*block, gcc_jit_location@w{ }*loc, gcc_jit_block@w{ }*target) Terminate a block by adding a jump to the given target block. @@ -7639,7 +7654,7 @@ goto target; @end deffn @geindex gcc_jit_block_end_with_return (C function) -@anchor{topics/functions gcc_jit_block_end_with_return}@anchor{d5} +@anchor{topics/functions gcc_jit_block_end_with_return}@anchor{d6} @deffn {C Function} void gcc_jit_block_end_with_return (gcc_jit_block@w{ }*block, gcc_jit_location@w{ }*loc, gcc_jit_rvalue@w{ }*rvalue) Terminate a block by adding evaluation of an rvalue, returning the value. @@ -7654,7 +7669,7 @@ return expression; @end deffn @geindex gcc_jit_block_end_with_void_return (C function) -@anchor{topics/functions gcc_jit_block_end_with_void_return}@anchor{d6} +@anchor{topics/functions gcc_jit_block_end_with_void_return}@anchor{d7} @deffn {C Function} void gcc_jit_block_end_with_void_return (gcc_jit_block@w{ }*block, gcc_jit_location@w{ }*loc) Terminate a block by adding a valueless return, for use within a function @@ -7670,7 +7685,7 @@ return; @end deffn @geindex gcc_jit_block_end_with_switch (C function) -@anchor{topics/functions gcc_jit_block_end_with_switch}@anchor{d7} +@anchor{topics/functions gcc_jit_block_end_with_switch}@anchor{d8} @deffn {C Function} void gcc_jit_block_end_with_switch (gcc_jit_block@w{ }*block, gcc_jit_location@w{ }*loc, gcc_jit_rvalue@w{ }*expr, gcc_jit_block@w{ }*default_block, int@w{ }num_cases, gcc_jit_case@w{ }**cases) Terminate a block by adding evalation of an rvalue, then performing @@ -7718,17 +7733,17 @@ The API entrypoints relating to switch statements and cases: @itemize * @item -@pxref{d7,,gcc_jit_block_end_with_switch()} +@pxref{d8,,gcc_jit_block_end_with_switch()} @item -@pxref{d8,,gcc_jit_case_as_object()} +@pxref{d9,,gcc_jit_case_as_object()} @item -@pxref{d9,,gcc_jit_context_new_case()} +@pxref{da,,gcc_jit_context_new_case()} @end itemize @end quotation -were added in @pxref{da,,LIBGCCJIT_ABI_3}; you can test for their presence +were added in @pxref{db,,LIBGCCJIT_ABI_3}; you can test for their presence using @example @@ -7738,20 +7753,20 @@ using @noindent @geindex gcc_jit_case (C type) -@anchor{topics/functions gcc_jit_case}@anchor{db} +@anchor{topics/functions gcc_jit_case}@anchor{dc} @deffn {C Type} gcc_jit_case @end deffn A @cite{gcc_jit_case} represents a case within a switch statement, and is created within a particular @pxref{8,,gcc_jit_context} using -@pxref{d9,,gcc_jit_context_new_case()}. +@pxref{da,,gcc_jit_context_new_case()}. Each case expresses a multivalued range of integer values. You can express single-valued cases by passing in the same value for both @cite{min_value} and @cite{max_value}. @geindex gcc_jit_context_new_case (C function) -@anchor{topics/functions gcc_jit_context_new_case}@anchor{d9} +@anchor{topics/functions gcc_jit_context_new_case}@anchor{da} @deffn {C Function} gcc_jit_case * gcc_jit_context_new_case (gcc_jit_context@w{ }*ctxt, gcc_jit_rvalue@w{ }*min_value, gcc_jit_rvalue@w{ }*max_value, gcc_jit_block@w{ }*dest_block) Create a new gcc_jit_case instance for use in a switch statement. @@ -7763,7 +7778,7 @@ statement. @end deffn @geindex gcc_jit_case_as_object (C function) -@anchor{topics/functions gcc_jit_case_as_object}@anchor{d8} +@anchor{topics/functions gcc_jit_case_as_object}@anchor{d9} @deffn {C Function} gcc_jit_object * gcc_jit_case_as_object (gcc_jit_case@w{ }*case_) Upcast from a case to an object. @@ -7898,7 +7913,7 @@ create_code (gcc_jit_context *ctxt, void *user_data) @c . @node Source Locations,Compiling a context,Creating and using functions,Topic Reference -@anchor{topics/locations source-locations}@anchor{dc}@anchor{topics/locations doc}@anchor{dd} +@anchor{topics/locations source-locations}@anchor{dd}@anchor{topics/locations doc}@anchor{de} @section Source Locations @@ -7948,7 +7963,7 @@ on-stack buffer. @end menu @node Faking it,,,Source Locations -@anchor{topics/locations faking-it}@anchor{de} +@anchor{topics/locations faking-it}@anchor{df} @subsection Faking it @@ -7986,7 +8001,7 @@ file, giving you @emph{something} you can step through in the debugger. @c . @node Compiling a context,ABI and API compatibility,Source Locations,Topic Reference -@anchor{topics/compilation compiling-a-context}@anchor{df}@anchor{topics/compilation doc}@anchor{e0} +@anchor{topics/compilation compiling-a-context}@anchor{e0}@anchor{topics/compilation doc}@anchor{e1} @section Compiling a context @@ -8005,7 +8020,7 @@ prevent any future compilation of that context. @end menu @node In-memory compilation,Ahead-of-time compilation,,Compiling a context -@anchor{topics/compilation in-memory-compilation}@anchor{e1} +@anchor{topics/compilation in-memory-compilation}@anchor{e2} @subsection In-memory compilation @@ -8040,7 +8055,7 @@ Functions are looked up by name. For this to succeed, a function with a name matching @cite{funcname} must have been created on @cite{result}'s context (or a parent context) via a call to @pxref{11,,gcc_jit_context_new_function()} with @cite{kind} -@pxref{c8,,GCC_JIT_FUNCTION_EXPORTED}: +@pxref{c9,,GCC_JIT_FUNCTION_EXPORTED}: @example gcc_jit_context_new_function (ctxt, @@ -8070,7 +8085,7 @@ to a segmentation fault. @end deffn @geindex gcc_jit_result_get_global (C function) -@anchor{topics/compilation gcc_jit_result_get_global}@anchor{b8} +@anchor{topics/compilation gcc_jit_result_get_global}@anchor{b9} @deffn {C Function} void * gcc_jit_result_get_global (gcc_jit_result@w{ }*result, const char@w{ }*name) Locate a given global within the built machine code. @@ -8078,8 +8093,8 @@ Locate a given global within the built machine code. Globals are looked up by name. For this to succeed, a global with a name matching @cite{name} must have been created on @cite{result}'s context (or a parent context) via a call to -@pxref{b5,,gcc_jit_context_new_global()} with @cite{kind} -@pxref{b7,,GCC_JIT_GLOBAL_EXPORTED}. +@pxref{b6,,gcc_jit_context_new_global()} with @cite{kind} +@pxref{b8,,GCC_JIT_GLOBAL_EXPORTED}. If the global is found, the result will need to be cast to a pointer of the correct type before it can be called. @@ -8127,11 +8142,11 @@ Once we're done with the code, this unloads the built .so file. This cleans up the result; after calling this, it's no longer valid to use the result, or any code or globals that were obtained by calling @pxref{17,,gcc_jit_result_get_code()} or -@pxref{b8,,gcc_jit_result_get_global()} on it. +@pxref{b9,,gcc_jit_result_get_global()} on it. @end deffn @node Ahead-of-time compilation,,In-memory compilation,Compiling a context -@anchor{topics/compilation ahead-of-time-compilation}@anchor{e2} +@anchor{topics/compilation ahead-of-time-compilation}@anchor{e3} @subsection Ahead-of-time compilation @@ -8160,7 +8175,7 @@ suffix of the output file when determining what to do. @end cartouche @geindex gcc_jit_output_kind (C type) -@anchor{topics/compilation gcc_jit_output_kind}@anchor{e3} +@anchor{topics/compilation gcc_jit_output_kind}@anchor{e4} @deffn {C Type} enum gcc_jit_output_kind @end deffn @@ -8178,7 +8193,7 @@ Typical suffix @item -@pxref{e4,,GCC_JIT_OUTPUT_KIND_ASSEMBLER} +@pxref{e5,,GCC_JIT_OUTPUT_KIND_ASSEMBLER} @tab @@ -8186,7 +8201,7 @@ Typical suffix @item -@pxref{e5,,GCC_JIT_OUTPUT_KIND_OBJECT_FILE} +@pxref{e6,,GCC_JIT_OUTPUT_KIND_OBJECT_FILE} @tab @@ -8194,7 +8209,7 @@ Typical suffix @item -@pxref{e6,,GCC_JIT_OUTPUT_KIND_DYNAMIC_LIBRARY} +@pxref{e7,,GCC_JIT_OUTPUT_KIND_DYNAMIC_LIBRARY} @tab @@ -8202,7 +8217,7 @@ Typical suffix @item -@pxref{e7,,GCC_JIT_OUTPUT_KIND_EXECUTABLE} +@pxref{e8,,GCC_JIT_OUTPUT_KIND_EXECUTABLE} @tab @@ -8212,21 +8227,21 @@ None, or .exe @geindex GCC_JIT_OUTPUT_KIND_ASSEMBLER (C macro) -@anchor{topics/compilation GCC_JIT_OUTPUT_KIND_ASSEMBLER}@anchor{e4} +@anchor{topics/compilation GCC_JIT_OUTPUT_KIND_ASSEMBLER}@anchor{e5} @deffn {C Macro} GCC_JIT_OUTPUT_KIND_ASSEMBLER Compile the context to an assembler file. @end deffn @geindex GCC_JIT_OUTPUT_KIND_OBJECT_FILE (C macro) -@anchor{topics/compilation GCC_JIT_OUTPUT_KIND_OBJECT_FILE}@anchor{e5} +@anchor{topics/compilation GCC_JIT_OUTPUT_KIND_OBJECT_FILE}@anchor{e6} @deffn {C Macro} GCC_JIT_OUTPUT_KIND_OBJECT_FILE Compile the context to an object file. @end deffn @geindex GCC_JIT_OUTPUT_KIND_DYNAMIC_LIBRARY (C macro) -@anchor{topics/compilation GCC_JIT_OUTPUT_KIND_DYNAMIC_LIBRARY}@anchor{e6} +@anchor{topics/compilation GCC_JIT_OUTPUT_KIND_DYNAMIC_LIBRARY}@anchor{e7} @deffn {C Macro} GCC_JIT_OUTPUT_KIND_DYNAMIC_LIBRARY Compile the context to a dynamic library. @@ -8236,7 +8251,7 @@ against. @end deffn @geindex GCC_JIT_OUTPUT_KIND_EXECUTABLE (C macro) -@anchor{topics/compilation GCC_JIT_OUTPUT_KIND_EXECUTABLE}@anchor{e7} +@anchor{topics/compilation GCC_JIT_OUTPUT_KIND_EXECUTABLE}@anchor{e8} @deffn {C Macro} GCC_JIT_OUTPUT_KIND_EXECUTABLE Compile the context to an executable. @@ -8263,7 +8278,7 @@ against. @c . @node ABI and API compatibility,Performance,Compiling a context,Topic Reference -@anchor{topics/compatibility abi-and-api-compatibility}@anchor{e8}@anchor{topics/compatibility doc}@anchor{e9} +@anchor{topics/compatibility abi-and-api-compatibility}@anchor{e9}@anchor{topics/compatibility doc}@anchor{ea} @section ABI and API compatibility @@ -8332,7 +8347,7 @@ ABI symbol tags @node ABI symbol tags,,,ABI and API compatibility -@anchor{topics/compatibility abi-symbol-tags}@anchor{ea} +@anchor{topics/compatibility abi-symbol-tags}@anchor{eb} @subsection ABI symbol tags @@ -8351,7 +8366,7 @@ Newer releases use the following tags. @end menu @node LIBGCCJIT_ABI_0,LIBGCCJIT_ABI_1,,ABI symbol tags -@anchor{topics/compatibility libgccjit-abi-0}@anchor{eb}@anchor{topics/compatibility id1}@anchor{ec} +@anchor{topics/compatibility libgccjit-abi-0}@anchor{ec}@anchor{topics/compatibility id1}@anchor{ed} @subsubsection @code{LIBGCCJIT_ABI_0} @@ -8363,7 +8378,7 @@ continue to work, with this being handled transparently by the linker (see this post@footnote{https://gcc.gnu.org/ml/gcc-patches/2015-06/msg02126.html}) @node LIBGCCJIT_ABI_1,LIBGCCJIT_ABI_2,LIBGCCJIT_ABI_0,ABI symbol tags -@anchor{topics/compatibility libgccjit-abi-1}@anchor{73}@anchor{topics/compatibility id2}@anchor{ed} +@anchor{topics/compatibility libgccjit-abi-1}@anchor{73}@anchor{topics/compatibility id2}@anchor{ee} @subsubsection @code{LIBGCCJIT_ABI_1} @@ -8371,7 +8386,7 @@ continue to work, with this being handled transparently by the linker @pxref{72,,gcc_jit_context_add_command_line_option()} @node LIBGCCJIT_ABI_2,LIBGCCJIT_ABI_3,LIBGCCJIT_ABI_1,ABI symbol tags -@anchor{topics/compatibility libgccjit-abi-2}@anchor{6c}@anchor{topics/compatibility id3}@anchor{ee} +@anchor{topics/compatibility libgccjit-abi-2}@anchor{6c}@anchor{topics/compatibility id3}@anchor{ef} @subsubsection @code{LIBGCCJIT_ABI_2} @@ -8379,7 +8394,7 @@ continue to work, with this being handled transparently by the linker @pxref{6b,,gcc_jit_context_set_bool_allow_unreachable_blocks()} @node LIBGCCJIT_ABI_3,LIBGCCJIT_ABI_4,LIBGCCJIT_ABI_2,ABI symbol tags -@anchor{topics/compatibility libgccjit-abi-3}@anchor{da}@anchor{topics/compatibility id4}@anchor{ef} +@anchor{topics/compatibility libgccjit-abi-3}@anchor{db}@anchor{topics/compatibility id4}@anchor{f0} @subsubsection @code{LIBGCCJIT_ABI_3} @@ -8392,18 +8407,18 @@ entrypoints: @itemize * @item -@pxref{d7,,gcc_jit_block_end_with_switch()} +@pxref{d8,,gcc_jit_block_end_with_switch()} @item -@pxref{d8,,gcc_jit_case_as_object()} +@pxref{d9,,gcc_jit_case_as_object()} @item -@pxref{d9,,gcc_jit_context_new_case()} +@pxref{da,,gcc_jit_context_new_case()} @end itemize @end quotation @node LIBGCCJIT_ABI_4,LIBGCCJIT_ABI_5,LIBGCCJIT_ABI_3,ABI symbol tags -@anchor{topics/compatibility id5}@anchor{f0}@anchor{topics/compatibility libgccjit-abi-4}@anchor{f1} +@anchor{topics/compatibility id5}@anchor{f1}@anchor{topics/compatibility libgccjit-abi-4}@anchor{f2} @subsubsection @code{LIBGCCJIT_ABI_4} @@ -8416,30 +8431,30 @@ entrypoints: @itemize * @item -@pxref{f2,,gcc_jit_context_get_timer()} +@pxref{f3,,gcc_jit_context_get_timer()} @item -@pxref{f3,,gcc_jit_context_set_timer()} +@pxref{f4,,gcc_jit_context_set_timer()} @item -@pxref{f4,,gcc_jit_timer_new()} +@pxref{f5,,gcc_jit_timer_new()} @item -@pxref{f5,,gcc_jit_timer_release()} +@pxref{f6,,gcc_jit_timer_release()} @item -@pxref{f6,,gcc_jit_timer_push()} +@pxref{f7,,gcc_jit_timer_push()} @item -@pxref{f7,,gcc_jit_timer_pop()} +@pxref{f8,,gcc_jit_timer_pop()} @item -@pxref{f8,,gcc_jit_timer_print()} +@pxref{f9,,gcc_jit_timer_print()} @end itemize @end quotation @node LIBGCCJIT_ABI_5,,LIBGCCJIT_ABI_4,ABI symbol tags -@anchor{topics/compatibility id6}@anchor{f9}@anchor{topics/compatibility libgccjit-abi-5}@anchor{6e} +@anchor{topics/compatibility id6}@anchor{fa}@anchor{topics/compatibility libgccjit-abi-5}@anchor{6e} @subsubsection @code{LIBGCCJIT_ABI_5} @@ -8464,7 +8479,7 @@ entrypoints: @c . @node Performance,,ABI and API compatibility,Topic Reference -@anchor{topics/performance performance}@anchor{fa}@anchor{topics/performance doc}@anchor{fb} +@anchor{topics/performance performance}@anchor{fb}@anchor{topics/performance doc}@anchor{fc} @section Performance @@ -8474,14 +8489,14 @@ entrypoints: @end menu @node The timing API,,,Performance -@anchor{topics/performance the-timing-api}@anchor{fc} +@anchor{topics/performance the-timing-api}@anchor{fd} @subsection The timing API As of GCC 6, libgccjit exposes a timing API, for printing reports on how long was spent in different parts of code. -You can create a @pxref{fd,,gcc_jit_timer} instance, which will +You can create a @pxref{fe,,gcc_jit_timer} instance, which will measure time spent since its creation. The timer maintains a stack of "timer items": as control flow moves through your code, you can push and pop named items relating to your code onto the stack, and the timer @@ -8583,7 +8598,7 @@ Client items: The exact format is intended to be human-readable, and is subject to change. @geindex LIBGCCJIT_HAVE_TIMING_API (C macro) -@anchor{topics/performance LIBGCCJIT_HAVE_TIMING_API}@anchor{fe} +@anchor{topics/performance LIBGCCJIT_HAVE_TIMING_API}@anchor{ff} @deffn {C Macro} LIBGCCJIT_HAVE_TIMING_API The timer API was added to libgccjit in GCC 6. @@ -8602,15 +8617,15 @@ gcc_jit_context_set_timer (ctxt, t); @end deffn @geindex gcc_jit_timer (C type) -@anchor{topics/performance gcc_jit_timer}@anchor{fd} +@anchor{topics/performance gcc_jit_timer}@anchor{fe} @deffn {C Type} gcc_jit_timer @end deffn @geindex gcc_jit_timer_new (C function) -@anchor{topics/performance gcc_jit_timer_new}@anchor{f4} +@anchor{topics/performance gcc_jit_timer_new}@anchor{f5} @deffn {C Function} gcc_jit_timer * gcc_jit_timer_new (void) -Create a @pxref{fd,,gcc_jit_timer} instance, and start timing: +Create a @pxref{fe,,gcc_jit_timer} instance, and start timing: @example gcc_jit_timer *t = gcc_jit_timer_new (); @@ -8618,7 +8633,7 @@ gcc_jit_timer *t = gcc_jit_timer_new (); @noindent -This API entrypoint was added in @pxref{f1,,LIBGCCJIT_ABI_4}; you can test +This API entrypoint was added in @pxref{f2,,LIBGCCJIT_ABI_4}; you can test for its presence using @example @@ -8629,10 +8644,10 @@ for its presence using @end deffn @geindex gcc_jit_timer_release (C function) -@anchor{topics/performance gcc_jit_timer_release}@anchor{f5} +@anchor{topics/performance gcc_jit_timer_release}@anchor{f6} @deffn {C Function} void gcc_jit_timer_release (gcc_jit_timer@w{ }*timer) -Release a @pxref{fd,,gcc_jit_timer} instance: +Release a @pxref{fe,,gcc_jit_timer} instance: @example gcc_jit_timer_release (t); @@ -8642,7 +8657,7 @@ gcc_jit_timer_release (t); This should be called exactly once on a timer. -This API entrypoint was added in @pxref{f1,,LIBGCCJIT_ABI_4}; you can test +This API entrypoint was added in @pxref{f2,,LIBGCCJIT_ABI_4}; you can test for its presence using @example @@ -8653,10 +8668,10 @@ for its presence using @end deffn @geindex gcc_jit_context_set_timer (C function) -@anchor{topics/performance gcc_jit_context_set_timer}@anchor{f3} +@anchor{topics/performance gcc_jit_context_set_timer}@anchor{f4} @deffn {C Function} void gcc_jit_context_set_timer (gcc_jit_context@w{ }*ctxt, gcc_jit_timer@w{ }*timer) -Associate a @pxref{fd,,gcc_jit_timer} instance with a context: +Associate a @pxref{fe,,gcc_jit_timer} instance with a context: @example gcc_jit_context_set_timer (ctxt, t); @@ -8671,7 +8686,7 @@ Timers have no locking, so if you have a multithreaded program, you must provide your own locks if more than one thread could be working with the same timer via timer-associated contexts. -This API entrypoint was added in @pxref{f1,,LIBGCCJIT_ABI_4}; you can test +This API entrypoint was added in @pxref{f2,,LIBGCCJIT_ABI_4}; you can test for its presence using @example @@ -8682,12 +8697,12 @@ for its presence using @end deffn @geindex gcc_jit_context_get_timer (C function) -@anchor{topics/performance gcc_jit_context_get_timer}@anchor{f2} +@anchor{topics/performance gcc_jit_context_get_timer}@anchor{f3} @deffn {C Function} gcc_jit_timer *gcc_jit_context_get_timer (gcc_jit_context@w{ }*ctxt) Get the timer associated with a context (if any). -This API entrypoint was added in @pxref{f1,,LIBGCCJIT_ABI_4}; you can test +This API entrypoint was added in @pxref{f2,,LIBGCCJIT_ABI_4}; you can test for its presence using @example @@ -8698,7 +8713,7 @@ for its presence using @end deffn @geindex gcc_jit_timer_push (C function) -@anchor{topics/performance gcc_jit_timer_push}@anchor{f6} +@anchor{topics/performance gcc_jit_timer_push}@anchor{f7} @deffn {C Function} void gcc_jit_timer_push (gcc_jit_timer@w{ }*timer, const char@w{ }*item_name) Push the given item onto the timer's stack: @@ -8711,7 +8726,7 @@ gcc_jit_timer_pop (t, "running code"); @noindent -This API entrypoint was added in @pxref{f1,,LIBGCCJIT_ABI_4}; you can test +This API entrypoint was added in @pxref{f2,,LIBGCCJIT_ABI_4}; you can test for its presence using @example @@ -8722,7 +8737,7 @@ for its presence using @end deffn @geindex gcc_jit_timer_pop (C function) -@anchor{topics/performance gcc_jit_timer_pop}@anchor{f7} +@anchor{topics/performance gcc_jit_timer_pop}@anchor{f8} @deffn {C Function} void gcc_jit_timer_pop (gcc_jit_timer@w{ }*timer, const char@w{ }*item_name) Pop the top item from the timer's stack. @@ -8730,7 +8745,7 @@ Pop the top item from the timer's stack. If "item_name" is provided, it must match that of the top item. Alternatively, @code{NULL} can be passed in, to suppress checking. -This API entrypoint was added in @pxref{f1,,LIBGCCJIT_ABI_4}; you can test +This API entrypoint was added in @pxref{f2,,LIBGCCJIT_ABI_4}; you can test for its presence using @example @@ -8741,13 +8756,13 @@ for its presence using @end deffn @geindex gcc_jit_timer_print (C function) -@anchor{topics/performance gcc_jit_timer_print}@anchor{f8} +@anchor{topics/performance gcc_jit_timer_print}@anchor{f9} @deffn {C Function} void gcc_jit_timer_print (gcc_jit_timer@w{ }*timer, FILE@w{ }*f_out) Print timing information to the given stream about activity since the timer was started. -This API entrypoint was added in @pxref{f1,,LIBGCCJIT_ABI_4}; you can test +This API entrypoint was added in @pxref{f2,,LIBGCCJIT_ABI_4}; you can test for its presence using @example @@ -8775,7 +8790,7 @@ for its presence using @c . @node C++ bindings for libgccjit,Internals,Topic Reference,Top -@anchor{cp/index c-bindings-for-libgccjit}@anchor{ff}@anchor{cp/index doc}@anchor{100} +@anchor{cp/index c-bindings-for-libgccjit}@anchor{100}@anchor{cp/index doc}@anchor{101} @chapter C++ bindings for libgccjit @@ -8923,7 +8938,7 @@ Compiling a context @node Tutorial<2>,Topic Reference<2>,,C++ bindings for libgccjit -@anchor{cp/intro/index doc}@anchor{101}@anchor{cp/intro/index tutorial}@anchor{102} +@anchor{cp/intro/index doc}@anchor{102}@anchor{cp/intro/index tutorial}@anchor{103} @section Tutorial @@ -8953,7 +8968,7 @@ Compiling a context @end menu @node Tutorial part 1 "Hello world"<2>,Tutorial part 2 Creating a trivial machine code function<2>,,Tutorial<2> -@anchor{cp/intro/tutorial01 doc}@anchor{103}@anchor{cp/intro/tutorial01 tutorial-part-1-hello-world}@anchor{104} +@anchor{cp/intro/tutorial01 doc}@anchor{104}@anchor{cp/intro/tutorial01 tutorial-part-1-hello-world}@anchor{105} @subsection Tutorial part 1: "Hello world" @@ -9123,7 +9138,7 @@ hello world @c . @node Tutorial part 2 Creating a trivial machine code function<2>,Tutorial part 3 Loops and variables<2>,Tutorial part 1 "Hello world"<2>,Tutorial<2> -@anchor{cp/intro/tutorial02 doc}@anchor{105}@anchor{cp/intro/tutorial02 tutorial-part-2-creating-a-trivial-machine-code-function}@anchor{106} +@anchor{cp/intro/tutorial02 doc}@anchor{106}@anchor{cp/intro/tutorial02 tutorial-part-2-creating-a-trivial-machine-code-function}@anchor{107} @subsection Tutorial part 2: Creating a trivial machine code function @@ -9152,7 +9167,7 @@ All state associated with compilation is associated with a @code{gccjit::context}, which is a thin C++ wrapper around the C API's @pxref{8,,gcc_jit_context *}. -Create one using @pxref{107,,gccjit;;context;;acquire()}: +Create one using @pxref{108,,gccjit;;context;;acquire()}: @example gccjit::context ctxt; @@ -9165,7 +9180,7 @@ The JIT library has a system of types. It is statically-typed: every expression is of a specific type, fixed at compile-time. In our example, all of the expressions are of the C @cite{int} type, so let's obtain this from the context, as a @code{gccjit::type}, using -@pxref{108,,gccjit;;context;;get_type()}: +@pxref{109,,gccjit;;context;;get_type()}: @example gccjit::type int_type = ctxt.get_type (GCC_JIT_TYPE_INT); @@ -9178,7 +9193,7 @@ entity in the API is associated with a @code{gccjit::context}. Memory management is easy: all such "contextual" objects are automatically cleaned up for you when the context is released, using -@pxref{109,,gccjit;;context;;release()}: +@pxref{10a,,gccjit;;context;;release()}: @example ctxt.release (); @@ -9211,7 +9226,7 @@ The C++ class hierarchy within the @code{gccjit} namespace looks like this: One thing you can do with a @code{gccjit::object} is to ask it for a human-readable description as a @code{std::string}, using -@pxref{10a,,gccjit;;object;;get_debug_string()}: +@pxref{10b,,gccjit;;object;;get_debug_string()}: @example printf ("obj: %s\n", obj.get_debug_string ().c_str ()); @@ -9231,7 +9246,7 @@ This is invaluable when debugging. Let's create the function. To do so, we first need to construct its single parameter, specifying its type and giving it a name, -using @pxref{10b,,gccjit;;context;;new_param()}: +using @pxref{10c,,gccjit;;context;;new_param()}: @example gccjit::param param_i = ctxt.new_param (int_type, "i"); @@ -9280,7 +9295,7 @@ gccjit::block block = func.new_block (); Our basic block is relatively simple: it immediately terminates by returning the value of an expression. -We can build the expression using @pxref{10c,,gccjit;;context;;new_binary_op()}: +We can build the expression using @pxref{10d,,gccjit;;context;;new_binary_op()}: @example gccjit::rvalue expr = @@ -9293,7 +9308,7 @@ gccjit::rvalue expr = A @code{gccjit::rvalue} is another example of a @code{gccjit::object} subclass. As before, we can print it with -@pxref{10a,,gccjit;;object;;get_debug_string()}. +@pxref{10b,,gccjit;;object;;get_debug_string()}. @example printf ("expr: %s\n", expr.get_debug_string ().c_str ()); @@ -9330,7 +9345,7 @@ block.end_with_return (expr); @noindent OK, we've populated the context. We can now compile it using -@pxref{10d,,gccjit;;context;;compile()}: +@pxref{10e,,gccjit;;context;;compile()}: @example gcc_jit_result *result; @@ -9380,12 +9395,12 @@ result: 25 @end menu @node Options<3>,Full example<3>,,Tutorial part 2 Creating a trivial machine code function<2> -@anchor{cp/intro/tutorial02 options}@anchor{10e} +@anchor{cp/intro/tutorial02 options}@anchor{10f} @subsubsection Options To get more information on what's going on, you can set debugging flags -on the context using @pxref{10f,,gccjit;;context;;set_bool_option()}. +on the context using @pxref{110,,gccjit;;context;;set_bool_option()}. @c (I'm deliberately not mentioning @c :c:macro:`GCC_JIT_BOOL_OPTION_DUMP_INITIAL_TREE` here since I think @@ -9457,7 +9472,7 @@ square: By default, no optimizations are performed, the equivalent of GCC's @cite{-O0} option. We can turn things up to e.g. @cite{-O3} by calling -@pxref{110,,gccjit;;context;;set_int_option()} with +@pxref{111,,gccjit;;context;;set_int_option()} with @pxref{1f,,GCC_JIT_INT_OPTION_OPTIMIZATION_LEVEL}: @example @@ -9491,7 +9506,7 @@ square: Naturally this has only a small effect on such a trivial function. @node Full example<3>,,Options<3>,Tutorial part 2 Creating a trivial machine code function<2> -@anchor{cp/intro/tutorial02 full-example}@anchor{111} +@anchor{cp/intro/tutorial02 full-example}@anchor{112} @subsubsection Full example @@ -9634,7 +9649,7 @@ result: 25 @c . @node Tutorial part 3 Loops and variables<2>,Tutorial part 4 Adding JIT-compilation to a toy interpreter<2>,Tutorial part 2 Creating a trivial machine code function<2>,Tutorial<2> -@anchor{cp/intro/tutorial03 tutorial-part-3-loops-and-variables}@anchor{112}@anchor{cp/intro/tutorial03 doc}@anchor{113} +@anchor{cp/intro/tutorial03 tutorial-part-3-loops-and-variables}@anchor{113}@anchor{cp/intro/tutorial03 doc}@anchor{114} @subsection Tutorial part 3: Loops and variables @@ -9758,7 +9773,7 @@ gccjit::function func = @end menu @node Expressions lvalues and rvalues<2>,Control flow<2>,,Tutorial part 3 Loops and variables<2> -@anchor{cp/intro/tutorial03 expressions-lvalues-and-rvalues}@anchor{114} +@anchor{cp/intro/tutorial03 expressions-lvalues-and-rvalues}@anchor{115} @subsubsection Expressions: lvalues and rvalues @@ -9831,7 +9846,7 @@ body of a function. Our new example has a new kind of expression: we have two local variables. We create them by calling -@pxref{115,,gccjit;;function;;new_local()}, supplying a type and a name: +@pxref{116,,gccjit;;function;;new_local()}, supplying a type and a name: @example /* Build locals: */ @@ -9857,7 +9872,7 @@ Instead, having added the local to the function, we have to separately add an assignment of @cite{0} to @cite{local_i} at the beginning of the function. @node Control flow<2>,Visualizing the control flow graph<2>,Expressions lvalues and rvalues<2>,Tutorial part 3 Loops and variables<2> -@anchor{cp/intro/tutorial03 control-flow}@anchor{116} +@anchor{cp/intro/tutorial03 control-flow}@anchor{117} @subsubsection Control flow @@ -9896,8 +9911,8 @@ We now populate each block with statements. The entry block @cite{b_initial} consists of initializations followed by a jump to the conditional. We assign @cite{0} to @cite{i} and to @cite{sum}, using -@pxref{117,,gccjit;;block;;add_assignment()} to add -an assignment statement, and using @pxref{118,,gccjit;;context;;zero()} to get +@pxref{118,,gccjit;;block;;add_assignment()} to add +an assignment statement, and using @pxref{119,,gccjit;;context;;zero()} to get the constant value @cite{0} for the relevant type for the right-hand side of the assignment: @@ -9924,7 +9939,7 @@ C example. It contains a single statement: a conditional, which jumps to one of two destination blocks depending on a boolean @code{gccjit::rvalue}, in this case the comparison of @cite{i} and @cite{n}. -We could build the comparison using @pxref{119,,gccjit;;context;;new_comparison()}: +We could build the comparison using @pxref{11a,,gccjit;;context;;new_comparison()}: @example gccjit::rvalue guard = @@ -9935,7 +9950,7 @@ gccjit::rvalue guard = @noindent and can then use this to add @cite{b_loop_cond}'s sole statement, via -@pxref{11a,,gccjit;;block;;end_with_conditional()}: +@pxref{11b,,gccjit;;block;;end_with_conditional()}: @example b_loop_cond.end_with_conditional (guard, @@ -9969,7 +9984,7 @@ Next, we populate the body of the loop. The C statement @cite{sum += i * i;} is an assignment operation, where an lvalue is modified "in-place". We use -@pxref{11b,,gccjit;;block;;add_assignment_op()} to handle these operations: +@pxref{11c,,gccjit;;block;;add_assignment_op()} to handle these operations: @example /* sum += i * i */ @@ -9997,7 +10012,7 @@ b_loop_body.add_assignment_op (i, @cartouche @quotation Note For numeric constants other than 0 or 1, we could use -@pxref{11c,,gccjit;;context;;new_rvalue()}, which has overloads +@pxref{11d,,gccjit;;context;;new_rvalue()}, which has overloads for both @code{int} and @code{double}. @end quotation @end cartouche @@ -10073,12 +10088,12 @@ result: 285 @noindent @node Visualizing the control flow graph<2>,Full example<4>,Control flow<2>,Tutorial part 3 Loops and variables<2> -@anchor{cp/intro/tutorial03 visualizing-the-control-flow-graph}@anchor{11d} +@anchor{cp/intro/tutorial03 visualizing-the-control-flow-graph}@anchor{11e} @subsubsection Visualizing the control flow graph You can see the control flow graph of a function using -@pxref{11e,,gccjit;;function;;dump_to_dot()}: +@pxref{11f,,gccjit;;function;;dump_to_dot()}: @example func.dump_to_dot ("/tmp/sum-of-squares.dot"); @@ -10112,7 +10127,7 @@ install it with @cite{yum install python-xdot}): @end quotation @node Full example<4>,,Visualizing the control flow graph<2>,Tutorial part 3 Loops and variables<2> -@anchor{cp/intro/tutorial03 full-example}@anchor{11f} +@anchor{cp/intro/tutorial03 full-example}@anchor{120} @subsubsection Full example @@ -10295,7 +10310,7 @@ loop_test returned: 285 @c . @node Tutorial part 4 Adding JIT-compilation to a toy interpreter<2>,,Tutorial part 3 Loops and variables<2>,Tutorial<2> -@anchor{cp/intro/tutorial04 tutorial-part-4-adding-jit-compilation-to-a-toy-interpreter}@anchor{120}@anchor{cp/intro/tutorial04 doc}@anchor{121} +@anchor{cp/intro/tutorial04 tutorial-part-4-adding-jit-compilation-to-a-toy-interpreter}@anchor{121}@anchor{cp/intro/tutorial04 doc}@anchor{122} @subsection Tutorial part 4: Adding JIT-compilation to a toy interpreter @@ -10317,7 +10332,7 @@ to it. @end menu @node Our toy interpreter<2>,Compiling to machine code<2>,,Tutorial part 4 Adding JIT-compilation to a toy interpreter<2> -@anchor{cp/intro/tutorial04 our-toy-interpreter}@anchor{122} +@anchor{cp/intro/tutorial04 our-toy-interpreter}@anchor{123} @subsubsection Our toy interpreter @@ -10725,7 +10740,7 @@ toyvm_function::interpret (int arg, FILE *trace) @end quotation @node Compiling to machine code<2>,Setting things up<2>,Our toy interpreter<2>,Tutorial part 4 Adding JIT-compilation to a toy interpreter<2> -@anchor{cp/intro/tutorial04 compiling-to-machine-code}@anchor{123} +@anchor{cp/intro/tutorial04 compiling-to-machine-code}@anchor{124} @subsubsection Compiling to machine code @@ -10805,7 +10820,7 @@ This means our compiler has the following state: @end quotation @node Setting things up<2>,Populating the function<2>,Compiling to machine code<2>,Tutorial part 4 Adding JIT-compilation to a toy interpreter<2> -@anchor{cp/intro/tutorial04 setting-things-up}@anchor{124} +@anchor{cp/intro/tutorial04 setting-things-up}@anchor{125} @subsubsection Setting things up @@ -10973,7 +10988,7 @@ We create the locals within the function. @end quotation @node Populating the function<2>,Verifying the control flow graph<2>,Setting things up<2>,Tutorial part 4 Adding JIT-compilation to a toy interpreter<2> -@anchor{cp/intro/tutorial04 populating-the-function}@anchor{125} +@anchor{cp/intro/tutorial04 populating-the-function}@anchor{126} @subsubsection Populating the function @@ -11101,7 +11116,7 @@ stack into @code{y} instead erroneously assigned it to @code{x}, leaving @code{y uninitialized. To track this kind of thing down, we can use -@pxref{126,,gccjit;;block;;add_comment()} to add descriptive comments +@pxref{127,,gccjit;;block;;add_comment()} to add descriptive comments to the internal representation. This is invaluable when looking through the generated IR for, say @code{factorial}: @@ -11250,14 +11265,14 @@ to the next block. This is analogous to simply incrementing the program counter. @node Verifying the control flow graph<2>,Compiling the context<2>,Populating the function<2>,Tutorial part 4 Adding JIT-compilation to a toy interpreter<2> -@anchor{cp/intro/tutorial04 verifying-the-control-flow-graph}@anchor{127} +@anchor{cp/intro/tutorial04 verifying-the-control-flow-graph}@anchor{128} @subsubsection Verifying the control flow graph Having finished looping over the blocks, the context is complete. As before, we can verify that the control flow and statements are sane by -using @pxref{11e,,gccjit;;function;;dump_to_dot()}: +using @pxref{11f,,gccjit;;function;;dump_to_dot()}: @example fn.dump_to_dot ("/tmp/factorial.dot"); @@ -11281,7 +11296,7 @@ errors in our compiler. @end quotation @node Compiling the context<2>,Single-stepping through the generated code<2>,Verifying the control flow graph<2>,Tutorial part 4 Adding JIT-compilation to a toy interpreter<2> -@anchor{cp/intro/tutorial04 compiling-the-context}@anchor{128} +@anchor{cp/intro/tutorial04 compiling-the-context}@anchor{129} @subsubsection Compiling the context @@ -11338,7 +11353,7 @@ private: @end quotation @node Single-stepping through the generated code<2>,Examining the generated code<2>,Compiling the context<2>,Tutorial part 4 Adding JIT-compilation to a toy interpreter<2> -@anchor{cp/intro/tutorial04 single-stepping-through-the-generated-code}@anchor{129} +@anchor{cp/intro/tutorial04 single-stepping-through-the-generated-code}@anchor{12a} @subsubsection Single-stepping through the generated code @@ -11352,14 +11367,14 @@ It's possible to debug the generated code. To do this we need to both: @item Set up source code locations for our statements, so that we can meaningfully step through the code. We did this above by -calling @pxref{12a,,gccjit;;context;;new_location()} and using the +calling @pxref{12b,,gccjit;;context;;new_location()} and using the results. @item Enable the generation of debugging information, by setting @pxref{42,,GCC_JIT_BOOL_OPTION_DEBUGINFO} on the @code{gccjit::context} via -@pxref{10f,,gccjit;;context;;set_bool_option()}: +@pxref{110,,gccjit;;context;;set_bool_option()}: @example ctxt.set_bool_option (GCC_JIT_BOOL_OPTION_DEBUGINFO, 1); @@ -11431,14 +11446,14 @@ optimization level in a regular compiler. @end cartouche @node Examining the generated code<2>,Putting it all together<2>,Single-stepping through the generated code<2>,Tutorial part 4 Adding JIT-compilation to a toy interpreter<2> -@anchor{cp/intro/tutorial04 examining-the-generated-code}@anchor{12b} +@anchor{cp/intro/tutorial04 examining-the-generated-code}@anchor{12c} @subsubsection Examining the generated code How good is the optimized code? We can turn up optimizations, by calling -@pxref{110,,gccjit;;context;;set_int_option()} with +@pxref{111,,gccjit;;context;;set_int_option()} with @pxref{1f,,GCC_JIT_INT_OPTION_OPTIMIZATION_LEVEL}: @example @@ -11620,7 +11635,7 @@ Note that the stack pushing and popping have been eliminated, as has the recursive call (in favor of an iteration). @node Putting it all together<2>,Behind the curtain How does our code get optimized?<2>,Examining the generated code<2>,Tutorial part 4 Adding JIT-compilation to a toy interpreter<2> -@anchor{cp/intro/tutorial04 putting-it-all-together}@anchor{12c} +@anchor{cp/intro/tutorial04 putting-it-all-together}@anchor{12d} @subsubsection Putting it all together @@ -11653,7 +11668,7 @@ compiler result: 55 @noindent @node Behind the curtain How does our code get optimized?<2>,,Putting it all together<2>,Tutorial part 4 Adding JIT-compilation to a toy interpreter<2> -@anchor{cp/intro/tutorial04 behind-the-curtain-how-does-our-code-get-optimized}@anchor{12d} +@anchor{cp/intro/tutorial04 behind-the-curtain-how-does-our-code-get-optimized}@anchor{12e} @subsubsection Behind the curtain: How does our code get optimized? @@ -11854,7 +11869,7 @@ representation: @code{initial}, @code{instr4} and @code{instr9}. @end menu @node Optimizing away stack manipulation<2>,Elimination of tail recursion<2>,,Behind the curtain How does our code get optimized?<2> -@anchor{cp/intro/tutorial04 optimizing-away-stack-manipulation}@anchor{12e} +@anchor{cp/intro/tutorial04 optimizing-away-stack-manipulation}@anchor{12f} @subsubsection Optimizing away stack manipulation @@ -12134,7 +12149,7 @@ instr9: @noindent @node Elimination of tail recursion<2>,,Optimizing away stack manipulation<2>,Behind the curtain How does our code get optimized?<2> -@anchor{cp/intro/tutorial04 elimination-of-tail-recursion}@anchor{12f} +@anchor{cp/intro/tutorial04 elimination-of-tail-recursion}@anchor{130} @subsubsection Elimination of tail recursion @@ -12221,7 +12236,7 @@ instr9: @c . @node Topic Reference<2>,,Tutorial<2>,C++ bindings for libgccjit -@anchor{cp/topics/index doc}@anchor{130}@anchor{cp/topics/index topic-reference}@anchor{131} +@anchor{cp/topics/index doc}@anchor{131}@anchor{cp/topics/index topic-reference}@anchor{132} @section Topic Reference @@ -12311,22 +12326,22 @@ Compiling a context @node Compilation contexts<2>,Objects<2>,,Topic Reference<2> -@anchor{cp/topics/contexts compilation-contexts}@anchor{132}@anchor{cp/topics/contexts doc}@anchor{133} +@anchor{cp/topics/contexts compilation-contexts}@anchor{133}@anchor{cp/topics/contexts doc}@anchor{134} @subsection Compilation contexts @geindex gccjit;;context (C++ class) -@anchor{cp/topics/contexts gccjit context}@anchor{134} +@anchor{cp/topics/contexts gccjit context}@anchor{135} @deffn {C++ Class} gccjit::context @end deffn -The top-level of the C++ API is the @pxref{134,,gccjit;;context} type. +The top-level of the C++ API is the @pxref{135,,gccjit;;context} type. -A @pxref{134,,gccjit;;context} instance encapsulates the state of a +A @pxref{135,,gccjit;;context} instance encapsulates the state of a compilation. You can set up options on it, and add types, functions and code. -Invoking @pxref{10d,,gccjit;;context;;compile()} on it gives you a +Invoking @pxref{10e,,gccjit;;context;;compile()} on it gives you a @pxref{16,,gcc_jit_result *}. It is a thin wrapper around the C API's @pxref{8,,gcc_jit_context *}. @@ -12341,7 +12356,7 @@ It is a thin wrapper around the C API's @pxref{8,,gcc_jit_context *}. @end menu @node Lifetime-management<2>,Thread-safety<2>,,Compilation contexts<2> -@anchor{cp/topics/contexts lifetime-management}@anchor{135} +@anchor{cp/topics/contexts lifetime-management}@anchor{136} @subsubsection Lifetime-management @@ -12350,16 +12365,16 @@ have their lifetime bounded by the context they are created within, and cleanup of such objects is done for you when the context is released. @geindex gccjit;;context;;acquire (C++ function) -@anchor{cp/topics/contexts gccjit context acquire}@anchor{107} +@anchor{cp/topics/contexts gccjit context acquire}@anchor{108} @deffn {C++ Function} gccjit::context gccjit::context::acquire () -This function acquires a new @pxref{134,,gccjit;;context} instance, +This function acquires a new @pxref{135,,gccjit;;context} instance, which is independent of any others that may be present within this process. @end deffn @geindex gccjit;;context;;release (C++ function) -@anchor{cp/topics/contexts gccjit context release}@anchor{109} +@anchor{cp/topics/contexts gccjit context release}@anchor{10a} @deffn {C++ Function} void gccjit::context::release () This function releases all resources associated with the given context. @@ -12378,7 +12393,7 @@ ctxt.release (); @end deffn @geindex gccjit;;context;;new_child_context (C++ function) -@anchor{cp/topics/contexts gccjit context new_child_context}@anchor{136} +@anchor{cp/topics/contexts gccjit context new_child_context}@anchor{137} @deffn {C++ Function} gccjit::context gccjit::context::new_child_context () Given an existing JIT context, create a child context. @@ -12410,16 +12425,16 @@ there will likely be a performance hit for such nesting. @end deffn @node Thread-safety<2>,Error-handling<3>,Lifetime-management<2>,Compilation contexts<2> -@anchor{cp/topics/contexts thread-safety}@anchor{137} +@anchor{cp/topics/contexts thread-safety}@anchor{138} @subsubsection Thread-safety -Instances of @pxref{134,,gccjit;;context} created via -@pxref{107,,gccjit;;context;;acquire()} are independent from each other: +Instances of @pxref{135,,gccjit;;context} created via +@pxref{108,,gccjit;;context;;acquire()} are independent from each other: only one thread may use a given context at once, but multiple threads could each have their own contexts without needing locks. -Contexts created via @pxref{136,,gccjit;;context;;new_child_context()} are +Contexts created via @pxref{137,,gccjit;;context;;new_child_context()} are related to their parent context. They can be partitioned by their ultimate ancestor into independent "family trees". Only one thread within a process may use a given "family tree" of such contexts at once, @@ -12427,7 +12442,7 @@ and if you're using multiple threads you should provide your own locking around entire such context partitions. @node Error-handling<3>,Debugging<2>,Thread-safety<2>,Compilation contexts<2> -@anchor{cp/topics/contexts error-handling}@anchor{138} +@anchor{cp/topics/contexts error-handling}@anchor{139} @subsubsection Error-handling @@ -12440,10 +12455,10 @@ NULL. You don't have to check everywhere for NULL results, since the API gracefully handles a NULL being passed in for any argument. Errors are printed on stderr and can be queried using -@pxref{139,,gccjit;;context;;get_first_error()}. +@pxref{13a,,gccjit;;context;;get_first_error()}. @geindex gccjit;;context;;get_first_error (C++ function) -@anchor{cp/topics/contexts gccjit context get_first_error__gccjit contextP}@anchor{139} +@anchor{cp/topics/contexts gccjit context get_first_error__gccjit contextP}@anchor{13a} @deffn {C++ Function} const char* gccjit::context::get_first_error (gccjit::context* ctxt) Returns the first error message that occurred on the context. @@ -12455,18 +12470,18 @@ If no errors occurred, this will be NULL. @end deffn @node Debugging<2>,Options<4>,Error-handling<3>,Compilation contexts<2> -@anchor{cp/topics/contexts debugging}@anchor{13a} +@anchor{cp/topics/contexts debugging}@anchor{13b} @subsubsection Debugging @geindex gccjit;;context;;dump_to_file (C++ function) -@anchor{cp/topics/contexts gccjit context dump_to_file__ssCR i}@anchor{13b} +@anchor{cp/topics/contexts gccjit context dump_to_file__ssCR i}@anchor{13c} @deffn {C++ Function} void gccjit::context::dump_to_file (const std::string& path, int update_locations) To help with debugging: dump a C-like representation to the given path, describing what's been set up on the context. -If "update_locations" is true, then also set up @pxref{13c,,gccjit;;location} +If "update_locations" is true, then also set up @pxref{13d,,gccjit;;location} information throughout the context, pointing at the dump file as if it were a source file. This may be of use in conjunction with @code{GCCJIT::BOOL_OPTION_DEBUGINFO} to allow stepping through the @@ -12474,7 +12489,7 @@ code in a debugger. @end deffn @geindex gccjit;;context;;dump_reproducer_to_file (C++ function) -@anchor{cp/topics/contexts gccjit context dump_reproducer_to_file__gcc_jit_contextP cCP}@anchor{13d} +@anchor{cp/topics/contexts gccjit context dump_reproducer_to_file__gcc_jit_contextP cCP}@anchor{13e} @deffn {C++ Function} void gccjit::context::dump_reproducer_to_file (gcc_jit_context* ctxt, const char* path) This is a thin wrapper around the C API @@ -12486,7 +12501,7 @@ for seeing what the C++ bindings are doing at the C level. @end deffn @node Options<4>,,Debugging<2>,Compilation contexts<2> -@anchor{cp/topics/contexts options}@anchor{13e} +@anchor{cp/topics/contexts options}@anchor{13f} @subsubsection Options @@ -12499,12 +12514,12 @@ for seeing what the C++ bindings are doing at the C level. @end menu @node String Options<2>,Boolean options<2>,,Options<4> -@anchor{cp/topics/contexts string-options}@anchor{13f} +@anchor{cp/topics/contexts string-options}@anchor{140} @subsubsection String Options @geindex gccjit;;context;;set_str_option (C++ function) -@anchor{cp/topics/contexts gccjit context set_str_option__enum cCP}@anchor{140} +@anchor{cp/topics/contexts gccjit context set_str_option__enum cCP}@anchor{141} @deffn {C++ Function} void gccjit::context::set_str_option (enum gcc_jit_str_option, const char* value) Set a string option of the context. @@ -12515,12 +12530,12 @@ meaning. @end deffn @node Boolean options<2>,Integer options<2>,String Options<2>,Options<4> -@anchor{cp/topics/contexts boolean-options}@anchor{141} +@anchor{cp/topics/contexts boolean-options}@anchor{142} @subsubsection Boolean options @geindex gccjit;;context;;set_bool_option (C++ function) -@anchor{cp/topics/contexts gccjit context set_bool_option__enum i}@anchor{10f} +@anchor{cp/topics/contexts gccjit context set_bool_option__enum i}@anchor{110} @deffn {C++ Function} void gccjit::context::set_bool_option (enum gcc_jit_bool_option, int value) Set a boolean option of the context. @@ -12531,7 +12546,7 @@ meaning. @end deffn @geindex gccjit;;context;;set_bool_allow_unreachable_blocks (C++ function) -@anchor{cp/topics/contexts gccjit context set_bool_allow_unreachable_blocks__i}@anchor{142} +@anchor{cp/topics/contexts gccjit context set_bool_allow_unreachable_blocks__i}@anchor{143} @deffn {C++ Function} void gccjit::context::set_bool_allow_unreachable_blocks (int bool_value) By default, libgccjit will issue an error about unreachable blocks @@ -12552,7 +12567,7 @@ its presence using @end deffn @geindex gccjit;;context;;set_bool_use_external_driver (C++ function) -@anchor{cp/topics/contexts gccjit context set_bool_use_external_driver__i}@anchor{143} +@anchor{cp/topics/contexts gccjit context set_bool_use_external_driver__i}@anchor{144} @deffn {C++ Function} void gccjit::context::set_bool_use_external_driver (int bool_value) libgccjit internally generates assembler, and uses "driver" code @@ -12576,12 +12591,12 @@ its presence using @end deffn @node Integer options<2>,Additional command-line options<2>,Boolean options<2>,Options<4> -@anchor{cp/topics/contexts integer-options}@anchor{144} +@anchor{cp/topics/contexts integer-options}@anchor{145} @subsubsection Integer options @geindex gccjit;;context;;set_int_option (C++ function) -@anchor{cp/topics/contexts gccjit context set_int_option__enum i}@anchor{110} +@anchor{cp/topics/contexts gccjit context set_int_option__enum i}@anchor{111} @deffn {C++ Function} void gccjit::context::set_int_option (enum gcc_jit_int_option, int value) Set an integer option of the context. @@ -12592,12 +12607,12 @@ meaning. @end deffn @node Additional command-line options<2>,,Integer options<2>,Options<4> -@anchor{cp/topics/contexts additional-command-line-options}@anchor{145} +@anchor{cp/topics/contexts additional-command-line-options}@anchor{146} @subsubsection Additional command-line options @geindex gccjit;;context;;add_command_line_option (C++ function) -@anchor{cp/topics/contexts gccjit context add_command_line_option__cCP}@anchor{146} +@anchor{cp/topics/contexts gccjit context add_command_line_option__cCP}@anchor{147} @deffn {C++ Function} void gccjit::context::add_command_line_option (const char* optname) Add an arbitrary gcc command-line option to the context for use @@ -12634,18 +12649,18 @@ its presence using @c . @node Objects<2>,Types<2>,Compilation contexts<2>,Topic Reference<2> -@anchor{cp/topics/objects objects}@anchor{147}@anchor{cp/topics/objects doc}@anchor{148} +@anchor{cp/topics/objects objects}@anchor{148}@anchor{cp/topics/objects doc}@anchor{149} @subsection Objects @geindex gccjit;;object (C++ class) -@anchor{cp/topics/objects gccjit object}@anchor{149} +@anchor{cp/topics/objects gccjit object}@anchor{14a} @deffn {C++ Class} gccjit::object @end deffn Almost every entity in the API (with the exception of -@pxref{134,,gccjit;;context} and @pxref{16,,gcc_jit_result *}) is a -"contextual" object, a @pxref{149,,gccjit;;object}. +@pxref{135,,gccjit;;context} and @pxref{16,,gcc_jit_result *}) is a +"contextual" object, a @pxref{14a,,gccjit;;object}. A JIT object: @@ -12655,7 +12670,7 @@ A JIT object: @itemize * @item -is associated with a @pxref{134,,gccjit;;context}. +is associated with a @pxref{135,,gccjit;;context}. @item is automatically cleaned up for you when its context is released so @@ -12682,17 +12697,17 @@ The C++ class hierarchy within the @code{gccjit} namespace looks like this: @noindent -The @pxref{149,,gccjit;;object} base class has the following operations: +The @pxref{14a,,gccjit;;object} base class has the following operations: @geindex gccjit;;object;;get_context (C++ function) -@anchor{cp/topics/objects gccjit object get_contextC}@anchor{14a} +@anchor{cp/topics/objects gccjit object get_contextC}@anchor{14b} @deffn {C++ Function} gccjit::context gccjit::object::get_context () const Which context is the obj within? @end deffn @geindex gccjit;;object;;get_debug_string (C++ function) -@anchor{cp/topics/objects gccjit object get_debug_stringC}@anchor{10a} +@anchor{cp/topics/objects gccjit object get_debug_stringC}@anchor{10b} @deffn {C++ Function} std::string gccjit::object::get_debug_string () const Generate a human-readable description for the given object. @@ -12732,16 +12747,16 @@ obj: 4.0 * (float)i @c . @node Types<2>,Expressions<2>,Objects<2>,Topic Reference<2> -@anchor{cp/topics/types doc}@anchor{14b}@anchor{cp/topics/types types}@anchor{14c} +@anchor{cp/topics/types doc}@anchor{14c}@anchor{cp/topics/types types}@anchor{14d} @subsection Types @geindex gccjit;;type (C++ class) -@anchor{cp/topics/types gccjit type}@anchor{14d} +@anchor{cp/topics/types gccjit type}@anchor{14e} @deffn {C++ Class} gccjit::type gccjit::type represents a type within the library. It is a subclass -of @pxref{149,,gccjit;;object}. +of @pxref{14a,,gccjit;;object}. @end deffn Types can be created in several ways: @@ -12751,7 +12766,7 @@ Types can be created in several ways: @item fundamental types can be accessed using -@pxref{108,,gccjit;;context;;get_type()}: +@pxref{109,,gccjit;;context;;get_type()}: @example gccjit::type int_type = ctxt.get_type (GCC_JIT_TYPE_INT); @@ -12771,7 +12786,7 @@ See @pxref{b,,gcc_jit_context_get_type()} for the available types. @item derived types can be accessed by using functions such as -@pxref{14e,,gccjit;;type;;get_pointer()} and @pxref{14f,,gccjit;;type;;get_const()}: +@pxref{14f,,gccjit;;type;;get_pointer()} and @pxref{150,,gccjit;;type;;get_const()}: @example gccjit::type const_int_star = int_type.get_const ().get_pointer (); @@ -12792,12 +12807,12 @@ by creating structures (see below). @end menu @node Standard types<2>,Pointers const and volatile<2>,,Types<2> -@anchor{cp/topics/types standard-types}@anchor{150} +@anchor{cp/topics/types standard-types}@anchor{151} @subsubsection Standard types @geindex gccjit;;context;;get_type (C++ function) -@anchor{cp/topics/types gccjit context get_type__enum}@anchor{108} +@anchor{cp/topics/types gccjit context get_type__enum}@anchor{109} @deffn {C++ Function} gccjit::type gccjit::context::get_type (enum gcc_jit_types) Access a specific type. This is a thin wrapper around @@ -12805,14 +12820,14 @@ Access a specific type. This is a thin wrapper around @end deffn @geindex gccjit;;context;;get_int_type (C++ function) -@anchor{cp/topics/types gccjit context get_int_type__s i}@anchor{151} +@anchor{cp/topics/types gccjit context get_int_type__s i}@anchor{152} @deffn {C++ Function} gccjit::type gccjit::context::get_int_type (size_t num_bytes, int is_signed) Access the integer type of the given size. @end deffn @geindex gccjit;;context;;get_int_type (C++ function) -@anchor{cp/topics/types gccjit context get_int_type T}@anchor{152} +@anchor{cp/topics/types gccjit context get_int_type T}@anchor{153} @deffn {C++ Function} gccjit::type gccjit::context::get_int_type () Access the given integer type. For example, you could map the @@ -12826,12 +12841,12 @@ gccjit::type t = ctxt.get_int_type (); @end deffn @node Pointers const and volatile<2>,Structures and unions<2>,Standard types<2>,Types<2> -@anchor{cp/topics/types pointers-const-and-volatile}@anchor{153} +@anchor{cp/topics/types pointers-const-and-volatile}@anchor{154} @subsubsection Pointers, @cite{const}, and @cite{volatile} @geindex gccjit;;type;;get_pointer (C++ function) -@anchor{cp/topics/types gccjit type get_pointer}@anchor{14e} +@anchor{cp/topics/types gccjit type get_pointer}@anchor{14f} @deffn {C++ Function} gccjit::type gccjit::type::get_pointer () Given type "T", get type "T*". @@ -12840,21 +12855,21 @@ Given type "T", get type "T*". @c FIXME: get_const doesn't seem to exist @geindex gccjit;;type;;get_const (C++ function) -@anchor{cp/topics/types gccjit type get_const}@anchor{14f} +@anchor{cp/topics/types gccjit type get_const}@anchor{150} @deffn {C++ Function} gccjit::type gccjit::type::get_const () Given type "T", get type "const T". @end deffn @geindex gccjit;;type;;get_volatile (C++ function) -@anchor{cp/topics/types gccjit type get_volatile}@anchor{154} +@anchor{cp/topics/types gccjit type get_volatile}@anchor{155} @deffn {C++ Function} gccjit::type gccjit::type::get_volatile () Given type "T", get type "volatile T". @end deffn @geindex gccjit;;context;;new_array_type (C++ function) -@anchor{cp/topics/types gccjit context new_array_type__gccjit type i gccjit location}@anchor{155} +@anchor{cp/topics/types gccjit context new_array_type__gccjit type i gccjit location}@anchor{156} @deffn {C++ Function} gccjit::type gccjit::context::new_array_type (gccjit::type element_type, int num_elements, gccjit::location loc) Given type "T", get type "T[N]" (for a constant N). @@ -12862,31 +12877,31 @@ Param "loc" is optional. @end deffn @node Structures and unions<2>,,Pointers const and volatile<2>,Types<2> -@anchor{cp/topics/types structures-and-unions}@anchor{156} +@anchor{cp/topics/types structures-and-unions}@anchor{157} @subsubsection Structures and unions @geindex gccjit;;struct_ (C++ class) -@anchor{cp/topics/types gccjit struct_}@anchor{157} +@anchor{cp/topics/types gccjit struct_}@anchor{158} @deffn {C++ Class} gccjit::struct_ @end deffn A compound type analagous to a C @cite{struct}. -@pxref{157,,gccjit;;struct_} is a subclass of @pxref{14d,,gccjit;;type} (and thus -of @pxref{149,,gccjit;;object} in turn). +@pxref{158,,gccjit;;struct_} is a subclass of @pxref{14e,,gccjit;;type} (and thus +of @pxref{14a,,gccjit;;object} in turn). @geindex gccjit;;field (C++ class) -@anchor{cp/topics/types gccjit field}@anchor{158} +@anchor{cp/topics/types gccjit field}@anchor{159} @deffn {C++ Class} gccjit::field @end deffn -A field within a @pxref{157,,gccjit;;struct_}. +A field within a @pxref{158,,gccjit;;struct_}. -@pxref{158,,gccjit;;field} is a subclass of @pxref{149,,gccjit;;object}. +@pxref{159,,gccjit;;field} is a subclass of @pxref{14a,,gccjit;;object}. -You can model C @cite{struct} types by creating @pxref{157,,gccjit;;struct_} and -@pxref{158,,gccjit;;field} instances, in either order: +You can model C @cite{struct} types by creating @pxref{158,,gccjit;;struct_} and +@pxref{159,,gccjit;;field} instances, in either order: @itemize * @@ -12942,14 +12957,14 @@ node.set_fields (fields); @c FIXME: the above API doesn't seem to exist yet @geindex gccjit;;context;;new_field (C++ function) -@anchor{cp/topics/types gccjit context new_field__gccjit type cCP gccjit location}@anchor{159} +@anchor{cp/topics/types gccjit context new_field__gccjit type cCP gccjit location}@anchor{15a} @deffn {C++ Function} gccjit::field gccjit::context::new_field (gccjit::type type, const char* name, gccjit::location loc) Construct a new field, with the given type and name. @end deffn @geindex gccjit;;context;;new_struct_type (C++ function) -@anchor{cp/topics/types gccjit context new_struct_type__ssCR std vector field R gccjit location}@anchor{15a} +@anchor{cp/topics/types gccjit context new_struct_type__ssCR std vector field R gccjit location}@anchor{15b} @deffn {C++ Function} gccjit::struct_ gccjit::context::new_struct_type (const std::string& name, std::vector& fields, gccjit::location loc) @quotation @@ -12959,7 +12974,7 @@ Construct a new struct type, with the given name and fields. @end deffn @geindex gccjit;;context;;new_opaque_struct (C++ function) -@anchor{cp/topics/types gccjit context new_opaque_struct__ssCR gccjit location}@anchor{15b} +@anchor{cp/topics/types gccjit context new_opaque_struct__ssCR gccjit location}@anchor{15c} @deffn {C++ Function} gccjit::struct_ gccjit::context::new_opaque_struct (const std::string& name, gccjit::location loc) Construct a new struct type, with the given name, but without @@ -12986,7 +13001,7 @@ size of the struct is not known), or later specified using @c . @node Expressions<2>,Creating and using functions<2>,Types<2>,Topic Reference<2> -@anchor{cp/topics/expressions expressions}@anchor{15c}@anchor{cp/topics/expressions doc}@anchor{15d} +@anchor{cp/topics/expressions expressions}@anchor{15d}@anchor{cp/topics/expressions doc}@anchor{15e} @subsection Expressions @@ -13012,17 +13027,17 @@ Lvalues @node Rvalues<2>,Lvalues<2>,,Expressions<2> -@anchor{cp/topics/expressions rvalues}@anchor{15e} +@anchor{cp/topics/expressions rvalues}@anchor{15f} @subsubsection Rvalues @geindex gccjit;;rvalue (C++ class) -@anchor{cp/topics/expressions gccjit rvalue}@anchor{15f} +@anchor{cp/topics/expressions gccjit rvalue}@anchor{160} @deffn {C++ Class} gccjit::rvalue @end deffn -A @pxref{15f,,gccjit;;rvalue} is an expression that can be computed. It is a -subclass of @pxref{149,,gccjit;;object}, and is a thin wrapper around +A @pxref{160,,gccjit;;rvalue} is an expression that can be computed. It is a +subclass of @pxref{14a,,gccjit;;object}, and is a thin wrapper around @pxref{13,,gcc_jit_rvalue *} from the C API. It can be simple, e.g.: @@ -13068,7 +13083,7 @@ Every rvalue has an associated type, and the API will check to ensure that types match up correctly (otherwise the context will emit an error). @geindex gccjit;;rvalue;;get_type (C++ function) -@anchor{cp/topics/expressions gccjit rvalue get_type}@anchor{160} +@anchor{cp/topics/expressions gccjit rvalue get_type}@anchor{161} @deffn {C++ Function} gccjit::type gccjit::rvalue::get_type () Get the type of this rvalue. @@ -13085,12 +13100,12 @@ Get the type of this rvalue. @end menu @node Simple expressions<2>,Unary Operations<2>,,Rvalues<2> -@anchor{cp/topics/expressions simple-expressions}@anchor{161} +@anchor{cp/topics/expressions simple-expressions}@anchor{162} @subsubsection Simple expressions @geindex gccjit;;context;;new_rvalue (C++ function) -@anchor{cp/topics/expressions gccjit context new_rvalue__gccjit type iC}@anchor{11c} +@anchor{cp/topics/expressions gccjit context new_rvalue__gccjit type iC}@anchor{11d} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_rvalue (gccjit::type numeric_type, int value) const Given a numeric type (integer or floating point), build an rvalue for @@ -13098,7 +13113,7 @@ the given constant @code{int} value. @end deffn @geindex gccjit;;context;;new_rvalue (C++ function) -@anchor{cp/topics/expressions gccjit context new_rvalue__gccjit type lC}@anchor{162} +@anchor{cp/topics/expressions gccjit context new_rvalue__gccjit type lC}@anchor{163} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_rvalue (gccjit::type numeric_type, long value) const Given a numeric type (integer or floating point), build an rvalue for @@ -13106,7 +13121,7 @@ the given constant @code{long} value. @end deffn @geindex gccjit;;context;;zero (C++ function) -@anchor{cp/topics/expressions gccjit context zero__gccjit typeC}@anchor{118} +@anchor{cp/topics/expressions gccjit context zero__gccjit typeC}@anchor{119} @deffn {C++ Function} gccjit::rvalue gccjit::context::zero (gccjit::type numeric_type) const Given a numeric type (integer or floating point), get the rvalue for @@ -13120,7 +13135,7 @@ ctxt.new_rvalue (numeric_type, 0) @end deffn @geindex gccjit;;context;;one (C++ function) -@anchor{cp/topics/expressions gccjit context one__gccjit typeC}@anchor{163} +@anchor{cp/topics/expressions gccjit context one__gccjit typeC}@anchor{164} @deffn {C++ Function} gccjit::rvalue gccjit::context::one (gccjit::type numeric_type) const Given a numeric type (integer or floating point), get the rvalue for @@ -13134,7 +13149,7 @@ ctxt.new_rvalue (numeric_type, 1) @end deffn @geindex gccjit;;context;;new_rvalue (C++ function) -@anchor{cp/topics/expressions gccjit context new_rvalue__gccjit type doubleC}@anchor{164} +@anchor{cp/topics/expressions gccjit context new_rvalue__gccjit type doubleC}@anchor{165} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_rvalue (gccjit::type numeric_type, double value) const Given a numeric type (integer or floating point), build an rvalue for @@ -13142,14 +13157,14 @@ the given constant @code{double} value. @end deffn @geindex gccjit;;context;;new_rvalue (C++ function) -@anchor{cp/topics/expressions gccjit context new_rvalue__gccjit type voidPC}@anchor{165} +@anchor{cp/topics/expressions gccjit context new_rvalue__gccjit type voidPC}@anchor{166} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_rvalue (gccjit::type pointer_type, void* value) const Given a pointer type, build an rvalue for the given address. @end deffn @geindex gccjit;;context;;new_rvalue (C++ function) -@anchor{cp/topics/expressions gccjit context new_rvalue__ssCRC}@anchor{166} +@anchor{cp/topics/expressions gccjit context new_rvalue__ssCRC}@anchor{167} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_rvalue (const std::string& value) const Generate an rvalue of type @code{GCC_JIT_TYPE_CONST_CHAR_PTR} for @@ -13157,12 +13172,12 @@ the given string. This is akin to a string literal. @end deffn @node Unary Operations<2>,Binary Operations<2>,Simple expressions<2>,Rvalues<2> -@anchor{cp/topics/expressions unary-operations}@anchor{167} +@anchor{cp/topics/expressions unary-operations}@anchor{168} @subsubsection Unary Operations @geindex gccjit;;context;;new_unary_op (C++ function) -@anchor{cp/topics/expressions gccjit context new_unary_op__enum gccjit type gccjit rvalue gccjit location}@anchor{168} +@anchor{cp/topics/expressions gccjit context new_unary_op__enum gccjit type gccjit rvalue gccjit location}@anchor{169} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_unary_op (enum gcc_jit_unary_op, gccjit::type result_type, gccjit::rvalue rvalue, gccjit::location loc) Build a unary operation out of an input rvalue. @@ -13178,7 +13193,7 @@ There are shorter ways to spell the various specific kinds of unary operation: @geindex gccjit;;context;;new_minus (C++ function) -@anchor{cp/topics/expressions gccjit context new_minus__gccjit type gccjit rvalue gccjit location}@anchor{169} +@anchor{cp/topics/expressions gccjit context new_minus__gccjit type gccjit rvalue gccjit location}@anchor{16a} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_minus (gccjit::type result_type, gccjit::rvalue a, gccjit::location loc) Negate an arithmetic value; for example: @@ -13199,7 +13214,7 @@ builds the equivalent of this C expression: @end deffn @geindex new_bitwise_negate (C++ function) -@anchor{cp/topics/expressions new_bitwise_negate__gccjit type gccjit rvalue gccjit location}@anchor{16a} +@anchor{cp/topics/expressions new_bitwise_negate__gccjit type gccjit rvalue gccjit location}@anchor{16b} @deffn {C++ Function} gccjit::rvalue new_bitwise_negate (gccjit::type result_type, gccjit::rvalue a, gccjit::location loc) Bitwise negation of an integer value (one's complement); for example: @@ -13220,7 +13235,7 @@ builds the equivalent of this C expression: @end deffn @geindex new_logical_negate (C++ function) -@anchor{cp/topics/expressions new_logical_negate__gccjit type gccjit rvalue gccjit location}@anchor{16b} +@anchor{cp/topics/expressions new_logical_negate__gccjit type gccjit rvalue gccjit location}@anchor{16c} @deffn {C++ Function} gccjit::rvalue new_logical_negate (gccjit::type result_type, gccjit::rvalue a, gccjit::location loc) Logical negation of an arithmetic or pointer value; for example: @@ -13243,7 +13258,7 @@ builds the equivalent of this C expression: The most concise way to spell them is with overloaded operators: @geindex operator- (C++ function) -@anchor{cp/topics/expressions sub-operator__gccjit rvalue}@anchor{16c} +@anchor{cp/topics/expressions sub-operator__gccjit rvalue}@anchor{16d} @deffn {C++ Function} gccjit::rvalue operator- (gccjit::rvalue a) @example @@ -13254,7 +13269,7 @@ gccjit::rvalue negpi = -pi; @end deffn @geindex operator~ (C++ function) -@anchor{cp/topics/expressions inv-operator__gccjit rvalue}@anchor{16d} +@anchor{cp/topics/expressions inv-operator__gccjit rvalue}@anchor{16e} @deffn {C++ Function} gccjit::rvalue operator~ (gccjit::rvalue a) @example @@ -13265,7 +13280,7 @@ gccjit::rvalue mask = ~a; @end deffn @geindex operator! (C++ function) -@anchor{cp/topics/expressions not-operator__gccjit rvalue}@anchor{16e} +@anchor{cp/topics/expressions not-operator__gccjit rvalue}@anchor{16f} @deffn {C++ Function} gccjit::rvalue operator! (gccjit::rvalue a) @example @@ -13276,12 +13291,12 @@ gccjit::rvalue guard = !cond; @end deffn @node Binary Operations<2>,Comparisons<2>,Unary Operations<2>,Rvalues<2> -@anchor{cp/topics/expressions binary-operations}@anchor{16f} +@anchor{cp/topics/expressions binary-operations}@anchor{170} @subsubsection Binary Operations @geindex gccjit;;context;;new_binary_op (C++ function) -@anchor{cp/topics/expressions gccjit context new_binary_op__enum gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{10c} +@anchor{cp/topics/expressions gccjit context new_binary_op__enum gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{10d} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_binary_op (enum gcc_jit_binary_op, gccjit::type result_type, gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) Build a binary operation out of two constituent rvalues. @@ -13297,59 +13312,59 @@ There are shorter ways to spell the various specific kinds of binary operation: @geindex gccjit;;context;;new_plus (C++ function) -@anchor{cp/topics/expressions gccjit context new_plus__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{170} +@anchor{cp/topics/expressions gccjit context new_plus__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{171} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_plus (gccjit::type result_type, gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn @geindex gccjit;;context;;new_minus (C++ function) -@anchor{cp/topics/expressions gccjit context new_minus__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{171} +@anchor{cp/topics/expressions gccjit context new_minus__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{172} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_minus (gccjit::type result_type, gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn @geindex gccjit;;context;;new_mult (C++ function) -@anchor{cp/topics/expressions gccjit context new_mult__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{172} +@anchor{cp/topics/expressions gccjit context new_mult__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{173} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_mult (gccjit::type result_type, gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn @geindex gccjit;;context;;new_divide (C++ function) -@anchor{cp/topics/expressions gccjit context new_divide__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{173} +@anchor{cp/topics/expressions gccjit context new_divide__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{174} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_divide (gccjit::type result_type, gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn @geindex gccjit;;context;;new_modulo (C++ function) -@anchor{cp/topics/expressions gccjit context new_modulo__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{174} +@anchor{cp/topics/expressions gccjit context new_modulo__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{175} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_modulo (gccjit::type result_type, gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn @geindex gccjit;;context;;new_bitwise_and (C++ function) -@anchor{cp/topics/expressions gccjit context new_bitwise_and__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{175} +@anchor{cp/topics/expressions gccjit context new_bitwise_and__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{176} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_bitwise_and (gccjit::type result_type, gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn @geindex gccjit;;context;;new_bitwise_xor (C++ function) -@anchor{cp/topics/expressions gccjit context new_bitwise_xor__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{176} +@anchor{cp/topics/expressions gccjit context new_bitwise_xor__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{177} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_bitwise_xor (gccjit::type result_type, gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn @geindex gccjit;;context;;new_bitwise_or (C++ function) -@anchor{cp/topics/expressions gccjit context new_bitwise_or__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{177} +@anchor{cp/topics/expressions gccjit context new_bitwise_or__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{178} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_bitwise_or (gccjit::type result_type, gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn @geindex gccjit;;context;;new_logical_and (C++ function) -@anchor{cp/topics/expressions gccjit context new_logical_and__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{178} +@anchor{cp/topics/expressions gccjit context new_logical_and__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{179} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_logical_and (gccjit::type result_type, gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn @geindex gccjit;;context;;new_logical_or (C++ function) -@anchor{cp/topics/expressions gccjit context new_logical_or__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{179} +@anchor{cp/topics/expressions gccjit context new_logical_or__gccjit type gccjit rvalue gccjit rvalue gccjit location}@anchor{17a} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_logical_or (gccjit::type result_type, gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn The most concise way to spell them is with overloaded operators: @geindex operator+ (C++ function) -@anchor{cp/topics/expressions add-operator__gccjit rvalue gccjit rvalue}@anchor{17a} +@anchor{cp/topics/expressions add-operator__gccjit rvalue gccjit rvalue}@anchor{17b} @deffn {C++ Function} gccjit::rvalue operator+ (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13360,7 +13375,7 @@ gccjit::rvalue sum = a + b; @end deffn @geindex operator- (C++ function) -@anchor{cp/topics/expressions sub-operator__gccjit rvalue gccjit rvalue}@anchor{17b} +@anchor{cp/topics/expressions sub-operator__gccjit rvalue gccjit rvalue}@anchor{17c} @deffn {C++ Function} gccjit::rvalue operator- (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13371,7 +13386,7 @@ gccjit::rvalue diff = a - b; @end deffn @geindex operator* (C++ function) -@anchor{cp/topics/expressions mul-operator__gccjit rvalue gccjit rvalue}@anchor{17c} +@anchor{cp/topics/expressions mul-operator__gccjit rvalue gccjit rvalue}@anchor{17d} @deffn {C++ Function} gccjit::rvalue operator* (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13382,7 +13397,7 @@ gccjit::rvalue prod = a * b; @end deffn @geindex operator/ (C++ function) -@anchor{cp/topics/expressions div-operator__gccjit rvalue gccjit rvalue}@anchor{17d} +@anchor{cp/topics/expressions div-operator__gccjit rvalue gccjit rvalue}@anchor{17e} @deffn {C++ Function} gccjit::rvalue operator/ (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13393,7 +13408,7 @@ gccjit::rvalue result = a / b; @end deffn @geindex operator% (C++ function) -@anchor{cp/topics/expressions mod-operator__gccjit rvalue gccjit rvalue}@anchor{17e} +@anchor{cp/topics/expressions mod-operator__gccjit rvalue gccjit rvalue}@anchor{17f} @deffn {C++ Function} gccjit::rvalue operator% (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13404,7 +13419,7 @@ gccjit::rvalue mod = a % b; @end deffn @geindex operator& (C++ function) -@anchor{cp/topics/expressions and-operator__gccjit rvalue gccjit rvalue}@anchor{17f} +@anchor{cp/topics/expressions and-operator__gccjit rvalue gccjit rvalue}@anchor{180} @deffn {C++ Function} gccjit::rvalue operator& (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13415,7 +13430,7 @@ gccjit::rvalue x = a & b; @end deffn @geindex operator^ (C++ function) -@anchor{cp/topics/expressions xor-operator__gccjit rvalue gccjit rvalue}@anchor{180} +@anchor{cp/topics/expressions xor-operator__gccjit rvalue gccjit rvalue}@anchor{181} @deffn {C++ Function} gccjit::rvalue operator^ (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13426,7 +13441,7 @@ gccjit::rvalue x = a ^ b; @end deffn @geindex operator| (C++ function) -@anchor{cp/topics/expressions or-operator__gccjit rvalue gccjit rvalue}@anchor{181} +@anchor{cp/topics/expressions or-operator__gccjit rvalue gccjit rvalue}@anchor{182} @deffn {C++ Function} gccjit::rvalue operator| (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13437,7 +13452,7 @@ gccjit::rvalue x = a | b; @end deffn @geindex operator&& (C++ function) -@anchor{cp/topics/expressions sand-operator__gccjit rvalue gccjit rvalue}@anchor{182} +@anchor{cp/topics/expressions sand-operator__gccjit rvalue gccjit rvalue}@anchor{183} @deffn {C++ Function} gccjit::rvalue operator&& (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13448,7 +13463,7 @@ gccjit::rvalue cond = a && b; @end deffn @geindex operator|| (C++ function) -@anchor{cp/topics/expressions sor-operator__gccjit rvalue gccjit rvalue}@anchor{183} +@anchor{cp/topics/expressions sor-operator__gccjit rvalue gccjit rvalue}@anchor{184} @deffn {C++ Function} gccjit::rvalue operator|| (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13471,12 +13486,12 @@ gccjit::rvalue discriminant = (b * b) - (four * a * c); @end quotation @node Comparisons<2>,Function calls<2>,Binary Operations<2>,Rvalues<2> -@anchor{cp/topics/expressions comparisons}@anchor{184} +@anchor{cp/topics/expressions comparisons}@anchor{185} @subsubsection Comparisons @geindex gccjit;;context;;new_comparison (C++ function) -@anchor{cp/topics/expressions gccjit context new_comparison__enum gccjit rvalue gccjit rvalue gccjit location}@anchor{119} +@anchor{cp/topics/expressions gccjit context new_comparison__enum gccjit rvalue gccjit rvalue gccjit location}@anchor{11a} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_comparison (enum gcc_jit_comparison, gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) Build a boolean rvalue out of the comparison of two other rvalues. @@ -13492,39 +13507,39 @@ There are shorter ways to spell the various specific kinds of binary operation: @geindex gccjit;;context;;new_eq (C++ function) -@anchor{cp/topics/expressions gccjit context new_eq__gccjit rvalue gccjit rvalue gccjit location}@anchor{185} +@anchor{cp/topics/expressions gccjit context new_eq__gccjit rvalue gccjit rvalue gccjit location}@anchor{186} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_eq (gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn @geindex gccjit;;context;;new_ne (C++ function) -@anchor{cp/topics/expressions gccjit context new_ne__gccjit rvalue gccjit rvalue gccjit location}@anchor{186} +@anchor{cp/topics/expressions gccjit context new_ne__gccjit rvalue gccjit rvalue gccjit location}@anchor{187} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_ne (gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn @geindex gccjit;;context;;new_lt (C++ function) -@anchor{cp/topics/expressions gccjit context new_lt__gccjit rvalue gccjit rvalue gccjit location}@anchor{187} +@anchor{cp/topics/expressions gccjit context new_lt__gccjit rvalue gccjit rvalue gccjit location}@anchor{188} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_lt (gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn @geindex gccjit;;context;;new_le (C++ function) -@anchor{cp/topics/expressions gccjit context new_le__gccjit rvalue gccjit rvalue gccjit location}@anchor{188} +@anchor{cp/topics/expressions gccjit context new_le__gccjit rvalue gccjit rvalue gccjit location}@anchor{189} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_le (gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn @geindex gccjit;;context;;new_gt (C++ function) -@anchor{cp/topics/expressions gccjit context new_gt__gccjit rvalue gccjit rvalue gccjit location}@anchor{189} +@anchor{cp/topics/expressions gccjit context new_gt__gccjit rvalue gccjit rvalue gccjit location}@anchor{18a} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_gt (gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn @geindex gccjit;;context;;new_ge (C++ function) -@anchor{cp/topics/expressions gccjit context new_ge__gccjit rvalue gccjit rvalue gccjit location}@anchor{18a} +@anchor{cp/topics/expressions gccjit context new_ge__gccjit rvalue gccjit rvalue gccjit location}@anchor{18b} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_ge (gccjit::rvalue a, gccjit::rvalue b, gccjit::location loc) @end deffn The most concise way to spell them is with overloaded operators: @geindex operator== (C++ function) -@anchor{cp/topics/expressions eq-operator__gccjit rvalue gccjit rvalue}@anchor{18b} +@anchor{cp/topics/expressions eq-operator__gccjit rvalue gccjit rvalue}@anchor{18c} @deffn {C++ Function} gccjit::rvalue operator== (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13535,7 +13550,7 @@ gccjit::rvalue cond = (a == ctxt.zero (t_int)); @end deffn @geindex operator!= (C++ function) -@anchor{cp/topics/expressions neq-operator__gccjit rvalue gccjit rvalue}@anchor{18c} +@anchor{cp/topics/expressions neq-operator__gccjit rvalue gccjit rvalue}@anchor{18d} @deffn {C++ Function} gccjit::rvalue operator!= (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13546,7 +13561,7 @@ gccjit::rvalue cond = (i != j); @end deffn @geindex operator< (C++ function) -@anchor{cp/topics/expressions lt-operator__gccjit rvalue gccjit rvalue}@anchor{18d} +@anchor{cp/topics/expressions lt-operator__gccjit rvalue gccjit rvalue}@anchor{18e} @deffn {C++ Function} gccjit::rvalue operator< (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13557,7 +13572,7 @@ gccjit::rvalue cond = i < n; @end deffn @geindex operator<= (C++ function) -@anchor{cp/topics/expressions lte-operator__gccjit rvalue gccjit rvalue}@anchor{18e} +@anchor{cp/topics/expressions lte-operator__gccjit rvalue gccjit rvalue}@anchor{18f} @deffn {C++ Function} gccjit::rvalue operator<= (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13568,7 +13583,7 @@ gccjit::rvalue cond = i <= n; @end deffn @geindex operator> (C++ function) -@anchor{cp/topics/expressions gt-operator__gccjit rvalue gccjit rvalue}@anchor{18f} +@anchor{cp/topics/expressions gt-operator__gccjit rvalue gccjit rvalue}@anchor{190} @deffn {C++ Function} gccjit::rvalue operator> (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13579,7 +13594,7 @@ gccjit::rvalue cond = (ch > limit); @end deffn @geindex operator>= (C++ function) -@anchor{cp/topics/expressions gte-operator__gccjit rvalue gccjit rvalue}@anchor{190} +@anchor{cp/topics/expressions gte-operator__gccjit rvalue gccjit rvalue}@anchor{191} @deffn {C++ Function} gccjit::rvalue operator>= (gccjit::rvalue a, gccjit::rvalue b) @example @@ -13592,12 +13607,12 @@ gccjit::rvalue cond = (score >= ctxt.new_rvalue (t_int, 100)); @c TODO: beyond this point @node Function calls<2>,Type-coercion<2>,Comparisons<2>,Rvalues<2> -@anchor{cp/topics/expressions function-calls}@anchor{191} +@anchor{cp/topics/expressions function-calls}@anchor{192} @subsubsection Function calls @geindex gcc_jit_context_new_call (C++ function) -@anchor{cp/topics/expressions gcc_jit_context_new_call__gcc_jit_contextP gcc_jit_locationP gcc_jit_functionP i gcc_jit_rvaluePP}@anchor{192} +@anchor{cp/topics/expressions gcc_jit_context_new_call__gcc_jit_contextP gcc_jit_locationP gcc_jit_functionP i gcc_jit_rvaluePP}@anchor{193} @deffn {C++ Function} gcc_jit_rvalue* gcc_jit_context_new_call (gcc_jit_context* ctxt, gcc_jit_location* loc, gcc_jit_function* func, int numargs, gcc_jit_rvalue** args) Given a function and the given table of argument rvalues, construct a @@ -13606,14 +13621,14 @@ call to the function, with the result as an rvalue. @cartouche @quotation Note @code{gccjit::context::new_call()} merely builds a -@pxref{15f,,gccjit;;rvalue} i.e. an expression that can be evaluated, +@pxref{160,,gccjit;;rvalue} i.e. an expression that can be evaluated, perhaps as part of a more complicated expression. The call @emph{won't} happen unless you add a statement to a function that evaluates the expression. For example, if you want to call a function and discard the result (or to call a function with @code{void} return type), use -@pxref{193,,gccjit;;block;;add_eval()}: +@pxref{194,,gccjit;;block;;add_eval()}: @example /* Add "(void)printf (arg0, arg1);". */ @@ -13626,12 +13641,12 @@ block.add_eval (ctxt.new_call (printf_func, arg0, arg1)); @end deffn @node Type-coercion<2>,,Function calls<2>,Rvalues<2> -@anchor{cp/topics/expressions type-coercion}@anchor{194} +@anchor{cp/topics/expressions type-coercion}@anchor{195} @subsubsection Type-coercion @geindex gccjit;;context;;new_cast (C++ function) -@anchor{cp/topics/expressions gccjit context new_cast__gccjit rvalue gccjit type gccjit location}@anchor{195} +@anchor{cp/topics/expressions gccjit context new_cast__gccjit rvalue gccjit type gccjit location}@anchor{196} @deffn {C++ Function} gccjit::rvalue gccjit::context::new_cast (gccjit::rvalue rvalue, gccjit::type type, gccjit::location loc) Given an rvalue of T, construct another rvalue of another type. @@ -13656,24 +13671,24 @@ P* <-> Q*, for pointer types P and Q @end deffn @node Lvalues<2>,Working with pointers structs and unions<2>,Rvalues<2>,Expressions<2> -@anchor{cp/topics/expressions lvalues}@anchor{196} +@anchor{cp/topics/expressions lvalues}@anchor{197} @subsubsection Lvalues @geindex gccjit;;lvalue (C++ class) -@anchor{cp/topics/expressions gccjit lvalue}@anchor{197} +@anchor{cp/topics/expressions gccjit lvalue}@anchor{198} @deffn {C++ Class} gccjit::lvalue @end deffn An lvalue is something that can of the @emph{left}-hand side of an assignment: a storage area (such as a variable). It is a subclass of -@pxref{15f,,gccjit;;rvalue}, where the rvalue is computed by reading from the +@pxref{160,,gccjit;;rvalue}, where the rvalue is computed by reading from the storage area. It iss a thin wrapper around @pxref{24,,gcc_jit_lvalue *} from the C API. @geindex gccjit;;lvalue;;get_address (C++ function) -@anchor{cp/topics/expressions gccjit lvalue get_address__gccjit location}@anchor{198} +@anchor{cp/topics/expressions gccjit lvalue get_address__gccjit location}@anchor{199} @deffn {C++ Function} gccjit::rvalue gccjit::lvalue::get_address (gccjit::location loc) Take the address of an lvalue; analogous to: @@ -13695,27 +13710,27 @@ Parameter "loc" is optional. @end menu @node Global variables<2>,,,Lvalues<2> -@anchor{cp/topics/expressions global-variables}@anchor{199} +@anchor{cp/topics/expressions global-variables}@anchor{19a} @subsubsection Global variables @geindex gccjit;;context;;new_global (C++ function) -@anchor{cp/topics/expressions gccjit context new_global__enum gccjit type cCP gccjit location}@anchor{19a} +@anchor{cp/topics/expressions gccjit context new_global__enum gccjit type cCP gccjit location}@anchor{19b} @deffn {C++ Function} gccjit::lvalue gccjit::context::new_global (enum gcc_jit_global_kind, gccjit::type type, const char* name, gccjit::location loc) Add a new global variable of the given type and name to the context. -This is a thin wrapper around @pxref{b5,,gcc_jit_context_new_global()} from +This is a thin wrapper around @pxref{b6,,gcc_jit_context_new_global()} from the C API; the "kind" parameter has the same meaning as there. @end deffn @node Working with pointers structs and unions<2>,,Lvalues<2>,Expressions<2> -@anchor{cp/topics/expressions working-with-pointers-structs-and-unions}@anchor{19b} +@anchor{cp/topics/expressions working-with-pointers-structs-and-unions}@anchor{19c} @subsubsection Working with pointers, structs and unions @geindex gccjit;;rvalue;;dereference (C++ function) -@anchor{cp/topics/expressions gccjit rvalue dereference__gccjit location}@anchor{19c} +@anchor{cp/topics/expressions gccjit rvalue dereference__gccjit location}@anchor{19d} @deffn {C++ Function} gccjit::lvalue gccjit::rvalue::dereference (gccjit::location loc) Given an rvalue of pointer type @code{T *}, dereferencing the pointer, @@ -13736,7 +13751,7 @@ If you don't need to specify the location, this can also be expressed using an overloaded operator: @geindex gccjit;;rvalue;;operator* (C++ function) -@anchor{cp/topics/expressions gccjit rvalue mul-operator}@anchor{19d} +@anchor{cp/topics/expressions gccjit rvalue mul-operator}@anchor{19e} @deffn {C++ Function} gccjit::lvalue gccjit::rvalue::operator* () @example @@ -13749,7 +13764,7 @@ gccjit::lvalue content = *ptr; Field access is provided separately for both lvalues and rvalues: @geindex gccjit;;lvalue;;access_field (C++ function) -@anchor{cp/topics/expressions gccjit lvalue access_field__gccjit field gccjit location}@anchor{19e} +@anchor{cp/topics/expressions gccjit lvalue access_field__gccjit field gccjit location}@anchor{19f} @deffn {C++ Function} gccjit::lvalue gccjit::lvalue::access_field (gccjit::field field, gccjit::location loc) Given an lvalue of struct or union type, access the given field, @@ -13765,7 +13780,7 @@ in C. @end deffn @geindex gccjit;;rvalue;;access_field (C++ function) -@anchor{cp/topics/expressions gccjit rvalue access_field__gccjit field gccjit location}@anchor{19f} +@anchor{cp/topics/expressions gccjit rvalue access_field__gccjit field gccjit location}@anchor{1a0} @deffn {C++ Function} gccjit::rvalue gccjit::rvalue::access_field (gccjit::field field, gccjit::location loc) Given an rvalue of struct or union type, access the given field @@ -13781,7 +13796,7 @@ in C. @end deffn @geindex gccjit;;rvalue;;dereference_field (C++ function) -@anchor{cp/topics/expressions gccjit rvalue dereference_field__gccjit field gccjit location}@anchor{1a0} +@anchor{cp/topics/expressions gccjit rvalue dereference_field__gccjit field gccjit location}@anchor{1a1} @deffn {C++ Function} gccjit::lvalue gccjit::rvalue::dereference_field (gccjit::field field, gccjit::location loc) Given an rvalue of pointer type @code{T *} where T is of struct or union @@ -13797,7 +13812,7 @@ in C, itself equivalent to @code{(*EXPR).FIELD}. @end deffn @geindex gccjit;;context;;new_array_access (C++ function) -@anchor{cp/topics/expressions gccjit context new_array_access__gccjit rvalue gccjit rvalue gccjit location}@anchor{1a1} +@anchor{cp/topics/expressions gccjit context new_array_access__gccjit rvalue gccjit rvalue gccjit location}@anchor{1a2} @deffn {C++ Function} gccjit::lvalue gccjit::context::new_array_access (gccjit::rvalue ptr, gccjit::rvalue index, gccjit::location loc) Given an rvalue of pointer type @code{T *}, get at the element @cite{T} at @@ -13816,7 +13831,7 @@ in C (or, indeed, to @code{PTR + INDEX}). Parameter "loc" is optional. @end deffn -For array accesses where you don't need to specify a @pxref{13c,,gccjit;;location}, +For array accesses where you don't need to specify a @pxref{13d,,gccjit;;location}, two overloaded operators are available: @quotation @@ -13856,7 +13871,7 @@ gccjit::lvalue element = array[0]; @c . @node Creating and using functions<2>,Source Locations<2>,Expressions<2>,Topic Reference<2> -@anchor{cp/topics/functions doc}@anchor{1a2}@anchor{cp/topics/functions creating-and-using-functions}@anchor{1a3} +@anchor{cp/topics/functions doc}@anchor{1a3}@anchor{cp/topics/functions creating-and-using-functions}@anchor{1a4} @subsection Creating and using functions @@ -13869,36 +13884,36 @@ gccjit::lvalue element = array[0]; @end menu @node Params<2>,Functions<2>,,Creating and using functions<2> -@anchor{cp/topics/functions params}@anchor{1a4} +@anchor{cp/topics/functions params}@anchor{1a5} @subsubsection Params @geindex gccjit;;param (C++ class) -@anchor{cp/topics/functions gccjit param}@anchor{1a5} +@anchor{cp/topics/functions gccjit param}@anchor{1a6} @deffn {C++ Class} gccjit::param A @cite{gccjit::param} represents a parameter to a function. @end deffn @geindex gccjit;;context;;new_param (C++ function) -@anchor{cp/topics/functions gccjit context new_param__gccjit type cCP gccjit location}@anchor{10b} +@anchor{cp/topics/functions gccjit context new_param__gccjit type cCP gccjit location}@anchor{10c} @deffn {C++ Function} gccjit::param gccjit::context::new_param (gccjit::type type, const char* name, gccjit::location loc) In preparation for creating a function, create a new parameter of the given type and name. @end deffn -@pxref{1a5,,gccjit;;param} is a subclass of @pxref{197,,gccjit;;lvalue} (and thus -of @pxref{15f,,gccjit;;rvalue} and @pxref{149,,gccjit;;object}). It is a thin +@pxref{1a6,,gccjit;;param} is a subclass of @pxref{198,,gccjit;;lvalue} (and thus +of @pxref{160,,gccjit;;rvalue} and @pxref{14a,,gccjit;;object}). It is a thin wrapper around the C API's @pxref{25,,gcc_jit_param *}. @node Functions<2>,Blocks<2>,Params<2>,Creating and using functions<2> -@anchor{cp/topics/functions functions}@anchor{1a6} +@anchor{cp/topics/functions functions}@anchor{1a7} @subsubsection Functions @geindex gccjit;;function (C++ class) -@anchor{cp/topics/functions gccjit function}@anchor{1a7} +@anchor{cp/topics/functions gccjit function}@anchor{1a8} @deffn {C++ Class} gccjit::function A @cite{gccjit::function} represents a function - either one that we're @@ -13906,7 +13921,7 @@ creating ourselves, or one that we're referencing. @end deffn @geindex gccjit;;context;;new_function (C++ function) -@anchor{cp/topics/functions gccjit context new_function__enum gccjit type cCP std vector param R i gccjit location}@anchor{1a8} +@anchor{cp/topics/functions gccjit context new_function__enum gccjit type cCP std vector param R i gccjit location}@anchor{1a9} @deffn {C++ Function} gccjit::function gccjit::context::new_function (enum gcc_jit_function_kind, gccjit::type return_type, const char* name, std::vector& params, int is_variadic, gccjit::location loc) Create a gcc_jit_function with the given name and parameters. @@ -13917,29 +13932,29 @@ This is a wrapper around the C API's @pxref{11,,gcc_jit_context_new_function()}. @end deffn @geindex gccjit;;context;;get_builtin_function (C++ function) -@anchor{cp/topics/functions gccjit context get_builtin_function__cCP}@anchor{1a9} +@anchor{cp/topics/functions gccjit context get_builtin_function__cCP}@anchor{1aa} @deffn {C++ Function} gccjit::function gccjit::context::get_builtin_function (const char* name) This is a wrapper around the C API's -@pxref{cc,,gcc_jit_context_get_builtin_function()}. +@pxref{cd,,gcc_jit_context_get_builtin_function()}. @end deffn @geindex gccjit;;function;;get_param (C++ function) -@anchor{cp/topics/functions gccjit function get_param__iC}@anchor{1aa} +@anchor{cp/topics/functions gccjit function get_param__iC}@anchor{1ab} @deffn {C++ Function} gccjit::param gccjit::function::get_param (int index) const Get the param of the given index (0-based). @end deffn @geindex gccjit;;function;;dump_to_dot (C++ function) -@anchor{cp/topics/functions gccjit function dump_to_dot__cCP}@anchor{11e} +@anchor{cp/topics/functions gccjit function dump_to_dot__cCP}@anchor{11f} @deffn {C++ Function} void gccjit::function::dump_to_dot (const char* path) Emit the function in graphviz format to the given path. @end deffn @geindex gccjit;;function;;new_local (C++ function) -@anchor{cp/topics/functions gccjit function new_local__gccjit type cCP gccjit location}@anchor{115} +@anchor{cp/topics/functions gccjit function new_local__gccjit type cCP gccjit location}@anchor{116} @deffn {C++ Function} gccjit::lvalue gccjit::function::new_local (gccjit::type type, const char* name, gccjit::location loc) Create a new local variable within the function, of the given type and @@ -13947,19 +13962,19 @@ name. @end deffn @node Blocks<2>,Statements<2>,Functions<2>,Creating and using functions<2> -@anchor{cp/topics/functions blocks}@anchor{1ab} +@anchor{cp/topics/functions blocks}@anchor{1ac} @subsubsection Blocks @geindex gccjit;;block (C++ class) -@anchor{cp/topics/functions gccjit block}@anchor{1ac} +@anchor{cp/topics/functions gccjit block}@anchor{1ad} @deffn {C++ Class} gccjit::block A @cite{gccjit::block} represents a basic block within a function i.e. a sequence of statements with a single entry point and a single exit point. -@pxref{1ac,,gccjit;;block} is a subclass of @pxref{149,,gccjit;;object}. +@pxref{1ad,,gccjit;;block} is a subclass of @pxref{14a,,gccjit;;object}. The first basic block that you create within a function will be the entrypoint. @@ -13973,7 +13988,7 @@ one function. @end deffn @geindex gccjit;;function;;new_block (C++ function) -@anchor{cp/topics/functions gccjit function new_block__cCP}@anchor{1ad} +@anchor{cp/topics/functions gccjit function new_block__cCP}@anchor{1ae} @deffn {C++ Function} gccjit::block gccjit::function::new_block (const char* name) Create a basic block of the given name. The name may be NULL, but @@ -13983,12 +13998,12 @@ messages. @end deffn @node Statements<2>,,Blocks<2>,Creating and using functions<2> -@anchor{cp/topics/functions statements}@anchor{1ae} +@anchor{cp/topics/functions statements}@anchor{1af} @subsubsection Statements @geindex gccjit;;block;;add_eval (C++ function) -@anchor{cp/topics/functions gccjit block add_eval__gccjit rvalue gccjit location}@anchor{193} +@anchor{cp/topics/functions gccjit block add_eval__gccjit rvalue gccjit location}@anchor{194} @deffn {C++ Function} void gccjit::block::add_eval (gccjit::rvalue rvalue, gccjit::location loc) Add evaluation of an rvalue, discarding the result @@ -14004,7 +14019,7 @@ This is equivalent to this C code: @end deffn @geindex gccjit;;block;;add_assignment (C++ function) -@anchor{cp/topics/functions gccjit block add_assignment__gccjit lvalue gccjit rvalue gccjit location}@anchor{117} +@anchor{cp/topics/functions gccjit block add_assignment__gccjit lvalue gccjit rvalue gccjit location}@anchor{118} @deffn {C++ Function} void gccjit::block::add_assignment (gccjit::lvalue lvalue, gccjit::rvalue rvalue, gccjit::location loc) Add evaluation of an rvalue, assigning the result to the given @@ -14020,7 +14035,7 @@ lvalue = rvalue; @end deffn @geindex gccjit;;block;;add_assignment_op (C++ function) -@anchor{cp/topics/functions gccjit block add_assignment_op__gccjit lvalue enum gccjit rvalue gccjit location}@anchor{11b} +@anchor{cp/topics/functions gccjit block add_assignment_op__gccjit lvalue enum gccjit rvalue gccjit location}@anchor{11c} @deffn {C++ Function} void gccjit::block::add_assignment_op (gccjit::lvalue lvalue, enum gcc_jit_binary_op, gccjit::rvalue rvalue, gccjit::location loc) Add evaluation of an rvalue, using the result to modify an @@ -14050,7 +14065,7 @@ loop_body.add_assignment_op ( @end deffn @geindex gccjit;;block;;add_comment (C++ function) -@anchor{cp/topics/functions gccjit block add_comment__cCP gccjit location}@anchor{126} +@anchor{cp/topics/functions gccjit block add_comment__cCP gccjit location}@anchor{127} @deffn {C++ Function} void gccjit::block::add_comment (const char* text, gccjit::location loc) Add a no-op textual comment to the internal representation of the @@ -14064,7 +14079,7 @@ Parameter "loc" is optional. @end deffn @geindex gccjit;;block;;end_with_conditional (C++ function) -@anchor{cp/topics/functions gccjit block end_with_conditional__gccjit rvalue gccjit block gccjit block gccjit location}@anchor{11a} +@anchor{cp/topics/functions gccjit block end_with_conditional__gccjit rvalue gccjit block gccjit block gccjit location}@anchor{11b} @deffn {C++ Function} void gccjit::block::end_with_conditional (gccjit::rvalue boolval, gccjit::block on_true, gccjit::block on_false, gccjit::location loc) Terminate a block by adding evaluation of an rvalue, branching on the @@ -14085,7 +14100,7 @@ block, boolval, on_true, and on_false must be non-NULL. @end deffn @geindex gccjit;;block;;end_with_jump (C++ function) -@anchor{cp/topics/functions gccjit block end_with_jump__gccjit block gccjit location}@anchor{1af} +@anchor{cp/topics/functions gccjit block end_with_jump__gccjit block gccjit location}@anchor{1b0} @deffn {C++ Function} void gccjit::block::end_with_jump (gccjit::block target, gccjit::location loc) Terminate a block by adding a jump to the given target block. @@ -14100,7 +14115,7 @@ goto target; @end deffn @geindex gccjit;;block;;end_with_return (C++ function) -@anchor{cp/topics/functions gccjit block end_with_return__gccjit rvalue gccjit location}@anchor{1b0} +@anchor{cp/topics/functions gccjit block end_with_return__gccjit rvalue gccjit location}@anchor{1b1} @deffn {C++ Function} void gccjit::block::end_with_return (gccjit::rvalue rvalue, gccjit::location loc) Terminate a block. @@ -14134,7 +14149,7 @@ return; @end deffn @geindex gccjit;;block;;end_with_switch (C++ function) -@anchor{cp/topics/functions gccjit block end_with_switch__gccjit rvalue gccjit block std vector gccjit case_ gccjit location}@anchor{1b1} +@anchor{cp/topics/functions gccjit block end_with_switch__gccjit rvalue gccjit block std vector gccjit case_ gccjit location}@anchor{1b2} @deffn {C++ Function} void gccjit::block::end_with_switch (gccjit::rvalue expr, gccjit::block default_block, std::vector cases, gccjit::location loc) Terminate a block by adding evalation of an rvalue, then performing @@ -14177,14 +14192,14 @@ The API entrypoints relating to switch statements and cases: @itemize * @item -@pxref{1b1,,gccjit;;block;;end_with_switch()} +@pxref{1b2,,gccjit;;block;;end_with_switch()} @item -@pxref{1b2,,gccjit;;context;;new_case()} +@pxref{1b3,,gccjit;;context;;new_case()} @end itemize @end quotation -were added in @pxref{da,,LIBGCCJIT_ABI_3}; you can test for their presence +were added in @pxref{db,,LIBGCCJIT_ABI_3}; you can test for their presence using @example @@ -14194,21 +14209,21 @@ using @noindent @geindex gccjit;;block;;end_with_switch;;gccjit;;case_ (C++ class) -@anchor{cp/topics/functions gccjit block end_with_switch gccjit case_}@anchor{1b3} +@anchor{cp/topics/functions gccjit block end_with_switch gccjit case_}@anchor{1b4} @deffn {C++ Class} gccjit::case_ @end deffn A @cite{gccjit::case_} represents a case within a switch statement, and -is created within a particular @pxref{134,,gccjit;;context} using -@pxref{1b2,,gccjit;;context;;new_case()}. It is a subclass of -@pxref{149,,gccjit;;object}. +is created within a particular @pxref{135,,gccjit;;context} using +@pxref{1b3,,gccjit;;context;;new_case()}. It is a subclass of +@pxref{14a,,gccjit;;object}. Each case expresses a multivalued range of integer values. You can express single-valued cases by passing in the same value for both @cite{min_value} and @cite{max_value}. @geindex gccjit;;block;;end_with_switch;;gccjit;;context;;new_case (C++ function) -@anchor{cp/topics/functions gccjit block end_with_switch gccjit context new_case__gccjit rvalue gccjit rvalue gccjit block}@anchor{1b2} +@anchor{cp/topics/functions gccjit block end_with_switch gccjit context new_case__gccjit rvalue gccjit rvalue gccjit block}@anchor{1b3} @deffn {C++ Function} gccjit::case_* gccjit::context::new_case (gccjit::rvalue min_value, gccjit::rvalue max_value, gccjit::block dest_block) Create a new gccjit::case for use in a switch statement. @@ -14319,12 +14334,12 @@ create_code (gcc_jit_context *c_ctxt, void *user_data) @c . @node Source Locations<2>,Compiling a context<2>,Creating and using functions<2>,Topic Reference<2> -@anchor{cp/topics/locations source-locations}@anchor{1b4}@anchor{cp/topics/locations doc}@anchor{1b5} +@anchor{cp/topics/locations source-locations}@anchor{1b5}@anchor{cp/topics/locations doc}@anchor{1b6} @subsection Source Locations @geindex gccjit;;location (C++ class) -@anchor{cp/topics/locations gccjit location}@anchor{13c} +@anchor{cp/topics/locations gccjit location}@anchor{13d} @deffn {C++ Class} gccjit::location A @cite{gccjit::location} encapsulates a source code location, so that @@ -14335,10 +14350,10 @@ single-step through your language. @cite{gccjit::location} instances are optional: you can always omit them from any C++ API entrypoint accepting one. -You can construct them using @pxref{12a,,gccjit;;context;;new_location()}. +You can construct them using @pxref{12b,,gccjit;;context;;new_location()}. You need to enable @pxref{42,,GCC_JIT_BOOL_OPTION_DEBUGINFO} on the -@pxref{134,,gccjit;;context} for these locations to actually be usable by +@pxref{135,,gccjit;;context} for these locations to actually be usable by the debugger: @example @@ -14349,7 +14364,7 @@ ctxt.set_bool_option (GCC_JIT_BOOL_OPTION_DEBUGINFO, 1); @end deffn @geindex gccjit;;context;;new_location (C++ function) -@anchor{cp/topics/locations gccjit context new_location__cCP i i}@anchor{12a} +@anchor{cp/topics/locations gccjit context new_location__cCP i i}@anchor{12b} @deffn {C++ Function} gccjit::location gccjit::context::new_location (const char* filename, int line, int column) Create a @cite{gccjit::location} instance representing the given source @@ -14362,13 +14377,13 @@ location. @end menu @node Faking it<2>,,,Source Locations<2> -@anchor{cp/topics/locations faking-it}@anchor{1b6} +@anchor{cp/topics/locations faking-it}@anchor{1b7} @subsubsection Faking it If you don't have source code for your internal representation, but need to debug, you can generate a C-like representation of the functions in -your context using @pxref{13b,,gccjit;;context;;dump_to_file()}: +your context using @pxref{13c,,gccjit;;context;;dump_to_file()}: @example ctxt.dump_to_file ("/tmp/something.c", @@ -14400,13 +14415,13 @@ file, giving you @emph{something} you can step through in the debugger. @c . @node Compiling a context<2>,,Source Locations<2>,Topic Reference<2> -@anchor{cp/topics/compilation compiling-a-context}@anchor{1b7}@anchor{cp/topics/compilation doc}@anchor{1b8} +@anchor{cp/topics/compilation compiling-a-context}@anchor{1b8}@anchor{cp/topics/compilation doc}@anchor{1b9} @subsection Compiling a context -Once populated, a @pxref{134,,gccjit;;context} can be compiled to -machine code, either in-memory via @pxref{10d,,gccjit;;context;;compile()} or -to disk via @pxref{1b9,,gccjit;;context;;compile_to_file()}. +Once populated, a @pxref{135,,gccjit;;context} can be compiled to +machine code, either in-memory via @pxref{10e,,gccjit;;context;;compile()} or +to disk via @pxref{1ba,,gccjit;;context;;compile_to_file()}. You can compile a context multiple times (using either form of compilation), although any errors that occur on the context will @@ -14419,12 +14434,12 @@ prevent any future compilation of that context. @end menu @node In-memory compilation<2>,Ahead-of-time compilation<2>,,Compiling a context<2> -@anchor{cp/topics/compilation in-memory-compilation}@anchor{1ba} +@anchor{cp/topics/compilation in-memory-compilation}@anchor{1bb} @subsubsection In-memory compilation @geindex gccjit;;context;;compile (C++ function) -@anchor{cp/topics/compilation gccjit context compile}@anchor{10d} +@anchor{cp/topics/compilation gccjit context compile}@anchor{10e} @deffn {C++ Function} gcc_jit_result* gccjit::context::compile () This calls into GCC and builds the code, returning a @@ -14435,19 +14450,19 @@ This is a thin wrapper around the @end deffn @node Ahead-of-time compilation<2>,,In-memory compilation<2>,Compiling a context<2> -@anchor{cp/topics/compilation ahead-of-time-compilation}@anchor{1bb} +@anchor{cp/topics/compilation ahead-of-time-compilation}@anchor{1bc} @subsubsection Ahead-of-time compilation Although libgccjit is primarily aimed at just-in-time compilation, it can also be used for implementing more traditional ahead-of-time -compilers, via the @pxref{1b9,,gccjit;;context;;compile_to_file()} method. +compilers, via the @pxref{1ba,,gccjit;;context;;compile_to_file()} method. @geindex gccjit;;context;;compile_to_file (C++ function) -@anchor{cp/topics/compilation gccjit context compile_to_file__enum cCP}@anchor{1b9} +@anchor{cp/topics/compilation gccjit context compile_to_file__enum cCP}@anchor{1ba} @deffn {C++ Function} void gccjit::context::compile_to_file (enum gcc_jit_output_kind, const char* output_path) -Compile the @pxref{134,,gccjit;;context} to a file of the given +Compile the @pxref{135,,gccjit;;context} to a file of the given kind. This is a thin wrapper around the @@ -14472,7 +14487,7 @@ This is a thin wrapper around the @c . @node Internals,Indices and tables,C++ bindings for libgccjit,Top -@anchor{internals/index internals}@anchor{1bc}@anchor{internals/index doc}@anchor{1bd} +@anchor{internals/index internals}@anchor{1bd}@anchor{internals/index doc}@anchor{1be} @chapter Internals @@ -14488,7 +14503,7 @@ This is a thin wrapper around the @end menu @node Working on the JIT library,Running the test suite,,Internals -@anchor{internals/index working-on-the-jit-library}@anchor{1be} +@anchor{internals/index working-on-the-jit-library}@anchor{1bf} @section Working on the JIT library @@ -14525,7 +14540,7 @@ gcc/libgccjit.so.0.0.1: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), Here's what those configuration options mean: @geindex command line option; --enable-host-shared -@anchor{internals/index cmdoption--enable-host-shared}@anchor{1bf} +@anchor{internals/index cmdoption--enable-host-shared}@anchor{1c0} @deffn {Option} --enable-host-shared Configuring with this option means that the compiler is built as @@ -14534,7 +14549,7 @@ but it necessary for a shared library. @end deffn @geindex command line option; --enable-languages=jit@comma{}c++ -@anchor{internals/index cmdoption--enable-languages}@anchor{1c0} +@anchor{internals/index cmdoption--enable-languages}@anchor{1c1} @deffn {Option} --enable-languages=jit,c++ This specifies which frontends to build. The JIT library looks like @@ -14553,7 +14568,7 @@ c++: error trying to exec 'cc1plus': execvp: No such file or directory @end deffn @geindex command line option; --disable-bootstrap -@anchor{internals/index cmdoption--disable-bootstrap}@anchor{1c1} +@anchor{internals/index cmdoption--disable-bootstrap}@anchor{1c2} @deffn {Option} --disable-bootstrap For hacking on the "jit" subdirectory, performing a full @@ -14563,7 +14578,7 @@ the compiler can still bootstrap itself. @end deffn @geindex command line option; --enable-checking=release -@anchor{internals/index cmdoption--enable-checking}@anchor{1c2} +@anchor{internals/index cmdoption--enable-checking}@anchor{1c3} @deffn {Option} --enable-checking=release The compile can perform extensive self-checking as it runs, useful when @@ -14574,7 +14589,7 @@ disable this self-checking. @end deffn @node Running the test suite,Environment variables,Working on the JIT library,Internals -@anchor{internals/index running-the-test-suite}@anchor{1c3} +@anchor{internals/index running-the-test-suite}@anchor{1c4} @section Running the test suite @@ -14637,7 +14652,7 @@ and once a test has been compiled, you can debug it directly: @end menu @node Running under valgrind,,,Running the test suite -@anchor{internals/index running-under-valgrind}@anchor{1c4} +@anchor{internals/index running-under-valgrind}@anchor{1c5} @subsection Running under valgrind @@ -14685,7 +14700,7 @@ When running under valgrind, it's best to have configured gcc with various known false positives. @node Environment variables,Packaging notes,Running the test suite,Internals -@anchor{internals/index environment-variables}@anchor{1c5} +@anchor{internals/index environment-variables}@anchor{1c6} @section Environment variables @@ -14693,7 +14708,7 @@ When running client code against a locally-built libgccjit, three environment variables need to be set up: @geindex environment variable; LD_LIBRARY_PATH -@anchor{internals/index envvar-LD_LIBRARY_PATH}@anchor{1c6} +@anchor{internals/index envvar-LD_LIBRARY_PATH}@anchor{1c7} @deffn {Environment Variable} LD_LIBRARY_PATH @quotation @@ -14715,7 +14730,7 @@ libgccjit.so.0.0.1: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), @end deffn @geindex environment variable; PATH -@anchor{internals/index envvar-PATH}@anchor{1c7} +@anchor{internals/index envvar-PATH}@anchor{1c8} @deffn {Environment Variable} PATH The library uses a driver executable for converting from .s assembler @@ -14734,7 +14749,7 @@ of development. @end deffn @geindex environment variable; LIBRARY_PATH -@anchor{internals/index envvar-LIBRARY_PATH}@anchor{1c8} +@anchor{internals/index envvar-LIBRARY_PATH}@anchor{1c9} @deffn {Environment Variable} LIBRARY_PATH The driver executable invokes the linker, and the latter needs to locate @@ -14770,11 +14785,11 @@ hello world @noindent @node Packaging notes,Overview of code structure,Environment variables,Internals -@anchor{internals/index packaging-notes}@anchor{1c9} +@anchor{internals/index packaging-notes}@anchor{1ca} @section Packaging notes -The configure-time option @pxref{1bf,,--enable-host-shared} is needed when +The configure-time option @pxref{1c0,,--enable-host-shared} is needed when building the jit in order to get position-independent code. This will slow down the regular compiler by a few percent. Hence when packaging gcc with libgccjit, please configure and build twice: @@ -14785,10 +14800,10 @@ with libgccjit, please configure and build twice: @itemize * @item -once without @pxref{1bf,,--enable-host-shared} for most languages, and +once without @pxref{1c0,,--enable-host-shared} for most languages, and @item -once with @pxref{1bf,,--enable-host-shared} for the jit +once with @pxref{1c0,,--enable-host-shared} for the jit @end itemize @end quotation @@ -14832,7 +14847,7 @@ popd @noindent @node Overview of code structure,Design notes,Packaging notes,Internals -@anchor{internals/index overview-of-code-structure}@anchor{1ca} +@anchor{internals/index overview-of-code-structure}@anchor{1cb} @section Overview of code structure @@ -15307,7 +15322,7 @@ JIT: gcc::jit::logger::~logger() @noindent @node Design notes,Submitting patches,Overview of code structure,Internals -@anchor{internals/index design-notes}@anchor{1cb} +@anchor{internals/index design-notes}@anchor{1cc} @section Design notes @@ -15320,7 +15335,7 @@ close as possible to the error; failing that, a good place is within @code{recording::context::validate ()} in jit-recording.c. @node Submitting patches,,Design notes,Internals -@anchor{internals/index submitting-patches}@anchor{1cc} +@anchor{internals/index submitting-patches}@anchor{1cd} @section Submitting patches @@ -15454,7 +15469,7 @@ large and inconsequential (e.g. anchor renumbering), rather like generated committing to svn. @node Indices and tables,Index,Internals,Top -@anchor{index indices-and-tables}@anchor{1cd} +@anchor{index indices-and-tables}@anchor{1ce} @unnumbered Indices and tables diff --git a/gcc/jit/docs/topics/expressions.rst b/gcc/jit/docs/topics/expressions.rst index cb65c43838a..04453321b9c 100644 --- a/gcc/jit/docs/topics/expressions.rst +++ b/gcc/jit/docs/topics/expressions.rst @@ -409,6 +409,22 @@ Function calls printf_func, 2, args)); +.. function:: gcc_jit_rvalue *\ + gcc_jit_context_new_call_through_ptr (gcc_jit_context *ctxt,\ + gcc_jit_location *loc,\ + gcc_jit_rvalue *fn_ptr,\ + int numargs, \ + gcc_jit_rvalue **args) + + Given an rvalue of function pointer type, and the given table of + argument rvalues, construct a call to the function pointer, with the + result as an rvalue. + + .. note:: + + The same caveat as for :c:func:`gcc_jit_context_new_call` applies. + + Type-coercion ************* -- 2.30.2