The attached patch corrects a couple of minor typos in the description
of -Wmemset-transposed-args. It also tweaks the text a bit for better
readability.
Martin
gcc/ChangeLog:
* invoke.texi (-Wmemset-transposed-args): Fix typos, adjust wording.
Index: gcc/doc/invoke.texi
===================================================================
--- gcc/doc/invoke.texi (revision 267568)
+++ gcc/doc/invoke.texi (working copy)
@@ -6958,14 +6958,15 @@ the element size. This warning is enabled by @opt
@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
