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

Wed Oct 13 07:10:54 PDT 2021

PeteSteinfeld added a comment.

Thanks for the updates and explanations, Andrzej.

Actually, I do think that end users would find it useful to dump out the symbol table and the parse tree.  This is because Fortran's language definition has aspects that make it possible to create programs that are confusing to look at and interpret -- spaces are not syntactically significant, there are no reserved words, and names can be implicitly declared.  I personally have spent many hours puzzling over Fortran source code, and I routinely dump out the symbol table and parse tree to help me understand what the compiler thinks the program represents.

I'm not so sure about `-fdebug-dump-provenance`.  I rarely use it.

I agree with you that having experimental flags might be useful.  But I don't see why this utility is specific to the frontend.  Might it not also be useful to have experimental flags for the compiler driver?

================
Comment at: flang/docs/FlangDriver.md:45
+specialised tools. In particular, `flang-new` is not aware of various
+compilation phases within the frontend (e.g. scanning, parsing or semantic
+checks). It does not have to. Conversely, the frontend driver, `flang-new
----------------
awarzynski wrote:
> PeteSteinfeld wrote:
> > There is no scanner in the compiler, so I don't think we should mention scanning.
> Would replacing `scanning` with `prescanning & preprocessing` make sense?
I'm not sure what `prescanning` is.  Replacing with `preprocessing` makes sense.

Repository:
  rG LLVM Github Monorepo

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

https://reviews.llvm.org/D111573