From: David Malcolm <dmalcolm@redhat.com>
To: gcc-patches@gcc.gnu.org, jit@gcc.gnu.org
Subject: [committed] jit: fix sphinx formatting issues in docs
Date: Tue, 26 May 2020 11:09:30 -0400 [thread overview]
Message-ID: <20200526150930.5295-1-dmalcolm@redhat.com> (raw)
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to master as 0981cf960d07752f9844a2f2799fbc85a7f1efd8.
gcc/jit/ChangeLog:
* docs/topics/compatibility.rst: Fix underline.
Fix missing labels.
* docs/topics/types.rst: Fix missing blank line.
* docs/_build/texinfo/Makefile: Regenerate.
* docs/_build/texinfo/libgccjit.texi: Regenerate.
---
gcc/jit/docs/topics/compatibility.rst | 6 +++++-
gcc/jit/docs/topics/types.rst | 1 +
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/gcc/jit/docs/topics/compatibility.rst b/gcc/jit/docs/topics/compatibility.rst
index 0c0ce070d72..bb3387fa583 100644
--- a/gcc/jit/docs/topics/compatibility.rst
+++ b/gcc/jit/docs/topics/compatibility.rst
@@ -62,7 +62,7 @@ You can see the symbol tags provided by libgccjit.so using ``objdump``:
[...snip...]
Programmatically checking version
-***************
+*********************************
Client code can programmatically check libgccjit version using:
@@ -200,11 +200,15 @@ entrypoints:
``LIBGCCJIT_ABI_11`` covers the addition of
:func:`gcc_jit_context_add_driver_option`
+.. _LIBGCCJIT_ABI_12:
+
``LIBGCCJIT_ABI_12``
--------------------
``LIBGCCJIT_ABI_12`` covers the addition of
:func:`gcc_jit_context_new_bitfield`
+.. _LIBGCCJIT_ABI_13:
+
``LIBGCCJIT_ABI_13``
--------------------
``LIBGCCJIT_ABI_13`` covers the addition of version functions via API
diff --git a/gcc/jit/docs/topics/types.rst b/gcc/jit/docs/topics/types.rst
index ea7c8ff4542..e508a6bed0d 100644
--- a/gcc/jit/docs/topics/types.rst
+++ b/gcc/jit/docs/topics/types.rst
@@ -269,6 +269,7 @@ You can model C `struct` types by creating :c:type:`gcc_jit_struct *` and
This API entrypoint was added in :ref:`LIBGCCJIT_ABI_12`; you can test
for its presence using
+
.. code-block:: c
#ifdef LIBGCCJIT_HAVE_gcc_jit_context_new_bitfield
--
2.21.0
reply other threads:[~2020-05-26 15:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200526150930.5295-1-dmalcolm@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jit@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).