`-Wno-nonportable-include-path` has no effect

[llvmbot]

Bugzilla Link	28813
Version	trunk
OS	All
Reporter	LLVM Bugzilla Contributor
CC	@DougGregor,@pogo59

Extended Description

When compiling any c++ file where the include statement has the wrong case for a local header file passing the argument -Wno-nonportable-include-path to the compiler command line doesn't suppress the warnings, warning: non-portable path to file...

[pogo59]

That's very peculiar, because we have locally set this warning to
DefaultIgnore and that works perfectly. Also I just tried using
-Wno-nonportable-include-path with r277322 and it worked fine.

Are you possibly putting -Wall after the -Wno-nonportable-include-path?

If you provide an exact example where you are seeing this behavior,
that will help work out what is going on.

[llvmbot]

It's definitely put after -Wall. -Wall is near the beginning of the command line.

I'm trying to recreate it in a simple example, but I can't.

I'm wondering if it has something to do with case issues in a -I... argument in the command line.

We have a product that we like to compile in clang occasionally because of it's far superior warnings to Visual Studio's compiler. However, it's got about 2000 cpp files and a very complicated make system.

[AaronBallman]

I cannot reproduce this issue, so closing as worksforme. If the issue still persists, please reopen with instructions on how to reproduce.