[Bug bootstrap/65150] [5 Regression] r220875 causes bootstrap failure on x86_64 darwin

[iains at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65150

--- Comment #21 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #20)
> Created attachment 34864 [details]
> icfmerge2
> 
> Updated version to apply after Jakub's patch

this bootstraps on x86_64-darwin12, and powerpc-darwin9 (at least).

in addition to new test failures seen with previous patches (FAIL:
gcc.dg/attr-noinline.c, FAIL: gcc.dg/ipa/iinline-5.c scan-ipa-dump-not inline
"wrong_target[^\\\\n]*inline copy in")

we also see :
FAIL: g++.dg/warn/Wsuggest-final.C  -std=gnu++11  (test for warnings, line 3)
(also, as expected, for c++98, c++14)

== looks like:

GCC/gcc-trunk/gcc/testsuite/g++.dg/warn/Wsuggest-final.C:3:8: warning:
Declaring type 'struct A' final would enable devirtualization of 2 calls
[-Wsuggest-final-types]
/GCC/gcc-trunk/gcc/testsuite/g++.dg/warn/Wsuggest-final.C:5:15: warning:
Declaring method 'virtual void A::b()' final would enable devirtualization of 2
calls [-Wsuggest-final-methods]
output is:
/GCC/gcc-trunk/gcc/testsuite/g++.dg/warn/Wsuggest-final.C:3:8: warning:
Declaring type 'struct A' final would enable devirtualization of 2 calls
[-Wsuggest-final-types]
/GCC/gcc-trunk/gcc/testsuite/g++.dg/warn/Wsuggest-final.C:5:15: warning:
Declaring method 'virtual void A::b()' final would enable devirtualization of 2
calls [-Wsuggest-final-methods]

FAIL: g++.dg/warn/Wsuggest-final.C  -std=gnu++11  (test for warnings, line 3)
FAIL: g++.dg/warn/Wsuggest-final.C  -std=gnu++11  (test for warnings, line 4)
PASS: g++.dg/warn/Wsuggest-final.C  -std=gnu++11  (test for warnings, line 5)
FAIL: g++.dg/warn/Wsuggest-final.C  -std=gnu++11 (test for excess errors)
Excess errors:
/GCC/gcc-trunk/gcc/testsuite/g++.dg/warn/Wsuggest-final.C:3:8: warning:
Declaring type 'struct A' final would enable devirtualization of 2 calls
[-Wsuggest-final-types]

==

there might be possibly be other related [C] fails - it's actually tricky to
get a clean baseline, since this PR is caused by a fix to a related one.