public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Liska <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH 0/7] jit,docs: remove warnings and modernize the docs
Date: Mon, 25 Jul 2022 15:13:08 +0200	[thread overview]
Message-ID: <cover.1658754788.git.mliska@suse.cz> (raw)

The patch set modernizes the documentation and removes most of the reported Sphinx
warnings.

Ready for master?
Thanks,
Martin

Martin Liska (7):
  jit,docs: use enum directive for enumeral types
  jit,docs: replace c:type:`int_type` with :expr:`int_type`
  jit,docs: various fixes
  jit,docs: compact function declarations
  jit,docs: use list-table instead of fixed table
  jit,docs: use :expr:`type *` for pointers to a type
  jit,docs: remove :ref:`modindex`

 gcc/jit/docs/conf.py                      |   3 +
 gcc/jit/docs/cp/intro/tutorial02.rst      |   6 +-
 gcc/jit/docs/cp/intro/tutorial04.rst      |  73 +++++++++-----
 gcc/jit/docs/cp/topics/asm.rst            |   2 +-
 gcc/jit/docs/cp/topics/contexts.rst       |   8 +-
 gcc/jit/docs/cp/topics/expressions.rst    |  52 ++++------
 gcc/jit/docs/cp/topics/functions.rst      |  48 +++++-----
 gcc/jit/docs/cp/topics/objects.rst        |   2 +-
 gcc/jit/docs/cp/topics/types.rst          |   2 +-
 gcc/jit/docs/examples/tut04-toyvm/toyvm.c |   1 +
 gcc/jit/docs/index.rst                    |   8 --
 gcc/jit/docs/intro/tutorial02.rst         |  16 ++--
 gcc/jit/docs/intro/tutorial03.rst         |  28 +++---
 gcc/jit/docs/intro/tutorial04.rst         |  77 ++++++++++-----
 gcc/jit/docs/intro/tutorial05.rst         |  41 +++++---
 gcc/jit/docs/topics/compilation.rst       |  38 ++++----
 gcc/jit/docs/topics/contexts.rst          |  12 +--
 gcc/jit/docs/topics/expressions.rst       | 111 ++++++++++++++--------
 gcc/jit/docs/topics/function-pointers.rst |   2 +-
 gcc/jit/docs/topics/functions.rst         |   2 +-
 gcc/jit/docs/topics/objects.rst           |   6 +-
 gcc/jit/docs/topics/types.rst             | 111 ++++++++++++++--------
 22 files changed, 379 insertions(+), 270 deletions(-)

-- 
2.37.1


             reply	other threads:[~2022-07-25 13:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 13:13 Martin Liska [this message]
2022-07-25  8:52 ` [PATCH 1/7] jit,docs: use enum directive for enumeral types Martin Liska
2022-07-25 22:35   ` David Malcolm
2022-07-26  4:47     ` Martin Liška
2022-07-25  9:03 ` [PATCH 2/7] jit, docs: replace c:type:`int_type` with :expr:`int_type` Martin Liska
2022-07-25 22:37   ` [PATCH 2/7] jit,docs: " David Malcolm
2022-07-26  4:48     ` Martin Liška
2022-07-26 15:42       ` David Malcolm
2022-07-25  9:15 ` [PATCH 3/7] jit,docs: various fixes Martin Liska
2022-07-25 22:39   ` David Malcolm
2022-07-25  9:51 ` [PATCH 4/7] jit,docs: compact function declarations Martin Liska
2022-07-25 22:39   ` David Malcolm
2022-07-25 10:35 ` [PATCH 5/7] jit,docs: use list-table instead of fixed table Martin Liska
2022-07-25 22:40   ` David Malcolm
2022-07-25 12:39 ` [PATCH 6/7] jit,docs: use :expr:`type *` for pointers to a type Martin Liska
2022-07-25 22:41   ` David Malcolm
2022-07-26  4:50     ` Martin Liška
2022-07-26 15:43       ` David Malcolm
2022-07-26  4:55 ` [PATCH 7/7] jit,docs: remove :ref:`modindex` Martin Liška
2022-07-26 15:44   ` David Malcolm

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=cover.1658754788.git.mliska@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@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).