# The master toctree document.
master_doc = 'index'
+# c:type directive is supported since 3.0
+needs_sphinx = '3.0'
+
# General information about the project.
project = u'libgccjit'
copyright = u'2014-2022 Free Software Foundation, Inc.'
* :ref:`genindex`
* :ref:`modindex`
* :ref:`search`
-
-.. Some notes:
-
- The Sphinx C domain appears to lack explicit support for enum values,
- so I've been using :c:macro: for them.
-
- See https://sphinx-doc.org/domains.html#the-c-domain
:c:func:`gcc_jit_context_compile_to_file` ignores the suffix of
``output_path``, and insteads uses the given
-:c:type:`enum gcc_jit_output_kind` to decide what to do.
+:c:enum:`gcc_jit_output_kind` to decide what to do.
.. note::
This is different from the ``gcc`` program, which does make use of the
suffix of the output file when determining what to do.
-.. type:: enum gcc_jit_output_kind
+.. enum:: gcc_jit_output_kind
The available kinds of output are:
Set a string option of the context.
- .. type:: enum gcc_jit_str_option
+ .. enum:: gcc_jit_str_option
The parameter ``value`` can be NULL. If non-NULL, the call takes a
copy of the underlying string, so it is valid to pass in a pointer to
Set a boolean option of the context.
Zero is "false" (the default), non-zero is "true".
- .. type:: enum gcc_jit_bool_option
+ .. enum:: gcc_jit_bool_option
.. macro:: GCC_JIT_BOOL_OPTION_DEBUGINFO
Set an integer option of the context.
- .. type:: enum gcc_jit_int_option
+ .. enum:: gcc_jit_int_option
There is just one integer option specified this way:
The parameter ``result_type`` must be a numeric type.
-.. type:: enum gcc_jit_unary_op
+.. enum:: gcc_jit_unary_op
The available unary operations are:
The parameter ``result_type`` must be a numeric type.
-.. type:: enum gcc_jit_binary_op
+.. enum:: gcc_jit_binary_op
The available binary operations are:
Build a boolean rvalue out of the comparison of two other rvalues.
-.. type:: enum gcc_jit_comparison
+.. enum:: gcc_jit_comparison
======================================= ============
Comparison C equivalent
The "model" parameter determines the thread-local storage model of the "lvalue":
- .. type:: enum gcc_jit_tls_model
+ .. enum:: gcc_jit_tls_model
.. c:macro:: GCC_JIT_TLS_MODEL_NONE
The "kind" parameter determines the visibility of the "global" outside
of the :c:type:`gcc_jit_result`:
- .. type:: enum gcc_jit_global_kind
+ .. enum:: gcc_jit_global_kind
.. c:macro:: GCC_JIT_GLOBAL_EXPORTED
Create a gcc_jit_function with the given name and parameters.
- .. type:: enum gcc_jit_function_kind
+ .. enum:: gcc_jit_function_kind
This enum controls the kind of function created, and has the following
values: