================ @@ -380,6 +380,9 @@ def pp_nonportable_path : NonportablePath, InGroup<DiagGroup<"nonportable-include-path">>; def pp_nonportable_system_path : NonportablePath, DefaultIgnore, InGroup<DiagGroup<"nonportable-system-include-path">>; +def pp_nonportable_path_separator : Warning< + "non-portable path to file '%0'; specified path contains backslashes">, + DefaultIgnore, InGroup<DiagGroup<"nonportable-include-path-separator">>; ---------------- rosefromthedead wrote:
I don't think it should necessarily be on by default for non-Windows targets, as these cases can still exclusively use Windows hosts. And especially because the more complex defaults logic would be tricky to express, I'm happy with the current state. Am I right to think that if nonportable-include-path-separator is always off by default, there's no use in tying it to nonportable-include-path? (I'm not familiar with this, but I saw that DiagGroups can have subgroups and I guess that's what you mean?) https://github.com/llvm/llvm-project/pull/186770 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
