------- Comment #7 from amylaar at gcc dot gnu dot org 2010-07-11 01:58 ------- (In reply to comment #6) > This still looks broken. Under a normal bootstrap, on x86_64-apple-darwin10, > these new testcases are silently executed against the system compiler rather > than the newly built compiler...
I see. We really should be using the same BUILD->HOST compiler that was used to build the last stage of the build. In the case of a native bootstrap (assuming stage2/3 comparison succeeded), that should be interchangeable with the newly built compiler. Feel free to re-open the PR; I have no plans to work on it, though. > /Users/howarth/gcc/gcc/testsuite/g++.dg/plugin/attribute_plugin.c: In function > 'void register_attributes(void*, void*)':^M > /Users/howarth/gcc/gcc/testsuite/g++.dg/plugin/attribute_plugin.c:35: error: > 'warning' was not declared in this scope^M > /Users/howarth/gcc/gcc/testsuite/g++.dg/plugin/attribute_plugin.c: In function > 'void handle_pre_generic(void*, void*)':^M > /Users/howarth/gcc/gcc/testsuite/g++.dg/plugin/attribute_plugin.c:55: error: > 'warning' was not declared in this scope^M Looking at the source makes me wonder why it succeeds elsewhere. It should be including diagnostic.h or disgnostic-core.h to get a declaration for warning. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42843
