------- Comment #4 from patriciak784-gccmainling at yahoo dot de 2008-09-04 16:38 ------- Now I know why gcc complains about a misformed pch file nul.gch! Checking if a file named NUL plus any extension exists, will always return that it exists because I did this on windows! open will not open a file on the disk but the NUL device which is the same as /dev/null on *nix. And of course nul.gch is no valid pch!
So this warning is a windows specific "bug" but I don't think it is necessary to provide a workaround in gcc as long as this doesn't break anything which is the case at least for me. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37215
