public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: sync latest changes
Date: Tue,  8 Nov 2022 10:21:44 +0000 (GMT)	[thread overview]
Message-ID: <20221108102144.4F2A53858C3A@sourceware.org> (raw)

https://gcc.gnu.org/g:d72e0abd5a025a69cf813fa307a3546c61cf1712

commit d72e0abd5a025a69cf813fa307a3546c61cf1712
Author: Martin Liska <mliska@suse.cz>
Date:   Mon Nov 7 22:18:24 2022 +0100

    sphinx: sync latest changes
    
    gcc/ChangeLog:
    
            * doc/gccint/target-macros/stack-layout-and-calling-conventions/passing-arguments-in-registers.rst:
            Port to RST.
            * doc/gccint/target-macros/storage-layout.rst: Likewise.

Diff:
---
 .../passing-arguments-in-registers.rst                              | 2 +-
 gcc/doc/gccint/target-macros/storage-layout.rst                     | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/gcc/doc/gccint/target-macros/stack-layout-and-calling-conventions/passing-arguments-in-registers.rst b/gcc/doc/gccint/target-macros/stack-layout-and-calling-conventions/passing-arguments-in-registers.rst
index 6ece8a4577b..8fce5c3403a 100644
--- a/gcc/doc/gccint/target-macros/stack-layout-and-calling-conventions/passing-arguments-in-registers.rst
+++ b/gcc/doc/gccint/target-macros/stack-layout-and-calling-conventions/passing-arguments-in-registers.rst
@@ -118,7 +118,7 @@ the stack.
   argument :samp:`{libname}` exists for symmetry with
   ``INIT_CUMULATIVE_ARGS``.
 
-  .. could use "this macro" in place of @code{INIT_CUMULATIVE_ARGS}, maybe.
+  .. could use "this macro" in place of ``INIT_CUMULATIVE_ARGS``, maybe.
 
   .. -mew 5feb93   i switched the order of the sentences.  -mew 10feb93
 
diff --git a/gcc/doc/gccint/target-macros/storage-layout.rst b/gcc/doc/gccint/target-macros/storage-layout.rst
index bcdc87eecd0..7e6b1c978f6 100644
--- a/gcc/doc/gccint/target-macros/storage-layout.rst
+++ b/gcc/doc/gccint/target-macros/storage-layout.rst
@@ -217,10 +217,10 @@ See :ref:`run-time-target`.
 
   If not defined, the default value is ``STACK_BOUNDARY``.
 
-  .. todo:: The default should be @code{PREFERRED_STACK_BOUNDARY}.
+  .. todo:: The default should be ``PREFERRED_STACK_BOUNDARY``.
     But the fix for PR 32893 indicates that we can only guarantee
-    maximum stack alignment on stack up to @code{STACK_BOUNDARY}, not
-    @code{PREFERRED_STACK_BOUNDARY}, if stack alignment isn't supported.
+    maximum stack alignment on stack up to ``STACK_BOUNDARY``, not
+    ``PREFERRED_STACK_BOUNDARY``, if stack alignment isn't supported.
 
 .. c:macro:: MAX_OFILE_ALIGNMENT

             reply	other threads:[~2022-11-08 10:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 10:21 Martin Liska [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-08 14:53 Martin Liska
2022-11-08 14:43 Martin Liska
2022-11-08 14:36 Martin Liska
2022-11-08 14:35 Martin Liska
2022-11-08 12:07 Martin Liska
2022-11-08 11:43 Martin Liska
2022-11-08 11:39 Martin Liska
2022-11-07 21:18 Martin Liska

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=20221108102144.4F2A53858C3A@sourceware.org \
    --to=marxin@gcc.gnu.org \
    --cc=gcc-cvs@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).