Please advise the clang community if this proposal needs adjustment to be (eventually) adopted by flang. [RFC] Add support for controlling diagnostics severities at file-level granularity through command line.
FYI @klausler
Please advise the clang community if this proposal needs adjustment to be (eventually) adopted by flang. [RFC] Add support for controlling diagnostics severities at file-level granularity through command line.
FYI @klausler
We don’t support -W<warning-name>, our warnings don’t have any identifiers to allow them to be referenced on command line. Are we planning to adopt clang’s diagnostic mechanism in the future?
All optional language features and usage warnings in f18 have names in the compiler (see Fortran-features.h) and can be enabled or disabled by a driver. Further, there’s some APIs there by which a driver can map the name of a feature or warning to its enum if it wants to do so. All warning messages are tagged with their enums, so it would be easy to emit their controlling options as suffixes to the messages.
I don’t know how that relates to whatever is going on in clang.
Ah, indeed. I didn’t realize that. There are still quite a few Say
calls that don’t specify any enums. Maybe we should make it mandatory for warnings?