[flang-commits] [flang] 626a4cf - [flang] Document non-standard use of larger INTEGER for sizes

[peter klausler via flang-commits]

Author: peter klausler
Date: 2019-07-08T10:44:14-07:00
New Revision: 626a4cfdfce09dc1368b3a6a298b0b7e4571247b

URL: https://github.com/llvm/llvm-project/commit/626a4cfdfce09dc1368b3a6a298b0b7e4571247b
DIFF: https://github.com/llvm/llvm-project/commit/626a4cfdfce09dc1368b3a6a298b0b7e4571247b.diff

LOG: [flang] Document non-standard use of larger INTEGER for sizes

Original-commit: flang-compiler/f18 at edc79c4257079378df534247858832dba7a35920
Reviewed-on: https://github.com/flang-compiler/f18/pull/553
Tree-same-pre-rewrite: false

Added: 
    

Modified: 
    flang/documentation/Extensions.md

Removed: 
    


################################################################################
diff  --git a/flang/documentation/Extensions.md b/flang/documentation/Extensions.md
index bf744a767616..b77ee4bf2d31 100644
--- a/flang/documentation/Extensions.md
+++ b/flang/documentation/Extensions.md
@@ -12,6 +12,17 @@ Other non-standard features, which do conflict with the current
 standard specification of the Fortran programming language, are
 accepted if enabled by command-line options.
 
+Intentional violations of the standard
+======================================
+* The default `INTEGER` type is required by the standard to occupy
+  the same amount of storage as the default `REAL` type.  Default
+  `REAL` is of course 32-bit IEEE-754 floating-point today.  This legacy
+  rule imposes an artificially small constraint in some cases
+  where Fortran mandates that something have the default `INTEGER`
+  type: array bounds, `CHARACTER` length, subscripts, and the results
+  of intrinsic function references that return such things.  We
+  use `INTEGER(KIND=8)` for such things.
+
 Extensions, deletions, and legacy features supported by default
 ===============================================================
 * Tabs in source