[gcc(refs/users/marxin/heads/sphinx-v1)] Temporary fixes for include warnings.
Martin Liska
marxin@gcc.gnu.org
Tue Jun 22 14:54:51 GMT 2021
https://gcc.gnu.org/g:3a3675435914e6b1f416489b13c4c2be5b21a424
commit 3a3675435914e6b1f416489b13c4c2be5b21a424
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jun 22 16:33:59 2021 +0200
Temporary fixes for include warnings.
Diff:
---
.../controlling-debugging-information-format.rst | 12 ++--
.../assembler-commands-for-exception-regions.rst | 52 +++++++++---------
.../the-overall-framework-of-an-assembler-file.rst | 4 +-
.../run-time-target-specification.rst | 64 +++++++++++-----------
4 files changed, 66 insertions(+), 66 deletions(-)
diff --git a/gcc/doc/gccint/target-description-macros-and-functions/controlling-debugging-information-format.rst b/gcc/doc/gccint/target-description-macros-and-functions/controlling-debugging-information-format.rst
index 2d7b47a97e8..99b8dd40d9c 100644
--- a/gcc/doc/gccint/target-description-macros-and-functions/controlling-debugging-information-format.rst
+++ b/gcc/doc/gccint/target-description-macros-and-functions/controlling-debugging-information-format.rst
@@ -320,11 +320,11 @@ Here are macros for DWARF output.
:end-before: [TARGET_DWARF_CALLING_CONVENTION]
- To support optional call frame debugging information, you must also
- define ``INCOMING_RETURN_ADDR_RTX`` and either set
- ``RTX_FRAME_RELATED_P`` on the prologue insns if you use RTL for the
- prologue, or call ``dwarf2out_def_cfa`` and ``dwarf2out_reg_save``
- as appropriate from ``TARGET_ASM_FUNCTION_PROLOGUE`` if you don't.
+To support optional call frame debugging information, you must also
+define ``INCOMING_RETURN_ADDR_RTX`` and either set
+``RTX_FRAME_RELATED_P`` on the prologue insns if you use RTL for the
+prologue, or call ``dwarf2out_def_cfa`` and ``dwarf2out_reg_save``
+as appropriate from ``TARGET_ASM_FUNCTION_PROLOGUE`` if you don't.
.. c:macro:: DWARF2_FRAME_INFO
@@ -433,4 +433,4 @@ Here are macros for VMS debug format.
is to generate minimal debug info for a traceback in the absence of
:option:`-g` unless explicitly overridden with :option:`-g0`. This
behavior is controlled by ``TARGET_OPTION_OPTIMIZATION`` and
- ``TARGET_OPTION_OVERRIDE``.
\ No newline at end of file
+ ``TARGET_OPTION_OVERRIDE``.
diff --git a/gcc/doc/gccint/target-description-macros-and-functions/defining-the-output-assembler-language/assembler-commands-for-exception-regions.rst b/gcc/doc/gccint/target-description-macros-and-functions/defining-the-output-assembler-language/assembler-commands-for-exception-regions.rst
index 230f49ad8a9..733eec92459 100644
--- a/gcc/doc/gccint/target-description-macros-and-functions/defining-the-output-assembler-language/assembler-commands-for-exception-regions.rst
+++ b/gcc/doc/gccint/target-description-macros-and-functions/defining-the-output-assembler-language/assembler-commands-for-exception-regions.rst
@@ -59,38 +59,38 @@ region.
:end-before: [TARGET_EXCEPT_UNWIND_INFO]
- This hook defines the mechanism that will be used for exception handling
- by the target. If the target has ABI specified unwind tables, the hook
- should return ``UI_TARGET``. If the target is to use the
- ``setjmp`` / ``longjmp`` -based exception handling scheme, the hook
- should return ``UI_SJLJ``. If the target supports DWARF 2 frame unwind
- information, the hook should return ``UI_DWARF2``.
-
- A target may, if exceptions are disabled, choose to return ``UI_NONE``.
- This may end up simplifying other parts of target-specific code. The
- default implementation of this hook never returns ``UI_NONE``.
-
- Note that the value returned by this hook should be constant. It should
- not depend on anything except the command-line switches described by
- :samp:`{opts}`. In particular, the
- setting ``UI_SJLJ`` must be fixed at compiler start-up as C pre-processor
- macros and builtin functions related to exception handling are set up
- depending on this setting.
-
- The default implementation of the hook first honors the
- :option:`--enable-sjlj-exceptions` configure option, then
- ``DWARF2_UNWIND_INFO``, and finally defaults to ``UI_SJLJ``. If
- ``DWARF2_UNWIND_INFO`` depends on command-line options, the target
- must define this hook so that :samp:`{opts}` is used correctly.
+This hook defines the mechanism that will be used for exception handling
+by the target. If the target has ABI specified unwind tables, the hook
+should return ``UI_TARGET``. If the target is to use the
+``setjmp`` / ``longjmp`` -based exception handling scheme, the hook
+should return ``UI_SJLJ``. If the target supports DWARF 2 frame unwind
+information, the hook should return ``UI_DWARF2``.
+
+A target may, if exceptions are disabled, choose to return ``UI_NONE``.
+This may end up simplifying other parts of target-specific code. The
+default implementation of this hook never returns ``UI_NONE``.
+
+Note that the value returned by this hook should be constant. It should
+not depend on anything except the command-line switches described by
+:samp:`{opts}`. In particular, the
+setting ``UI_SJLJ`` must be fixed at compiler start-up as C pre-processor
+macros and builtin functions related to exception handling are set up
+depending on this setting.
+
+The default implementation of the hook first honors the
+:option:`--enable-sjlj-exceptions` configure option, then
+``DWARF2_UNWIND_INFO``, and finally defaults to ``UI_SJLJ``. If
+``DWARF2_UNWIND_INFO`` depends on command-line options, the target
+must define this hook so that :samp:`{opts}` is used correctly.
.. include:: ../tm.rst.in
:start-after: [TARGET_UNWIND_TABLES_DEFAULT]
:end-before: [TARGET_UNWIND_TABLES_DEFAULT]
- This variable should be set to ``true`` if the target ABI requires unwinding
- tables even when exceptions are not used. It must not be modified by
- command-line option processing.
+This variable should be set to ``true`` if the target ABI requires unwinding
+tables even when exceptions are not used. It must not be modified by
+command-line option processing.
.. c:macro:: DONT_USE_BUILTIN_SETJMP
diff --git a/gcc/doc/gccint/target-description-macros-and-functions/defining-the-output-assembler-language/the-overall-framework-of-an-assembler-file.rst b/gcc/doc/gccint/target-description-macros-and-functions/defining-the-output-assembler-language/the-overall-framework-of-an-assembler-file.rst
index 712a80c0afd..5ab55abe972 100644
--- a/gcc/doc/gccint/target-description-macros-and-functions/defining-the-output-assembler-language/the-overall-framework-of-an-assembler-file.rst
+++ b/gcc/doc/gccint/target-description-macros-and-functions/defining-the-output-assembler-language/the-overall-framework-of-an-assembler-file.rst
@@ -135,8 +135,8 @@ This describes the overall framework of an assembly file.
:end-before: [TARGET_HAVE_NAMED_SECTIONS]
- This flag is true if the target supports ``TARGET_ASM_NAMED_SECTION``.
- It must not be modified by command-line option processing.
+This flag is true if the target supports ``TARGET_ASM_NAMED_SECTION``.
+It must not be modified by command-line option processing.
.. include:: ../tm.rst.in
:start-after: [TARGET_HAVE_SWITCHABLE_BSS_SECTIONS]
diff --git a/gcc/doc/gccint/target-description-macros-and-functions/run-time-target-specification.rst b/gcc/doc/gccint/target-description-macros-and-functions/run-time-target-specification.rst
index 0c8915b0501..e222051449b 100644
--- a/gcc/doc/gccint/target-description-macros-and-functions/run-time-target-specification.rst
+++ b/gcc/doc/gccint/target-description-macros-and-functions/run-time-target-specification.rst
@@ -76,8 +76,8 @@ any target-specific headers.
:end-before: [TARGET_DEFAULT_TARGET_FLAGS]
- This variable specifies the initial value of ``target_flags``.
- Its default setting is 0.
+This variable specifies the initial value of ``target_flags``.
+Its default setting is 0.
.. index:: optional hardware or system features
@@ -88,34 +88,34 @@ any target-specific headers.
:end-before: [TARGET_HANDLE_OPTION]
- This hook is called whenever the user specifies one of the
- target-specific options described by the :samp:`.opt` definition files
- (see :ref:`options`). It has the opportunity to do some option-specific
- processing and should return true if the option is valid. The default
- definition does nothing but return true.
+This hook is called whenever the user specifies one of the
+target-specific options described by the :samp:`.opt` definition files
+(see :ref:`options`). It has the opportunity to do some option-specific
+processing and should return true if the option is valid. The default
+definition does nothing but return true.
- :samp:`{decoded}` specifies the option and its arguments. :samp:`{opts}` and
- :samp:`{opts_set}` are the ``gcc_options`` structures to be used for
- storing option state, and :samp:`{loc}` is the location at which the
- option was passed ( ``UNKNOWN_LOCATION`` except for options passed
- via attributes).
+:samp:`{decoded}` specifies the option and its arguments. :samp:`{opts}` and
+:samp:`{opts_set}` are the ``gcc_options`` structures to be used for
+storing option state, and :samp:`{loc}` is the location at which the
+option was passed ( ``UNKNOWN_LOCATION`` except for options passed
+via attributes).
.. include:: tm.rst.in
:start-after: [TARGET_HANDLE_C_OPTION]
:end-before: [TARGET_HANDLE_C_OPTION]
- This target hook is called whenever the user specifies one of the
- target-specific C language family options described by the :samp:`.opt`
- definition files(see :ref:`options`). It has the opportunity to do some
- option-specific processing and should return true if the option is
- valid. The arguments are like for ``TARGET_HANDLE_OPTION``. The
- default definition does nothing but return false.
+This target hook is called whenever the user specifies one of the
+target-specific C language family options described by the :samp:`.opt`
+definition files(see :ref:`options`). It has the opportunity to do some
+option-specific processing and should return true if the option is
+valid. The arguments are like for ``TARGET_HANDLE_OPTION``. The
+default definition does nothing but return false.
- In general, you should use ``TARGET_HANDLE_OPTION`` to handle
- options. However, if processing an option requires routines that are
- only available in the C (and related language) front ends, then you
- should use ``TARGET_HANDLE_C_OPTION`` instead.
+In general, you should use ``TARGET_HANDLE_OPTION`` to handle
+options. However, if processing an option requires routines that are
+only available in the C (and related language) front ends, then you
+should use ``TARGET_HANDLE_C_OPTION`` instead.
.. include:: tm.rst.in
:start-after: [TARGET_OBJC_CONSTRUCT_STRING_OBJECT]
@@ -160,17 +160,17 @@ any target-specific headers.
:end-before: [TARGET_OPTION_OPTIMIZATION_TABLE]
- Some machines may desire to change what optimizations are performed for
- various optimization levels. This variable, if defined, describes
- options to enable at particular sets of optimization levels. These
- options are processed once
- just after the optimization level is determined and before the remainder
- of the command options have been parsed, so may be overridden by other
- options passed explicitly.
+Some machines may desire to change what optimizations are performed for
+various optimization levels. This variable, if defined, describes
+options to enable at particular sets of optimization levels. These
+options are processed once
+just after the optimization level is determined and before the remainder
+of the command options have been parsed, so may be overridden by other
+options passed explicitly.
- This processing is run once at program startup and when the optimization
- options are changed via ``#pragma GCC optimize`` or by using the
- ``optimize`` attribute.
+This processing is run once at program startup and when the optimization
+options are changed via ``#pragma GCC optimize`` or by using the
+``optimize`` attribute.
.. include:: tm.rst.in
:start-after: [TARGET_OPTION_INIT_STRUCT]
More information about the Gcc-cvs
mailing list