From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Cc: mirimmad@outlook.com, David Malcolm <dmalcolm@redhat.com>
Subject: [PATCH] docs: remove recently added trailing whitespaces
Date: Mon, 25 Jul 2022 09:00:20 +0200 [thread overview]
Message-ID: <0bbbacab-5518-8653-4748-5d47c2d03dc0@suse.cz> (raw)
Pushed as obvious.
Martin
gcc/ChangeLog:
* doc/extend.texi: Remove trailing whitespaces.
* doc/invoke.texi: Likewise.
---
gcc/doc/extend.texi | 12 ++++++------
gcc/doc/invoke.texi | 10 +++++-----
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 71897b84a1b..7fe7f8817cd 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -3007,15 +3007,15 @@ produced by @command{gold}.
For other linkers that cannot generate resolution file,
explicit @code{externally_visible} attributes are still necessary.
-@item fd_arg
+@item fd_arg
@itemx fd_arg (@var{N})
@cindex @code{fd_arg} function attribute
-The @code{fd_arg} attribute may be applied to a function that takes an open
+The @code{fd_arg} attribute may be applied to a function that takes an open
file descriptor at referenced argument @var{N}.
It indicates that the passed filedescriptor must not have been closed.
-Therefore, when the analyzer is enabled with @option{-fanalyzer}, the
-analyzer may emit a @option{-Wanalyzer-fd-use-after-close} diagnostic
+Therefore, when the analyzer is enabled with @option{-fanalyzer}, the
+analyzer may emit a @option{-Wanalyzer-fd-use-after-close} diagnostic
if it detects a code path in which a function with this attribute is
called with a closed file descriptor.
@@ -3040,8 +3040,8 @@ attribute is called on a file descriptor opened with @code{O_WRONLY}.
@itemx fd_arg_write (@var{N})
@cindex @code{fd_arg_write} function attribute
The @code{fd_arg_write} is identical to @code{fd_arg_read} except that the
-analyzer may emit a @option{-Wanalyzer-access-mode-mismatch} diagnostic if
-it detects a code path in which a function with this attribute is called on a
+analyzer may emit a @option{-Wanalyzer-access-mode-mismatch} diagnostic if
+it detects a code path in which a function with this attribute is called on a
file descriptor opened with @code{O_RDONLY}.
@item flatten
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index b1a9f50bfc7..9a3f2d14c5a 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -9847,7 +9847,7 @@ This warning requires @option{-fanalyzer}, which enables it; use
@option{-Wno-analyzer-fd-access-mode-mismatch}
to disable it.
-This diagnostic warns for paths through code in which a
+This diagnostic warns for paths through code in which a
@code{read} on a write-only file descriptor is attempted, or vice versa.
This diagnostic also warns for code paths in a which a function with attribute
@@ -9863,7 +9863,7 @@ This warning requires @option{-fanalyzer}, which enables it; use
@option{-Wno-analyzer-fd-double-close}
to disable it.
-This diagnostic warns for paths through code in which a
+This diagnostic warns for paths through code in which a
file descriptor can be closed more than once.
@item -Wno-analyzer-fd-leak
@@ -9873,7 +9873,7 @@ This warning requires @option{-fanalyzer}, which enables it; use
@option{-Wno-analyzer-fd-leak}
to disable it.
-This diagnostic warns for paths through code in which an
+This diagnostic warns for paths through code in which an
open file descriptor is leaked.
@item -Wno-analyzer-fd-use-after-close
@@ -9883,7 +9883,7 @@ This warning requires @option{-fanalyzer}, which enables it; use
@option{-Wno-analyzer-fd-use-after-close}
to disable it.
-This diagnostic warns for paths through code in which a
+This diagnostic warns for paths through code in which a
read or write is called on a closed file descriptor.
This diagnostic also warns for paths through code in which
@@ -9898,7 +9898,7 @@ This warning requires @option{-fanalyzer}, which enables it; use
@option{-Wno-analyzer-fd-use-without-check}
to disable it.
-This diagnostic warns for paths through code in which a
+This diagnostic warns for paths through code in which a
file descriptor is used without being checked for validity.
This diagnostic also warns for paths through code in which
--
2.37.1
reply other threads:[~2022-07-25 7:00 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=0bbbacab-5518-8653-4748-5d47c2d03dc0@suse.cz \
--to=mliska@suse.cz \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mirimmad@outlook.com \
/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).