[PATCH] D111573: [Flang][driver] Update docs

Andrzej Warzynski via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Tue Oct 12 05:14:29 PDT 2021


awarzynski added inline comments.


================
Comment at: flang/docs/FlangDriver.md:54
+* the compiler driver is an end-user tool
+* frontend-driver is a compiler developer tool with many additional options,
+
----------------
tschuett wrote:
> It is easier to understand, if talk about the driver and the frontend. frontend-driver is misleading.
"frontend" can  mean different things, though. For somebody from e.g. llvm-project/llvm (i.e. people working on the backend), probably both "llvm-project/clang" and "llvm-project/flang" are frontends (i.e. the entire sub-projects, with all the libraries and tools). For an "llvm-project/{flang|clang}" developer, it's probably just the core libraries (e.g. `clangSema`, `clangParse`, `FortranParser` or `FortranSemantics`).

I think that both perspectives are correct and simply depend on the point of reference. But it means that the term is ambiguous and I try to be careful about the context in which it is used. Also, "frontend" or "frontend tool"? The latter is more accurate (indeed, it's just a tool), but then which "frontend tool" does it refer to? There's already `flang-new`, `flang-new -fc1`, `tco`, `bbc`.

I really appreciate the suggestion! This is tricky. To me, "frontend driver" makes a lot of sense (i.e. it drives the frontend libraries), but I'm biased. Let's wait and see what others think!


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D111573/new/

https://reviews.llvm.org/D111573



More information about the llvm-commits mailing list