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: fix cross manual references Date: Tue, 8 Nov 2022 14:36:20 +0000 (GMT) [thread overview] Message-ID: <20221108143620.6EF6A3858433@sourceware.org> (raw) https://gcc.gnu.org/g:c4f43e485ee00fbb9319b9d7e83dbdd7af6c7282 commit c4f43e485ee00fbb9319b9d7e83dbdd7af6c7282 Author: Martin Liska <mliska@suse.cz> Date: Thu Jul 28 02:09:54 2022 +0200 sphinx: fix cross manual references gcc/ada/ChangeLog: * doc/gnat_rm/index.rst: Fix cross manual refs. gcc/ChangeLog: * doc/gcc/gcc-command-options/options-controlling-the-kind-of-output.rst: Fix cross manual refs. * doc/gcc/language-standards-supported-by-gcc/references-for-other-languages.rst: Likewise. gcc/jit/ChangeLog: * doc/internals/index.rst: Fix cross manual refs. * doc/topics/contexts.rst: Likewise. Diff: --- gcc/ada/doc/gnat_rm/index.rst | 3 ++- .../gcc-command-options/options-controlling-the-kind-of-output.rst | 2 +- .../references-for-other-languages.rst | 2 +- gcc/jit/doc/internals/index.rst | 2 +- gcc/jit/doc/topics/contexts.rst | 4 ++-- 5 files changed, 7 insertions(+), 6 deletions(-) diff --git a/gcc/ada/doc/gnat_rm/index.rst b/gcc/ada/doc/gnat_rm/index.rst index 6c2616a0f1c..372c2100e51 100644 --- a/gcc/ada/doc/gnat_rm/index.rst +++ b/gcc/ada/doc/gnat_rm/index.rst @@ -1,6 +1,7 @@ +.. _top: + GNAT Reference Manual ===================== - .. only:: not latex *GNAT, The GNU Ada Development Environment* diff --git a/gcc/doc/gcc/gcc-command-options/options-controlling-the-kind-of-output.rst b/gcc/doc/gcc/gcc-command-options/options-controlling-the-kind-of-output.rst index 61420c1c395..ea9e3cfc168 100644 --- a/gcc/doc/gcc/gcc-command-options/options-controlling-the-kind-of-output.rst +++ b/gcc/doc/gcc/gcc-command-options/options-controlling-the-kind-of-output.rst @@ -700,7 +700,7 @@ one of the options :option:`-c`, :option:`-S`, or :option:`-E` to say where .. option:: -fdump-ada-spec[-slim] For C and C++ source and include files, generate corresponding Ada specs. - See :ref:`gnat_ugn:generating-ada-bindings-for-c-and-c++-headers`, which provides detailed documentation on this feature. + See :ref:`gnat_ugn:Generating_Ada_Bindings_for_C_and_C++_headers`, which provides detailed documentation on this feature. .. option:: -fada-spec-parent={unit} diff --git a/gcc/doc/gcc/language-standards-supported-by-gcc/references-for-other-languages.rst b/gcc/doc/gcc/language-standards-supported-by-gcc/references-for-other-languages.rst index 001116ac260..b74c27e0fff 100644 --- a/gcc/doc/gcc/language-standards-supported-by-gcc/references-for-other-languages.rst +++ b/gcc/doc/gcc/language-standards-supported-by-gcc/references-for-other-languages.rst @@ -10,4 +10,4 @@ See :ref:`gnat_rm:top`, for information on standard conformance and compatibility of the Ada compiler. See :ref:`gfortran:standards`, for details -of standards supported by GNU Fortran. \ No newline at end of file +of standards supported by GNU Fortran. diff --git a/gcc/jit/doc/internals/index.rst b/gcc/jit/doc/internals/index.rst index 092380c8f20..7ca45310ffe 100644 --- a/gcc/jit/doc/internals/index.rst +++ b/gcc/jit/doc/internals/index.rst @@ -173,7 +173,7 @@ For example, the following invocation verbosely runs the testcase (...shows full valgrind report for this test case...) When running under valgrind, it's best to have configured gcc with -:option:`--enable-valgrind-annotations`, which automatically suppresses +:option:`install:--enable-valgrind-annotations`, which automatically suppresses various known false positives. Environment variables diff --git a/gcc/jit/doc/topics/contexts.rst b/gcc/jit/doc/topics/contexts.rst index b1a7a0af56f..0a079976f53 100644 --- a/gcc/jit/doc/topics/contexts.rst +++ b/gcc/jit/doc/topics/contexts.rst @@ -237,7 +237,7 @@ future activies on a context to the given `FILE *`. a much simpler executable that performs the equivalent calls into libgccjit, without needing the client code and its data. - Typically you need to supply :option:`-Wno-unused-variable` when + Typically you need to supply :option:`gcc:-Wno-unused-variable` when compiling the generated file (since the result of each API call is assigned to a unique variable within the generated C source, and not all are necessarily then used). @@ -252,7 +252,7 @@ future activies on a context to the given `FILE *`. Parameter "dumpname" corresponds to the equivalent gcc command-line option, without the "-fdump-" prefix. - For example, to get the equivalent of :option:`-fdump-tree-vrp1`, + For example, to get the equivalent of :option:`-fdump-tree-vrp <gcc:-fdump-tree-all>`, supply ``"tree-vrp1"``: .. code-block:: c
next reply other threads:[~2022-11-08 14:36 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-08 14:36 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:35 Martin Liska 2022-11-08 12:06 Martin Liska 2022-11-08 11:39 Martin Liska 2022-11-08 10:21 Martin Liska 2022-11-07 14:34 Martin Liska 2022-11-07 14:19 Martin Liska 2022-11-07 14:10 Martin Liska 2022-11-07 14:09 Martin Liska 2022-11-07 14:07 Martin Liska 2022-11-07 13:20 Martin Liska 2022-11-07 13:01 Martin Liska 2022-11-07 12:38 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=20221108143620.6EF6A3858433@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: linkBe 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).