------- Comment #13 from kristiaan dot lenaerts at gmail dot com 2010-06-04 20:10 ------- Created an attachment (id=20847) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20847&action=view) Updated fix for improper PCH dependency tracking
I got hit by this bug a few weeks ago when working on a C++ project. This project has a setup for which using -fpch-deps will not work, most pch files include local headers that have to be referenced by their complete path elsewhere. I rebased the proposed fix from Mario on the 4.5 branch (I created it when 4.5 was not yet out). I'm using this patch for about a month now without any obvious problems, but I would like to get this in mainline. What are the steps that I should take? I have not yet run the testsuite. (this is on a corporate laptop running under cygwin - windows XP and full hd-encryption - so compiling gcc was painfull, and I imagine running the testsuite will be worse) Would it be ok if I run the testsuite on cygwin with and without the patch, and if the results are the same submit this patch to gcc-patches (with meaningfull changelog entry)? I could also test on a x64_64-pc-linux-gnu machine at home, but it could take a while before I can test there. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14933
