search for: diagnosticengin

...he code-base) : Diag(ImmLoc, err_arm_invalid_immediate_shift); and pass through LLVMDiagnosticsEngine to get the diagnostic message and severity (defined in TableGen, similar to Diagnostic*Kinds.td in clang). Initially, LLVMDiagnosticsEngine will be a smaller, simpler version of clang's DiagnosticEngine. Over time, I would expect more features of clang's diagnostics to migrate to LLVM, where possible, to improve diagnostics for all the LLVM tools. I intend to implement the necessary infrastructure and convert a (small) number of diagnostics. Further conversions can be done incrementally....

...). Clang's frontend driver (CompilerInvocation, CompilerInstance and `clang -cc1` in general) should remain in Clang. Later we can decide that there are some commonalities that can be shared, but these are expected to be relatively small. In terms of the infra code, libclangDriver requires DiagnosticEngine, which contains SourceManager and also requires SourceLocation. This would suggest the following steps. 1a. Generalize SourceManager so that it's suitable for both Clang and Flang 1b. Move the updated SourceManager, together with SLocEntry, SourceLocation, FileManager, VFS to `frontend-supp...

On Tue, Jun 2, 2020 at 6:38 PM Richard Smith via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Tue, 2 Jun 2020 at 05:08, Andrzej Warzynski via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > >> *TL;DR* >> >> We propose some non-trivial refactoring in Clang and LLVM to enable >> further work on Flang driver. >> >> *SUMMARY* >> We