[flang-commits] [flang] [flang][docs] Extensions.md audit (PR #202331)

[via flang-commits]

================
@@ -529,6 +529,51 @@ end program
 * When the argument to intrinsic `ALLOCATED(p)` is actually a pointer
   rather than an allocatable, it is interpreted as `ASSOCIATED(p)` with a
   stern warning.
+* PowerPC `VECTOR(type)`, `__VECTOR_PAIR`, and `__VECTOR_QUAD` type specifiers
+  are accepted as an altivec extension, with a portability warning.
+* Multiple program units may appear on the same source line, separated by
+  semicolons; the standard requires each program unit to begin on a new line.
+  A portability warning is emitted.
+* Branching into a DO loop body from outside the loop via `GO TO` or arithmetic
+  `IF` is accepted with a portability warning.
+* Branching (via `GO TO` or `ASSIGN`/assigned `GO TO`) to a label that is not
+  a standard branch target is accepted with a portability warning.
+* A labeled `DO` loop is allowed to end at any labeled executable statement,
+  not only `END DO` or `CONTINUE`, with a portability warning.
+* Names that exceed the maximum length of 63 characters (F2023 C612) are
+  accepted with a portability warning.
+* An element of a contiguous `POINTER` or assumed-shape array may be used as
+  the initial element of a storage sequence (sequence association), with a
+  portability warning.
+* A Cray `POINTER` pointee whose type is a derived type that is neither
+  `SEQUENCE` nor `BIND(C)` is accepted with a portability warning.
----------------
tmjbios wrote:

Does this matter? `POINTER(ptr,pte)` isn't standard anyway, and Cray doesn't place such a restriction or warning; any usage of a cray pointer could be flagged as a portability warning.

https://github.com/llvm/llvm-project/pull/202331