search for: slocentry

...ms 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-support` (i.e. the new location for the common driver code) 2a. Split the diagnostics into separate namespaces so there's proper layering of various groups 2b. Move TableGen backend for diagnostics to `frontend-support`. The definitions specifi...

...at can be extracted, > with some significant work done to generalize the SourceManager > infrastructure and make it tailorable to the needs of Clang and Flang (and > any other consumers of it that might come along). I could imagine moving > all of the complexity to do with what kinds of SLocEntry are supported into > a traits type, and having a reusable template that can generate a data > structure that the Clang and Flang SourceManagers can be implemented in > terms of. > > Clang's SourceLocation is probably almost directly useable as-is -- it has > hardcoded assumpti...

*TL;DR* We propose some non-trivial refactoring in Clang and LLVM to enable further work on Flang driver. *SUMMARY* We would like to start extracting the driver/frontend code from Clang (alongside the code that the driver/frontend depends on, e.g. Diagnostics) and move the components that could be re-used by non-C-based languages to LLVM. From our initial investigation we see that these