------- Comment #43 from janis at gcc dot gnu dot org 2009-01-29 22:36 ------- Rob, your various assertions do not show that there is a bug here. The failure of gcc.target/i386/funcspec-3.c described in comment #41 does not prove that the compiler under test is using GCC files from the install tree. I think it's either an intermittent failure or some problem with running the testsuite where you've already run them. In particular, that test doesn't appear to use any files that are in $(libdir)/gcc/, it's a compile-only test and cc1 is not in that part of the installation. The assertion in comment #37 that "GCC_EXEC_PREFIX is simply always set" is not true; it is only being set within the testsuite and from the Makefile as part of an invocation of runtest. The others don't make much sense, either.
I built GCC from 20090106, broke a couple of thing affecting cc1, float.h, and libgcc.a, and installed it. Then I configured current mainline to use the same installation location, built it, and ran the tests affected the what I broke; they all passed. I added a test to print the value of GCC_EXEC_PREFIX and it confirmed that it was set. It does NOT affect the use of the compiler under test. Once again, the use of -B in the testsuite overrides GCC_EXEC_PREFIX for files that are part of GCC. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36443
