[Flang][NFC] Remove license comments from files in docs/ folder.

[sameeranjoshi]

Summary

Solves issue https://reviews.llvm.org/D86131#2247275

[hans]

lgtm

[sscalpone]

Why?

[sameeranjoshi]

In D86875#2247465, @sscalpone wrote:

Why?

Solves issue https://reviews.llvm.org/D86131#2247275

[klausler]

In D86875#2247476, @sameeranjoshi wrote:

In D86875#2247465, @sscalpone wrote:

Why?

Solves issue https://reviews.llvm.org/D86131#2247275

Has this change altered the license under which these documentation files were donated to LLVM?

[sscalpone]

@sameeranjoshi Please consider fixing this issue in the conversion tool (maybe commonmark.py) & propagating the fix to llvm.org?

[hans]

In D86875#2247593, @sscalpone wrote:

@sameeranjoshi Please consider fixing this issue in the conversion tool (maybe commonmark.py) & propagating the fix to llvm.org?

Markdown doesn't really support comments. Other LLVM docs don't have this kind of headers.

In D86875#2247549, @klausler wrote:

Has this change altered the license under which these documentation files were donated to LLVM?

I'm not a lawyer obviously, but I wouldn't think that this alters anything.

[SouraVX]

Revereted!
Thanks!

[hans]

Cherrty-picked the revert to 11.x as 8ae3293030d9691ebe0006b79cec1b06bb8015cf

flang/docs/ArrayComposition.md

-<!--===- docs/ArrayComposition.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
-  
--->
-
 This note attempts to describe the motivation for and design of an
 implementation of Fortran 90 (and later) array expression evaluation that
 minimizes the use of dynamically allocated temporary storage for
 the results of calls to transformational intrinsic functions, and
 making them more amenable to acceleration.
 
 The transformational intrinsic functions of Fortran of interest to
 us here include:

flang/docs/C++17.md

-<!--===- docs/C++17.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
-  
--->
-
 ## C++14/17 features used in f18
 
 The C++ dialect used in this project constitutes a subset of the
 standard C++ programming language and library features.
 We want our dialect to be compatible with the LLVM C++ language
 subset that will be in use at the time that we integrate with that
 project.
 We also want to maximize portability, future-proofing,

flang/docs/C++style.md

-<!--===- docs/C++style.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
-  
--->
-
 ## In brief:
 * Use *clang-format*
 from llvm 7
 on all C++ source and header files before
 every merge to master.  All code layout should be determined
 by means of clang-format.
 * Where a clear precedent exists in the project, follow it.
 * Otherwise, where [LLVM's C++ style guide](https://llvm.org/docs/CodingStandards.html#style-issues)

flang/docs/Calls.md

-<!--===- docs/Calls.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
-
--->
-
 ## Procedure reference implementation protocol
 
 Fortran function and subroutine references are complicated.
 This document attempts to collect the requirements imposed by the 2018
 standard (and legacy extensions) on programs and implementations, work
 through the implications of the various features, and propose both a
 runtime model and a compiler design.
 

flang/docs/Character.md

-<!--===- docs/Character.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
-
--->
-
 ## Implementation of `CHARACTER` types in f18
 
 ### Kinds and Character Sets
 
 The f18 compiler and runtime support three kinds of the intrinsic
 `CHARACTER` type of Fortran 2018.
 The default (`CHARACTER(KIND=1)`) holds 8-bit character codes;
 `CHARACTER(KIND=2)` holds 16-bit character codes;

flang/docs/ControlFlowGraph.md

-<!--===- docs/ControlFlowGraph.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
-  
--->
-
 ## Concept
 After a Fortran subprogram has been parsed, its names resolved, and all its
 semantic constraints successfully checked, the parse tree of its
 executable part is translated into another abstract representation,
 namely the _control flow graph_ described in this note.
 
 This second representation of the subprogram's executable part is
 suitable for analysis and incremental modification as the subprogram

flang/docs/Directives.md

-<!--===- docs/Directives.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 directives supported by F18
 ====================================
 
 * `!dir$ fixed` and `!dir$ free` select Fortran source forms.  Their effect
   persists to the end of the current source file.
 * `!dir$ ignore_tkr (tkr) var-list` omits checks on type, kind, and/or rank.

flang/docs/Extensions.md

-<!--===- docs/Extensions.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
-  
--->
-
 As a general principle, this compiler will accept by default and
 without complaint many legacy features, extensions to the standard
 language, and features that have been deleted from the standard,
 so long as the recognition of those features would not cause a
 standard-conforming program to be rejected or misinterpreted.
 
 Other non-standard features, which do conflict with the current
 standard specification of the Fortran programming language, are

flang/docs/FortranForCProgrammers.md

-<!--===- docs/FortranForCProgrammers.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 For C Programmers
 =========================
 
 This note is limited to essential information about Fortran so that
 a C or C++ programmer can get started more quickly with the language,
 at least as a reader, and avoid some common pitfalls when starting
 to write or modify Fortran code.
 Please see other sources to learn about Fortran's rich history,

flang/docs/FortranIR.md

-<!--===- docs/FortranIR.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
-  
--->
-
 # Design: Fortran IR
 
 ## Introduction
 
 After semantic analysis is complete and it has been determined that the compiler has a legal Fortran program as input, the parse tree will be lowered to an intermediate representation for the purposes of high-level analysis and optimization.  In this document, that intermediate representation will be called Fortran IR or FIR.  The pass that converts from the parse tree and other data structures of the front-end to FIR will be called the "Burnside bridge".
 
 FIR will be an explicit, operational, and strongly-typed representation, which shall encapsulate control-flow as graphs.
 

flang/docs/IORuntimeInternals.md

-<!--===- docs/IORuntimeInternals.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 I/O Runtime Library Internal Design
 ===========================================
 
 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.
 
 The *interface* to the I/O runtime support library is defined in the
 C++ header file `runtime/io-api.h`.

flang/docs/ImplementingASemanticCheck.md

-<!--===- docs/ImplementingASemanticCheck.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
-  
--->
-# Introduction
 I recently added a semantic check to the f18 compiler front end.  This document
 describes my thought process and the resulting implementation.
 
 For more information about the compiler, start with the 
 [compiler overview](Overview.md).
 
 # Problem definition
 

flang/docs/Intrinsics.md

-<!--===- docs/Intrinsics.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
-  
--->
-
 # A categorization of standard (2018) and extended Fortran intrinsic procedures
 
 This note attempts to group the intrinsic procedures of Fortran into categories
 of functions or subroutines with similar interfaces as an aid to
 comprehension beyond that which might be gained from the standard's
 alphabetical list.
 
 A brief status of intrinsic procedure support in f18 is also given at the end.

flang/docs/LabelResolution.md

-<!--===- docs/LabelResolution.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
-  
--->
-
 # Semantics: Resolving Labels and Construct Names
 
 ## Overview
 
 After the Fortran input file(s) has been parsed into a syntax tree, the compiler must check that the program checks semantically.  Target labels must be checked and violations of legal semantics should be reported to the user.
 
 This is the detailed design document on how these labels will be semantically checked.  Legal semantics may result in rewrite operations on the syntax tree.  Semantics violations will be reported as errors to the user.
 

flang/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
 
 Module files hold information from a module that is necessary to compile 
 program units that depend on the module.
 
 ## Name
 
 Module files must be searchable by module name. They are typically named

flang/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
 
 ## OpenMP for F18
 
 1. Define and document the parse tree representation for
     * Directives (listed below)
     * Clauses (listed below)
     * Documentation

flang/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
 
 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 [notes on Standards conformance](#standards).
 
 **There's also important information in the ___[Notes section](#notes)___ 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.
 

flang/docs/Overview.md

-<!--===- docs/Overview.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
-  
--->
-
 # Overview of Compiler Phases
 
 Each phase produces either correct output or fatal errors.
 
 ## Prescan and Preprocess
 
 See: [Preprocessing.md](Preprocessing.md).
 

flang/docs/ParserCombinators.md

-<!--===- docs/ParserCombinators.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
-  
--->
-
 ## Concept
 The Fortran language recognizer here can be classified as an LL recursive
 descent parser.  It is composed from a *parser combinator* library that
 defines a few fundamental parsers and a few ways to compose them into more
 powerful parsers.
 
 For our purposes here, a *parser* is any object that attempts to recognize
 an instance of some syntax from an input stream.  It may succeed or fail.

flang/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
 ==============
 This program source code implements a parser for the Fortran programming
 language.
 
 The draft ISO standard for Fortran 2018 dated July 2017 was used as the
 primary definition of the language.  The parser also accepts many features
 from previous versions of the standard that are no longer part of the Fortran

flang/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
 =====================
 
 Behavior common to (nearly) all compilers:
 ------------------------------------------
 * Macro and argument names are sensitive to case.
 * Fixed form right margin clipping after column 72 (or 132)
   has precedence over macro name recognition, and also over

flang/docs/PullRequestChecklist.md

-<!--===- docs/PullRequestChecklist.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
-
--->
-
 # Pull request checklist
 Please review the following items before submitting a pull request.  This list
 can also be used when reviewing pull requests.
 *  Verify that new files have a license with correct file name.
 *  Run `git diff` on all modified files to look for spurious changes such as
    `#include <iostream>`.
 *  If you added code that causes the compiler to emit a new error message, make
    sure that you also added a test that causes that error message to appear

flang/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
-  
--->
-
 ## Concept
 The properties that characterize data values and objects in Fortran
 programs must sometimes be materialized when the program runs.
 
 Some properties are known during compilation and constant during
 execution, yet must be reified anyway for execution in order to
 drive the interfaces of a language support library or the mandated
 interfaces of interoperable (i.e., C) procedure calls.

flang/docs/Semantics.md

-<!--===- docs/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
-  
--->
-
 # Semantic Analysis
 
 The semantic analysis pass determines if a syntactically correct Fortran
 program is is legal by enforcing the constraints of the language.
 
 The input is a parse tree with a `Program` node at the root;
 and a "cooked" character stream, a contiguous stream of characters
 containing a normalized form of the Fortran source.