[flang-commits] [flang] [flang][docs] Replace references to f18 with flang (Part 2) (PR #164258)
Tarun Prabhu via flang-commits
flang-commits at lists.llvm.org
Mon Oct 27 07:35:23 PDT 2025
https://github.com/tarunprabhu updated https://github.com/llvm/llvm-project/pull/164258
>From a0c38f40d5540a1b31c6fabc508edef87f097a31 Mon Sep 17 00:00:00 2001
From: Tarun Prabhu <tarun at lanl.gov>
Date: Mon, 20 Oct 2025 07:48:25 -0600
Subject: [PATCH 1/2] [flang][docs] Replace references to f18 with flang (Part
2)
Trailing whitespace was also removed in the files that were edited.
---
flang/docs/IORuntimeInternals.md | 6 ++---
flang/docs/ModFiles.md | 8 +++---
flang/docs/OpenACC-descriptor-management.md | 30 ++++++++++-----------
flang/docs/OpenMP-semantics.md | 10 +++----
flang/docs/OptionComparison.md | 22 +++++++--------
flang/docs/Parsing.md | 10 +++----
flang/docs/Preprocessing.md | 8 +++---
flang/docs/RuntimeDescriptor.md | 8 +++---
flang/docs/RuntimeTypeInfo.md | 12 ++++-----
9 files changed, 57 insertions(+), 57 deletions(-)
diff --git a/flang/docs/IORuntimeInternals.md b/flang/docs/IORuntimeInternals.md
index d4e321348b2de..a2d3971c9ef2a 100644
--- a/flang/docs/IORuntimeInternals.md
+++ b/flang/docs/IORuntimeInternals.md
@@ -15,7 +15,7 @@ local:
```
This note is meant to be an overview of the design of the *implementation*
-of the f18 Fortran compiler's runtime support library for I/O statements.
+of Flang's runtime support library for I/O statements.
The *interface* to the I/O runtime support library is defined in the
C++ header file `runtime/io-api.h`.
@@ -66,7 +66,7 @@ modified with optional template arguments that override their
allocators and deallocators.
Conversions between the many binary floating-point formats supported
-by f18 and their decimal representations are performed with the same
+by Flang and their decimal representations are performed with the same
template library of fast conversion algorithms used to interpret
floating-point values in Fortran source programs and to emit them
to module files.
@@ -245,7 +245,7 @@ for this purpose.
### `IoStatementState`
-F18's Fortran I/O runtime support library defines and implements an API
+Flang's Fortran I/O runtime support library defines and implements an API
that uses a sequence of function calls to implement each Fortran I/O
statement.
The state of each I/O statement in progress is maintained in some
diff --git a/flang/docs/ModFiles.md b/flang/docs/ModFiles.md
index fc05c2677fc26..4485770f7d24d 100644
--- a/flang/docs/ModFiles.md
+++ b/flang/docs/ModFiles.md
@@ -1,9 +1,9 @@
-<!--===- docs/ModFiles.md
-
+<!--===- docs/ModFiles.md
+
Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
See https://llvm.org/LICENSE.txt for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-
+
-->
# Module Files
@@ -36,7 +36,7 @@ but this one doesn't.
The disadvantage of using the same name as other compilers is that it is not
clear which compiler created a `.mod` file and files from multiple compilers
cannot be in the same directory. This can be solved by adding something
-between the module name and extension, e.g. `<modulename>-f18.mod`. When
+between the module name and extension, e.g. `<modulename>-flang.mod`. When
this is needed, Flang accepts the option `-module-suffix` to alter the suffix.
## Format
diff --git a/flang/docs/OpenACC-descriptor-management.md b/flang/docs/OpenACC-descriptor-management.md
index 008c57937e23b..a9618667af387 100644
--- a/flang/docs/OpenACC-descriptor-management.md
+++ b/flang/docs/OpenACC-descriptor-management.md
@@ -53,7 +53,7 @@ program main
real, pointer :: t1(:,:)
nullify(d%p)
allocate(t1(2,2))
-
+
! 2.7.9:
! Allocates the memory for object 'd' on the device.
! The descriptor member of 'd' is a NULL descriptor,
@@ -62,9 +62,9 @@ program main
! The descriptor storage is created on the device
! just as part of the object 'd' storage.
!$acc enter data create(d)
-
+
d%p => t1
-
+
! 2.7.7:
! Pointer d%p is not present on the device, so copyin
! action is performed for the data pointed to by the pointer:
@@ -80,7 +80,7 @@ program main
! from the host values of the corresponding members.
! * The attachment counter of 'd%p' is set to 1.
!$acc enter data copyin(d%p)
-
+
! 2.7.7:
! Pointer d%p is already present on the device, so no copyin
! action is performed.
@@ -89,12 +89,12 @@ program main
! during the previous attachment, only its attachment counter
! is incremented to 2.
!$acc enter data copyin(d%p)
-
+
! 3.2.29:
! The detach action is performed. According to 2.7.2 the attachment
! counter of d%p is decremented to 1.
call acc_detach(d%p)
-
+
! 3.2.29:
! The detach action is performed. According to 2.7.2 the attachment
! counter of d%p is decremented to 0, which initiates an update
@@ -102,7 +102,7 @@ program main
! pointer in the local memory.
! We will discuss this in more detail below.
call acc_detach(d%p)
-
+
! The following construct will fail, because the 'd%p' descriptor's
! base_addr is now the host address not accessible on the device.
! Without the second 'acc_detach' it will work correctly.
@@ -111,7 +111,7 @@ program main
!$acc end serial
```
-Let's discuss in more detail what happens during the second `acc_detach`.
+Let's discuss in more detail what happens during the second `acc_detach`.
OpenACC 2.6.4:
@@ -255,7 +255,7 @@ Due to `d%p` reference in the `present` clause of the `serial` region, the compi
In the case of POINTER dummy argument, if the descriptor storage is not explicitly created in the user code, the pointer attachment may not happen due to 2.7.2:
> 1693 If the pointer var is in shared memory or is not present in the current device memory, or if the
-> 1694 address to which var points is not present in the current device memory, no action is taken.
+> 1694 address to which var points is not present in the current device memory, no action is taken.
Example:
@@ -300,7 +300,7 @@ contains
### Other variables
-F18 compiler also uses descriptors for assumed-shape, assumed-rank, polymorphic, ... variables. The OpenACC specification does not prescribe how an implementation should manage the descriptors for such variables. In many (all?) cases the descriptors of these variables have a local scope of a single subprogram, and if a descriptor of such a variable is created on the device, then its live range must be limited on the device by the invocation of the subprogram (with any OpenACC constructs inside it).
+Flang also uses descriptors for assumed-shape, assumed-rank, polymorphic, ... variables. The OpenACC specification does not prescribe how an implementation should manage the descriptors for such variables. In many (all?) cases the descriptors of these variables have a local scope of a single subprogram, and if a descriptor of such a variable is created on the device, then its live range must be limited on the device by the invocation of the subprogram (with any OpenACC constructs inside it).
For example:
@@ -330,15 +330,15 @@ Pointer attachment for POINTER and ALLOCATABLE variables is a "composite" runtim
## Representing pointer attachment in MLIR OpenACC dialect
-The Fortran pointer attachment logic specified by OpenACC is not trivial, and in order to be expressed in a language independent MLIR OpenACC dialect we propose to use recipes for delegating the complexity of the implementation to F18 runtime.
+The Fortran pointer attachment logic specified by OpenACC is not trivial, and in order to be expressed in a language independent MLIR OpenACC dialect we propose to use recipes for delegating the complexity of the implementation to Flang's runtime.
```Fortran
!$acc enter data attach(d%p)
```
-The frontend generates an `acc.attach` data operation with `augPtr` being an address of the F18 descriptor representing a POINTER/ALLOCATABLE variable. Note that `augPtr` refers to an abstract augmented pointer structure, which is handled in a language specific manner by the code provided by the `attachRecipe` reference.
+The frontend generates an `acc.attach` data operation with `augPtr` being an address of the Flang descriptor representing a POINTER/ALLOCATABLE variable. Note that `augPtr` refers to an abstract augmented pointer structure, which is handled in a language specific manner by the code provided by the `attachRecipe` reference.
-The `attachRecipe` is a callback that takes `varPtr` and `augPtr` pointers, and the section's `offset` and `size` computed from the `bounds` operand of `acc.attach`. Fortran FE passes these arguments directly to F18 runtime that is aware of the descriptor structure and does all the required checks and device memory updates for the device copy of the descriptor, including the attachment counters updates.
+The `attachRecipe` is a callback that takes `varPtr` and `augPtr` pointers, and the section's `offset` and `size` computed from the `bounds` operand of `acc.attach`. Fortran FE passes these arguments directly to Flang's runtime that is aware of the descriptor structure and does all the required checks and device memory updates for the device copy of the descriptor, including the attachment counters updates.
```
acc.attach.recipe @attach_ref :
@@ -387,7 +387,7 @@ For other data clauses there is an implied ordering that the data action happens
Here, the `copyin` of the data is followed by the pointer attachment.
-### F18 runtime support
+### Flang runtime support
The `OpenACCAttachDescriptor` API is defined like this:
@@ -427,7 +427,7 @@ The implementation's behavior may be described as (OpenACC 2.7.2):
All the "is-present" checks and the data actions for the auxiliary pointers must be performed atomically with regards to the present counters bookkeeping.
-The API relies on the primitives provided by `liboffload`, so it is provided by a new F18 runtime library, e.g. `FortranOffloadRuntime`, that depends on `flang_rt.runtime` and `liboffload`. The F18 driver adds `FortranOffloadRuntime` for linking under `-fopenacc`/`-fopenmp` (and maybe additional switches like `-fopenmp-targets`).
+The API relies on the primitives provided by `liboffload`, so it is provided by a new Flang runtime library, e.g. `FortranOffloadRuntime`, that depends on `flang_rt.runtime` and `liboffload`. Flang's driver adds `FortranOffloadRuntime` for linking under `-fopenacc`/`-fopenmp` (and maybe additional switches like `-fopenmp-targets`).
## TODOs:
diff --git a/flang/docs/OpenMP-semantics.md b/flang/docs/OpenMP-semantics.md
index 57938afba62dd..de85f98292d10 100644
--- a/flang/docs/OpenMP-semantics.md
+++ b/flang/docs/OpenMP-semantics.md
@@ -1,9 +1,9 @@
-<!--===- docs/OpenMP-semantics.md
-
+<!--===- docs/OpenMP-semantics.md
+
Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
See https://llvm.org/LICENSE.txt for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-
+
-->
# OpenMP Semantic Analysis
@@ -14,7 +14,7 @@ local:
---
```
-## OpenMP for F18
+## OpenMP for Flang
1. Define and document the parse tree representation for
* Directives (listed below)
@@ -68,7 +68,7 @@ starting from `!$OMP`.
In `parser-tree.h`,
`OpenMPDeclarativeConstruct` is part
of the `SpecificationConstruct` and `SpecificationPart`
-in F18 because
+in Flang because
a declarative directive can only be placed in the specification part
of a Fortran program.
diff --git a/flang/docs/OptionComparison.md b/flang/docs/OptionComparison.md
index fb65498fa1f44..a293b284a5e8e 100644
--- a/flang/docs/OptionComparison.md
+++ b/flang/docs/OptionComparison.md
@@ -1,16 +1,16 @@
-<!--===- docs/OptionComparison.md
-
+<!--===- docs/OptionComparison.md
+
Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
See https://llvm.org/LICENSE.txt for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-
+
-->
# Compiler options comparison
-This document catalogs the options processed by F18's peers/competitors. Much of the document is taken up by a set of tables that list the options categorized into different topics. Some of the table headings link to more information about the contents of the tables. For example, the table on **Standards conformance** options links to <a href=#standards">notes on Standards conformance</a>.
+This document catalogs the options processed by Flang's peers/competitors. Much of the document is taken up by a set of tables that list the options categorized into different topics. Some of the table headings link to more information about the contents of the tables. For example, the table on **Standards conformance** options links to <a href=#standards">notes on Standards conformance</a>.
-**There's also important information in the ___[Appendix section](#appendix)___ near the end of the document on how this data was gathered and what ___is___ and ___is not___ included in this document.**
+**There's also important information in the ___[Appendix section](#appendix)___ near the end of the document on how this data was gathered and what ___is___ and ___is not___ included in this document.**
Note that compilers may support language features without having an option for them. Such cases are frequently, but not always noted in this document.
@@ -281,7 +281,7 @@ fd-lines-as-comments
</td>
<td>eQ
</td>
- <td>N/A
+ <td>N/A
</td>
<td>N/A
</td>
@@ -428,7 +428,7 @@ fd-lines-as-comments
</td>
<td>Monetrip
</td>
- <td>N/A
+ <td>N/A
</td>
</tr>
<tr>
@@ -1187,16 +1187,16 @@ Mcuda
## Notes
-**<a name="standards"></a>Standards conformance:**
+**<a name="standards"></a>Standards conformance:**
All conformance options are similar -- they issue warnings if non-standard features are used. All defaults are to allow extensions without warnings. The GNU, IBM, and Intel compilers allow multiple standard levels to be specified.
-* **Cray**: The capital "-eN" option specifies to issue error messages for non-compliance rather than warnings.
+* **Cray**: The capital "-eN" option specifies to issue error messages for non-compliance rather than warnings.
* **GNU:** The "std=_level_" option specifies the standard to which the program is expected to conform. The default value for std is 'gnu', which specifies a superset of the latest Fortran standard that includes all of the extensions supported by GNU Fortran, although warnings will be given for obsolete extensions not recommended for use in new code. The 'legacy' value is equivalent but without the warnings for obsolete extensions. The 'f95', 'f2003', 'f2008', and 'f2018' values specify strict conformance to the respective standards. Errors are given for all extensions beyond the relevant language standard, and warnings are given for the Fortran 77 features that are permitted but obsolescent in later standards. '-std=f2008ts' allows the Fortran 2008 standard including the additions of the Technical Specification (TS) 29113 on Further Interoperability of Fortran with C and TS 18508 on Additional Parallel Features in Fortran. Values for "_level_" are f_95, f2003, f2008, f2008ts, f2018, gnu,_ and _legacy._
-**<a name="source"></a>Source format:**
+**<a name="source"></a>Source format:**
**Fixed or free source:** Cray, IBM, and Intel default the source format based on the source file suffix as follows:
@@ -1220,7 +1220,7 @@ IBM Fortran's options allow the source line length to be specified with the opti
* **GNU:** For both "ffixed-line-length-_n_" and "ffree-line-length-_n_" options, characters are ignored after the specified length. The default for fixed is 72. The default for free is 132. For free, you can specify 'none' as the length, which means that all characters in the line are meaningful.
* **IBM:** For **fixed**, the default is 72. For **free**, there's no default, but the maximum length for either form is 132.
* **Intel:** The default is 72 for **fixed** and 132 for **free**.
-* **PGI, Flang:**
+* **PGI, Flang:**
* in free form, it is an error if the line is longer than 1000 characters
* in fixed form by default, characters after column 72 are ignored
* in fixed form with -Mextend, characters after column 132 are ignored
diff --git a/flang/docs/Parsing.md b/flang/docs/Parsing.md
index bedc1ea6aee97..eae92519c6004 100644
--- a/flang/docs/Parsing.md
+++ b/flang/docs/Parsing.md
@@ -1,12 +1,12 @@
-<!--===- docs/Parsing.md
-
+<!--===- docs/Parsing.md
+
Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
See https://llvm.org/LICENSE.txt for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-
+
-->
-# The F18 Parser
+# The Flang Parser
```{contents}
---
@@ -182,7 +182,7 @@ Parse tree entities should be viewed as values, not objects; their
addresses should not be abused for purposes of identification. They are
assembled with C++ move semantics during parse tree construction.
Their default and copy constructors are deliberately deleted in their
-declarations.
+declarations.
The std::list<> data type is used in the parse tree to reliably store pointers
to other relevant entries in the tree. Since the tree lists are moved and
diff --git a/flang/docs/Preprocessing.md b/flang/docs/Preprocessing.md
index db815b9244edf..e167922319785 100644
--- a/flang/docs/Preprocessing.md
+++ b/flang/docs/Preprocessing.md
@@ -1,9 +1,9 @@
-<!--===- docs/Preprocessing.md
-
+<!--===- docs/Preprocessing.md
+
Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
See https://llvm.org/LICENSE.txt for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-
+
-->
# Fortran Preprocessing
@@ -163,7 +163,7 @@ The first block of tests (`pp0*.F`) are all fixed-form source files;
the second block (`pp1*.F90`) are free-form source files.
```
-f18
+flang
| pgfortran
| | ifort
| | | gfortran
diff --git a/flang/docs/RuntimeDescriptor.md b/flang/docs/RuntimeDescriptor.md
index e6ce825b04402..a2a701a8c02bd 100644
--- a/flang/docs/RuntimeDescriptor.md
+++ b/flang/docs/RuntimeDescriptor.md
@@ -1,9 +1,9 @@
-<!--===- docs/RuntimeDescriptor.md
-
+<!--===- docs/RuntimeDescriptor.md
+
Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
See https://llvm.org/LICENSE.txt for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-
+
-->
# Runtime Descriptors
@@ -399,7 +399,7 @@ pointer.
This design in the Standard precludes the use of static descriptors that
could be associated with dynamic base addresses.
-The F18 runtime cannot use just the mandated interoperable
+Flang's runtime cannot use just the mandated interoperable
`struct CFI_cdesc_t` argument descriptor structure as its
all-purpose data descriptor.
It has no information about derived type components, overridable
diff --git a/flang/docs/RuntimeTypeInfo.md b/flang/docs/RuntimeTypeInfo.md
index 8bd5551c66678..c41a9975c3b9f 100644
--- a/flang/docs/RuntimeTypeInfo.md
+++ b/flang/docs/RuntimeTypeInfo.md
@@ -1,9 +1,9 @@
-<!--===- docs/RuntimeTypeInfo.md
-
+<!--===- docs/RuntimeTypeInfo.md
+
Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
See https://llvm.org/LICENSE.txt for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-
+
-->
# The derived type runtime information table
@@ -27,7 +27,7 @@ The runtime library uses *derived type description* tables to represent
the relevant characteristics of derived types.
This note summarizes the requirements for these descriptions.
-The semantics phase of the F18 frontend constructs derived type
+The semantics phase of Flang's frontend constructs derived type
descriptions from its scoped symbol table after name resolution
and semantic constraint checking have succeeded.
The lowering phase then transfers the tables to the static
@@ -85,7 +85,7 @@ bindings, and they do so in alphabetical order of binding name.
(This is an arbitrary choice -- we could also define them to
appear in binding declaration order, I suppose -- but a consistent
ordering should be used so that relocatables generated by distinct
-versions of the F18 compiler will have a better chance to interoperate.)
+versions of Flang will have a better chance to interoperate.)
### Type parameter values and "same type" testing
@@ -143,7 +143,7 @@ This means that it may or may not be passed by means of a descriptor.
Note that a `FINAL` subroutine with a scalar argument does not define
a finalizer for array objects unless the subroutine is elemental
(and probably `IMPURE`).
-This seems to be a language pitfall and F18 will emit a
+This seems to be a language pitfall and Flang will emit a
warning when an array of a finalizable derived type is declared
with a rank lacking a `FINAL` subroutine when other ranks do have one.
>From cd4ca0ffa100d156eb7aa102c1208ce49ebe51c4 Mon Sep 17 00:00:00 2001
From: Tarun Prabhu <tarun at lanl.gov>
Date: Mon, 20 Oct 2025 09:58:24 -0600
Subject: [PATCH 2/2] Don't strip trailing whitespace. The changes should only
include f18->flang
---
flang/docs/ModFiles.md | 6 +++---
flang/docs/OpenACC-descriptor-management.md | 18 +++++++++---------
flang/docs/OpenMP-semantics.md | 6 +++---
flang/docs/OptionComparison.md | 20 ++++++++++----------
flang/docs/Parsing.md | 8 ++++----
flang/docs/Preprocessing.md | 6 +++---
flang/docs/RuntimeDescriptor.md | 6 +++---
flang/docs/RuntimeTypeInfo.md | 6 +++---
8 files changed, 38 insertions(+), 38 deletions(-)
diff --git a/flang/docs/ModFiles.md b/flang/docs/ModFiles.md
index 4485770f7d24d..32d2784e9d9f0 100644
--- a/flang/docs/ModFiles.md
+++ b/flang/docs/ModFiles.md
@@ -1,9 +1,9 @@
-<!--===- docs/ModFiles.md
-
+<!--===- docs/ModFiles.md
+
Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
See https://llvm.org/LICENSE.txt for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-
+
-->
# Module Files
diff --git a/flang/docs/OpenACC-descriptor-management.md b/flang/docs/OpenACC-descriptor-management.md
index a9618667af387..7a6e6b4346348 100644
--- a/flang/docs/OpenACC-descriptor-management.md
+++ b/flang/docs/OpenACC-descriptor-management.md
@@ -53,7 +53,7 @@ program main
real, pointer :: t1(:,:)
nullify(d%p)
allocate(t1(2,2))
-
+
! 2.7.9:
! Allocates the memory for object 'd' on the device.
! The descriptor member of 'd' is a NULL descriptor,
@@ -62,9 +62,9 @@ program main
! The descriptor storage is created on the device
! just as part of the object 'd' storage.
!$acc enter data create(d)
-
+
d%p => t1
-
+
! 2.7.7:
! Pointer d%p is not present on the device, so copyin
! action is performed for the data pointed to by the pointer:
@@ -80,7 +80,7 @@ program main
! from the host values of the corresponding members.
! * The attachment counter of 'd%p' is set to 1.
!$acc enter data copyin(d%p)
-
+
! 2.7.7:
! Pointer d%p is already present on the device, so no copyin
! action is performed.
@@ -89,12 +89,12 @@ program main
! during the previous attachment, only its attachment counter
! is incremented to 2.
!$acc enter data copyin(d%p)
-
+
! 3.2.29:
! The detach action is performed. According to 2.7.2 the attachment
! counter of d%p is decremented to 1.
call acc_detach(d%p)
-
+
! 3.2.29:
! The detach action is performed. According to 2.7.2 the attachment
! counter of d%p is decremented to 0, which initiates an update
@@ -102,7 +102,7 @@ program main
! pointer in the local memory.
! We will discuss this in more detail below.
call acc_detach(d%p)
-
+
! The following construct will fail, because the 'd%p' descriptor's
! base_addr is now the host address not accessible on the device.
! Without the second 'acc_detach' it will work correctly.
@@ -111,7 +111,7 @@ program main
!$acc end serial
```
-Let's discuss in more detail what happens during the second `acc_detach`.
+Let's discuss in more detail what happens during the second `acc_detach`.
OpenACC 2.6.4:
@@ -255,7 +255,7 @@ Due to `d%p` reference in the `present` clause of the `serial` region, the compi
In the case of POINTER dummy argument, if the descriptor storage is not explicitly created in the user code, the pointer attachment may not happen due to 2.7.2:
> 1693 If the pointer var is in shared memory or is not present in the current device memory, or if the
-> 1694 address to which var points is not present in the current device memory, no action is taken.
+> 1694 address to which var points is not present in the current device memory, no action is taken.
Example:
diff --git a/flang/docs/OpenMP-semantics.md b/flang/docs/OpenMP-semantics.md
index de85f98292d10..9ba7595ce6130 100644
--- a/flang/docs/OpenMP-semantics.md
+++ b/flang/docs/OpenMP-semantics.md
@@ -1,9 +1,9 @@
-<!--===- docs/OpenMP-semantics.md
-
+<!--===- docs/OpenMP-semantics.md
+
Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
See https://llvm.org/LICENSE.txt for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-
+
-->
# OpenMP Semantic Analysis
diff --git a/flang/docs/OptionComparison.md b/flang/docs/OptionComparison.md
index a293b284a5e8e..934750a07e9bb 100644
--- a/flang/docs/OptionComparison.md
+++ b/flang/docs/OptionComparison.md
@@ -1,16 +1,16 @@
-<!--===- docs/OptionComparison.md
-
+<!--===- docs/OptionComparison.md
+
Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
See https://llvm.org/LICENSE.txt for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-
+
-->
# Compiler options comparison
This document catalogs the options processed by Flang's peers/competitors. Much of the document is taken up by a set of tables that list the options categorized into different topics. Some of the table headings link to more information about the contents of the tables. For example, the table on **Standards conformance** options links to <a href=#standards">notes on Standards conformance</a>.
-**There's also important information in the ___[Appendix section](#appendix)___ near the end of the document on how this data was gathered and what ___is___ and ___is not___ included in this document.**
+**There's also important information in the ___[Appendix section](#appendix)___ near the end of the document on how this data was gathered and what ___is___ and ___is not___ included in this document.**
Note that compilers may support language features without having an option for them. Such cases are frequently, but not always noted in this document.
@@ -281,7 +281,7 @@ fd-lines-as-comments
</td>
<td>eQ
</td>
- <td>N/A
+ <td>N/A
</td>
<td>N/A
</td>
@@ -428,7 +428,7 @@ fd-lines-as-comments
</td>
<td>Monetrip
</td>
- <td>N/A
+ <td>N/A
</td>
</tr>
<tr>
@@ -1187,16 +1187,16 @@ Mcuda
## Notes
-**<a name="standards"></a>Standards conformance:**
+**<a name="standards"></a>Standards conformance:**
All conformance options are similar -- they issue warnings if non-standard features are used. All defaults are to allow extensions without warnings. The GNU, IBM, and Intel compilers allow multiple standard levels to be specified.
-* **Cray**: The capital "-eN" option specifies to issue error messages for non-compliance rather than warnings.
+* **Cray**: The capital "-eN" option specifies to issue error messages for non-compliance rather than warnings.
* **GNU:** The "std=_level_" option specifies the standard to which the program is expected to conform. The default value for std is 'gnu', which specifies a superset of the latest Fortran standard that includes all of the extensions supported by GNU Fortran, although warnings will be given for obsolete extensions not recommended for use in new code. The 'legacy' value is equivalent but without the warnings for obsolete extensions. The 'f95', 'f2003', 'f2008', and 'f2018' values specify strict conformance to the respective standards. Errors are given for all extensions beyond the relevant language standard, and warnings are given for the Fortran 77 features that are permitted but obsolescent in later standards. '-std=f2008ts' allows the Fortran 2008 standard including the additions of the Technical Specification (TS) 29113 on Further Interoperability of Fortran with C and TS 18508 on Additional Parallel Features in Fortran. Values for "_level_" are f_95, f2003, f2008, f2008ts, f2018, gnu,_ and _legacy._
-**<a name="source"></a>Source format:**
+**<a name="source"></a>Source format:**
**Fixed or free source:** Cray, IBM, and Intel default the source format based on the source file suffix as follows:
@@ -1220,7 +1220,7 @@ IBM Fortran's options allow the source line length to be specified with the opti
* **GNU:** For both "ffixed-line-length-_n_" and "ffree-line-length-_n_" options, characters are ignored after the specified length. The default for fixed is 72. The default for free is 132. For free, you can specify 'none' as the length, which means that all characters in the line are meaningful.
* **IBM:** For **fixed**, the default is 72. For **free**, there's no default, but the maximum length for either form is 132.
* **Intel:** The default is 72 for **fixed** and 132 for **free**.
-* **PGI, Flang:**
+* **PGI, Flang:**
* in free form, it is an error if the line is longer than 1000 characters
* in fixed form by default, characters after column 72 are ignored
* in fixed form with -Mextend, characters after column 132 are ignored
diff --git a/flang/docs/Parsing.md b/flang/docs/Parsing.md
index eae92519c6004..ccc73a1d98524 100644
--- a/flang/docs/Parsing.md
+++ b/flang/docs/Parsing.md
@@ -1,9 +1,9 @@
-<!--===- docs/Parsing.md
-
+<!--===- docs/Parsing.md
+
Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
See https://llvm.org/LICENSE.txt for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-
+
-->
# The Flang Parser
@@ -182,7 +182,7 @@ Parse tree entities should be viewed as values, not objects; their
addresses should not be abused for purposes of identification. They are
assembled with C++ move semantics during parse tree construction.
Their default and copy constructors are deliberately deleted in their
-declarations.
+declarations.
The std::list<> data type is used in the parse tree to reliably store pointers
to other relevant entries in the tree. Since the tree lists are moved and
diff --git a/flang/docs/Preprocessing.md b/flang/docs/Preprocessing.md
index e167922319785..5df07bc125686 100644
--- a/flang/docs/Preprocessing.md
+++ b/flang/docs/Preprocessing.md
@@ -1,9 +1,9 @@
-<!--===- docs/Preprocessing.md
-
+<!--===- docs/Preprocessing.md
+
Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
See https://llvm.org/LICENSE.txt for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-
+
-->
# Fortran Preprocessing
diff --git a/flang/docs/RuntimeDescriptor.md b/flang/docs/RuntimeDescriptor.md
index a2a701a8c02bd..c90bad5d18ee1 100644
--- a/flang/docs/RuntimeDescriptor.md
+++ b/flang/docs/RuntimeDescriptor.md
@@ -1,9 +1,9 @@
-<!--===- docs/RuntimeDescriptor.md
-
+<!--===- docs/RuntimeDescriptor.md
+
Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
See https://llvm.org/LICENSE.txt for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-
+
-->
# Runtime Descriptors
diff --git a/flang/docs/RuntimeTypeInfo.md b/flang/docs/RuntimeTypeInfo.md
index c41a9975c3b9f..16fff4dd563ee 100644
--- a/flang/docs/RuntimeTypeInfo.md
+++ b/flang/docs/RuntimeTypeInfo.md
@@ -1,9 +1,9 @@
-<!--===- docs/RuntimeTypeInfo.md
-
+<!--===- docs/RuntimeTypeInfo.md
+
Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
See https://llvm.org/LICENSE.txt for license information.
SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
-
+
-->
# The derived type runtime information table
More information about the flang-commits
mailing list