History

Tim Keith 16356d58bc [flang] Allow forward reference to binding name in type-bound generic Type-bound generic statements can have binding names that refer to bindings that occur later in the type. So save a map of generic to binding names and process them when we get to the end of the type-bound procedure part. This is similar to how specific procedures of generic identifiers are handled. Also detect duplicate binding names for a type-bound generic. Fixes issue flang-compiler/f18#572. Original-commit: flang-compiler/f18@d58bb77cfa Reviewed-on: https://github.com/flang-compiler/f18/pull/577		2019-07-15 17:09:03 -07:00
..
documentation	[flang] Complete source provenance on OMP constructs (except ATOMIC)	2019-07-15 13:05:29 -07:00
include/flang	[flang] address comments	2019-03-11 11:33:54 -07:00
lib	[flang] Allow forward reference to binding name in type-bound generic	2019-07-15 17:09:03 -07:00
module	[flang] Use LOC() in iso_c_binding for C_LOC and C_FUNLOC	2019-07-01 16:54:53 -07:00
runtime	[flang] Missed a fortran.h instance	2019-02-28 11:48:16 -08:00
test	[flang] Allow forward reference to binding name in type-bound generic	2019-07-15 17:09:03 -07:00
tools	[flang] Add -fxor-operator	2019-07-10 16:42:10 -07:00
.clang-format	[flang] Changed .clang-format so that it will not add a comment after the closing brace of each namespace. Removed all such previous comments from all .cc and .h files	2018-10-25 05:55:23 -07:00
.gitignore	[flang] Clause 13 (Input/output editing) syntax and semantic checking (flang-compiler/f18#498 )	2019-06-25 15:59:30 -07:00
CMakeLists.txt	[flang] -fno-exceptions	2019-06-18 14:11:55 -07:00
LICENSE	[flang] Create LICENSE	2018-05-18 13:06:22 -07:00
README.md	[flang] Reorder the advice about putting GCC bin and lib on	2019-03-20 14:09:35 -07:00

README.md

F18

F18 is a ground-up implementation of a Fortran front end written in modern C++. F18, when combined with LLVM, is intended to replace the Flang compiler.

Flang is a Fortran compiler targeting LLVM. Visit the Flang wiki for more information about Flang.

Getting Started

Read more about f18 in the documentation directory. Start with the compiler overview.

To better understand Fortran as a language and the specific grammar accepted by f18, read Fortran For C Programmers and f18's specifications of the Fortran grammar and the OpenMP grammar.

Treatment of language extensions is covered in this document.

To understand the compilers handling of intrinsics, see the discussion of intrinsics.

To understand how an f18 program communicates with libraries at runtime, see the discussion of runtime descriptors.

If you're interested in contributing to the compiler, read the style guide and also review how f18 uses modern C++ features.

Building F18

Get the Source Code

cd where/you/want/the/source
git clone https://github.com/flang-compiler/f18.git

Supported C++ compilers

F18 is written in C++17.

The code has been compiled and tested with GCC versions 7.2.0, 7.3.0, 8.1.0, and 8.2.0.

The code has been compiled and tested with clang version 7.0 and 8.0 using either GNU's libstdc++ or LLVM's libc++.

LLVM dependency

F18 uses components from LLVM.

The instructions to build LLVM can be found at https://llvm.org/docs/GettingStarted.html.

We highly recommend using the same compiler to compile both llvm and f18.

The f18 CMakeList.txt file uses the variable LLVM_DIR to find the installed components.

To get the correct LLVM libraries included in your f18 build, define LLVM_DIR on the cmake command line.

LLVM=<LLVM_INSTALLATION_DIR>/lib/cmake/llvm cmake -DLLVM_DIR=$LLVM ...

where LLVM_INSTALLATION_DIR is the top-level directory where llvm is installed.

Building f18 with GCC

By default, cmake will search for g++ on your PATH. The g++ version must be one of the supported versions in order to build f18.

Or, cmake will use the variable CXX to find the C++ compiler. CXX should include the full path to the compiler or a name that will be found on your PATH, e.g. g++-7.2, assuming g++-7.2 is on your PATH.

export CXX=g++-7.2

CXX=/opt/gcc-7.2/bin/g++-7.2 cmake ...

There's a third option! The CMakeList.txt file uses the variable GCC as the path to the bin directory containing the C++ compiler.

GCC can be defined on the cmake command line where <GCC_DIRECTORY> is the path to a GCC installation with bin, lib, etc:

cmake -DGCC=<GCC_DIRECTORY> ...

Building f18 with clang

To build f18 with clang, cmake needs to know how to find clang++ and the GCC library and tools that were used to build clang++.

The CMakeList.txt file expects either CXX or BUILD_WITH_CLANG to be set.

CXX should include the full path to clang++ or clang++ should be found on your PATH.

export CXX=clang++

BUILD_WITH_CLANG can be defined on the cmake command line where <CLANG_DIRECTORY> is the path to a clang installation with bin, lib, etc:

cmake -DBUILD_WITH_CLANG=<CLANG_DIRECTORY>

Or GCC can be defined on the f18 cmake command line where <GCC_DIRECTORY> is the path to a GCC installation with bin, lib, etc:

cmake -DGCC=<GCC_DIRECTORY> ...

To use f18 after it is built, the environment variables PATH and LD_LIBRARY_PATH must be set to use GCC and its associated libraries.

Installation Directory

To specify a custom install location, add -DCMAKE_INSTALL_PREFIX=<INSTALL_PREFIX> to the cmake command where <INSTALL_PREFIX> is the path where f18 should be installed.

Build Types

To create a debug build, add -DCMAKE_BUILD_TYPE=Debug to the cmake command. Debug builds execute slowly.

To create a release build, add -DCMAKE_BUILD_TYPE=Release to the cmake command. Release builds execute quickly.

Build F18

cd ~/f18/build
cmake -DLLVM_DIR=$LLVM ~/f18/src
make