[Bug bootstrap/55051] [4.8 Regression] profiledbootstrap failed

["hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55051

--- Comment #15 from Jan Hubicka <hubicka at gcc dot gnu.org> 2012-11-15 01:10:29 UTC ---
Note that profiledbootstrap still dies for me on
config.status: creating tests/rand/Makefile
../../libiberty/cp-demangle.c: In function 'd_print_cast.isra.8':
../../libiberty/cp-demangle.c:5642:1: error: the control flow of function
'd_print_cast.isra.8' does not match its profile data (counter 'arcs')
[-Werror=coverage-mismatch]
 }
 ^
../../libiberty/cp-demangle.c:5642:1: note: use -Wno-error=coverage-mismatch to
tolerate the mismatch but performance may drop if the function is hot
../../libiberty/cp-demangle.c: In function 'd_print_function_type.isra.7':
../../libiberty/cp-demangle.c:5642:1: error: the control flow of function
'd_print_function_type.isra.7' does not match its profile data (counter 'arcs')
[-Werror=coverage-mismatch]
../../libiberty/cp-demangle.c:5642:1: note: use -Wno-error=coverage-mismatch to
tolerate the mismatch but performance may drop if the function is hot
../../libiberty/cp-demangle.c: In function 'd_print_array_type.isra.6':
../../libiberty/cp-demangle.c:5642:1: error: the control flow of function
'd_print_array_type.isra.6' does not match its profile data (counter 'arcs')
[-Werror=coverage-mismatch]
../../libiberty/cp-demangle.c:5642:1: note: use -Wno-error=coverage-mismatch to
tolerate the mismatch but performance may drop if the function is hot
../../libiberty/cp-demangle.c: In function 'd_lookup_template_argument.isra.5':
../../libiberty/cp-demangle.c:5642:1: error: the control flow of function
'd_lookup_template_argument.isra.5' does not match its profile data (counter
'arcs') [-Werror=coverage-mismatch]
../../libiberty/cp-demangle.c:5642:1: note: use -Wno-error=coverage-mismatch to
tolerate the mismatch but performance may drop if the function is hot
../../libiberty/cp-demangle.c: In function 'd_number.isra.0':


I am unsure if this is bug in profile code or different configuration of
libberty...