aboutsummaryrefslogtreecommitdiff
path: root/gcc/ada/gnat_rm.texi
diff options
context:
space:
mode:
authorEric Botcazou <ebotcazou@adacore.com>2020-08-18 16:04:09 +0200
committerPierre-Marie de Rodat <derodat@adacore.com>2020-10-22 08:11:22 -0400
commitea56c18c501657906e72a693dba7775b2f39a004 (patch)
tree41666c1e4a87a9fa9829ddbf8328e9a59adf1565 /gcc/ada/gnat_rm.texi
parent903275965921f6f63519f07b4f82467ee39160a1 (diff)
downloadgcc-ea56c18c501657906e72a693dba7775b2f39a004.zip
gcc-ea56c18c501657906e72a693dba7775b2f39a004.tar.gz
gcc-ea56c18c501657906e72a693dba7775b2f39a004.tar.bz2
[Ada] Minor fixes in GNAT RM
gcc/ada/ * doc/gnat_rm/implementation_defined_characteristics.rst: Minor fixes. * gnat_rm.texi: Regenerate.
Diffstat (limited to 'gcc/ada/gnat_rm.texi')
-rw-r--r--gcc/ada/gnat_rm.texi7
1 files changed, 3 insertions, 4 deletions
diff --git a/gcc/ada/gnat_rm.texi b/gcc/ada/gnat_rm.texi
index e5ea2e0..88e2479 100644
--- a/gcc/ada/gnat_rm.texi
+++ b/gcc/ada/gnat_rm.texi
@@ -15379,8 +15379,7 @@ Manual, and are summarized in Annex M.
A requirement for conforming Ada compilers is that they provide
documentation describing how the implementation deals with each of these
issues. In this chapter you will find each point in Annex M listed,
-followed by a description of how GNAT
-handles the implementation dependence.
+followed by a description of how GNAT handles the implementation dependence.
You can use this chapter as a guide to minimizing implementation
dependent features in your programs if portability to other compilers
@@ -15681,7 +15680,7 @@ supported for fixed point types. See 3.5.9(10)."
Any combinations are permitted that do not result in a small less than
@code{Fine_Delta} and do not result in a mantissa larger than 63 bits.
If the mantissa is larger than 53 bits on machines where Long_Long_Float
-is 64 bits (true of all architectures except ia32), then the output from
+is 64 bits (true of all architectures except x86), then the output from
Text_IO is accurate to only 53 bits, rather than the full mantissa. This
is because floating-point conversions are used to convert fixed point.
@@ -17505,7 +17504,7 @@ perfect result set. See G.2.3(22)."
The result is only defined to be in the perfect result set if the result
can be computed by a single scaling operation involving a scale factor
-representable in 64-bits.
+representable in 64 bits.
@itemize *