cyndyishida wrote: > I think that, in general, silently ignoring options that are not supported is > a disservice to the user in that it misleads them into thinking that some > functionality is there when it is not.
> -F is a darwin specific option in g++ so unless a target platform chooses to > also support this option, it should be flagged as an error. I plan to > introduce code in the future that will flag -F as an error on non-darwin > targets for this reason. @jamieschmeiser This is where I am confused. As far as I can tell, the clang support for respecting `-F` as a search path is not specific to darwin targets (I did a simple test using `-target powerpc64-unknown-linux-gnu` and a compilation that would fail without the search path option provided), so making it an error would remove preexisting functionality. And it's not obvious to me that it is valuable to remove such functionality to be more compatible with gcc. https://github.com/llvm/llvm-project/pull/141614 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
