Hello, I noticed tiny typos in the docs. (CC me with replies, please, as I'm not reading the list.)
Vladimir
From 707de44fdb74ecfbc7120e2d6b5b9fdb4d281855 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Vladim=C3=ADr=20=C4=8Cun=C3=A1t?= <vcu...@gmail.com>
Date: Fri, 1 Jan 2016 20:10:56 +0100
Subject: [PATCH] * doc/invoke.texi: fix typos of -finite-math-only
I believe there are no other s/-ff/-f/ typos in this file.
---
gcc/doc/invoke.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index b85f9b5..3f91d1a 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -20374,7 +20374,7 @@ Newton-Raphson steps to increase precision
instead of doing a divide or
square root and divide for floating-point arguments. You should use
the @option{-ffast-math} option when using @option{-mrecip} (or at
least @option{-funsafe-math-optimizations},
-@option{-finite-math-only}, @option{-freciprocal-math} and
+@option{-ffinite-math-only}, @option{-freciprocal-math} and
@option{-fno-trapping-math}). Note that while the throughput of the
sequence is generally higher than the throughput of the non-reciprocal
instruction, the precision of the sequence can be decreased by up to 2
@@ -23366,7 +23366,7 @@ to increase precision instead of @code{DIVSS}
and @code{SQRTSS}
(and their vectorized
variants) for single-precision floating-point arguments. These
instructions
are generated only when @option{-funsafe-math-optimizations} is enabled
-together with @option{-finite-math-only} and @option{-fno-trapping-math}.
+together with @option{-ffinite-math-only} and @option{-fno-trapping-math}.
Note that while the throughput of the sequence is higher than the
throughput
of the non-reciprocal instruction, the precision of the sequence can be
decreased by up to 2 ulp (i.e. the inverse of 1.0 equals 0.99999994).
--
2.5.2
smime.p7s
Description: S/MIME Cryptographic Signature
