From 97d41887192412188546fe863f9d67197997dbaa Mon Sep 17 00:00:00 2001 From: Martin Sebor Date: Mon, 14 Jan 2019 11:26:32 -0700 Subject: [PATCH] invoke.texi (-Wmemset-transposed-args): Fix typos, adjust wording. gcc/ChangeLog: * invoke.texi (-Wmemset-transposed-args): Fix typos, adjust wording. From-SVN: r267920 --- gcc/doc/invoke.texi | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index abfb1d19ed1..5ed1d133420 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -6959,14 +6959,15 @@ the element size. This warning is enabled by @option{-Wall}. @item -Wmemset-transposed-args @opindex Wmemset-transposed-args @opindex Wno-memset-transposed-args -Warn for suspicious calls to the @code{memset} built-in function, if the -second argument is not zero and the third argument is zero. This warns e.g.@: -about @code{memset (buf, sizeof buf, 0)} where most probably -@code{memset (buf, 0, sizeof buf)} was meant instead. The diagnostics -is only emitted if the third argument is literal zero. If it is some -expression that is folded to zero, a cast of zero to some type, etc., -it is far less likely that the user has mistakenly exchanged the arguments -and no warning is emitted. This warning is enabled by @option{-Wall}. +Warn for suspicious calls to the @code{memset} built-in function where +the second argument is not zero and the third argument is zero. For +example, the call @code{memset (buf, sizeof buf, 0)} is diagnosed because +@code{memset (buf, 0, sizeof buf)} was meant instead. The diagnostic +is only emitted if the third argument is a literal zero. Otherwise, if +it is an expression that is folded to zero, or a cast of zero to some +type, it is far less likely that the arguments have been mistakenly +transposed and no warning is emitted. This warning is enabled +by @option{-Wall}. @item -Waddress @opindex Waddress -- 2.30.2