* Using non-integer expressions for array bounds (e.g., REAL A(3.14159)) (PGI/Intel)
* Mixing INTEGER types as operands to bit intrinsics (e.g., IAND); only two
compilers support it, and they disagree on sign extension.
+
+Preprocessing behavior
+======================
+* The preprocessor is always run, whatever the filename extension may be.
+* We respect Fortran comments in macro actual arguments (like GNU, Intel, NAG;
+ unlike PGI and XLF) on the principle that macro calls should be treated
+ like function references. Fortran's line continuation methods also work.
<!--
-Copyright (c) 2018, NVIDIA CORPORATION. All rights reserved.
+Copyright (c) 2018-2019, NVIDIA CORPORATION. All rights reserved.
-->
Fortran Preprocessing
* `#define c 1` does not allow a `c` in column 1 to be used as a label
in fixed form, rather than as a comment line indicator.
* IBM claims to be ISO C compliant and therefore recognizes trigraph sequences.
+* Fortran comments in macro actual arguments should be respected, on
+ the principle that a macro call should work like a function reference.
Behavior that few compilers properly support (or none), but should:
-------------------------------------------------------------------