Update BOZ constant documentation.

In the section "BOZ Literal constants" delete paragraph about integer
overload errors when initialising integer variables with BOZ constants
as these no longer occur.

From-SVN: r274667

diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog
index 8cca6179eb84b3f31d2b77c2dad4ecaebc6e86ea..1f4477670038616d6b7b2fee69a5fafa4cc3d415 100644 (file)
--- a/gcc/fortran/ChangeLog
+++ b/gcc/fortran/ChangeLog
@@ -1,3 +1,9 @@
+2019-08-19  Mark Eggleston  <mark.eggleston@codethink.com>
+
+       * gfortran.texi: Delete paragraph about integer overload errors
+       when initialising integer variables with BOZ constants as these
+       no longer occur.
+
 2019-08-18  Steven G. Kargl  <kargl@gcc.gnu.org>
 
        PR fortran/91485

diff --git a/gcc/fortran/gfortran.texi b/gcc/fortran/gfortran.texi
index 16be9e05b43282ff475db5444f16cb4d5ae40ffc..4515b9d02e426ac584bdec1c998c4632341b792a 100644 (file)
--- a/gcc/fortran/gfortran.texi
+++ b/gcc/fortran/gfortran.texi
@@ -1882,13 +1882,6 @@ with @code{2.0}.) As different compilers implement the extension
 differently, one should be careful when doing bitwise initialization
 of non-integer variables.
 
-Note that initializing an @code{INTEGER} variable with a statement such
-as @code{DATA i/Z'FFFFFFFF'/} will give an integer overflow error rather
-than the desired result of @math{-1} when @code{i} is a 32-bit integer
-on a system that supports 64-bit integers.  The @samp{-fno-range-check}
-option can be used as a workaround for legacy code that initializes
-integers in this manner.
-
 @node Real array indices
 @subsection Real array indices
 @cindex array, indices of type real