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



davidxl <xinliangli at gmail dot com> changed:



           What    |Removed                     |Added

----------------------------------------------------------------------------

                 CC|                            |xinliangli at gmail dot com



--- Comment #1 from davidxl <xinliangli at gmail dot com> 2012-12-04 20:19:48 
UTC ---

google/main branch is not fully tested, and not supposed to be used. Google's

release branches are.



In very near future, lots of cleanups will be done in google/main, and it will

be synced with trunk. During that period, expect it to be very unstable.



David







(In reply to comment #0)

> starting with r172592, google/main fails profiledbootstrap with the error

> below. going one revision back eliminates the error. later commits

> compound/mutate the profiledbootstrap failures; once this bug is fixed, I'll

> retest.

> 

> $ rm -rf *

> 

> $ ../google-main/configure --program-suffix=-google-4.7 --prefix=/u/mhargett

> --enable-languages=c,c++,lto --enable-lto --with-fpmath=sse

> --disable-libmudflap --disable-libssp --enable-build-with-cxx 
> --enable-gold=yes

> --with-mpc=/u/mhargett --with-gmp=/u/mhargett/ --with-mpfr=/u/mhargett/

> --disable-multilib --disable-libgomp --disable-werror

> 

> $ make -j1 profiledbootstrap

> 

> if [ x"-fpic" != x ]; then \

>       /work/mhargett/google-main-obj/./prev-gcc/xgcc

> -B/work/mhargett/google-main-obj/./prev-gcc/

> -B/u/mhargett/x86_64-unknown-linux-gnu/bin/

> -B/u/mhargett/x86_64-unknown-linux-gnu/bin/

> -B/u/mhargett/x86_64-unknown-linux-gnu/lib/ -isystem

> /u/mhargett/x86_64-unknown-linux-gnu/include -isystem

> /u/mhargett/x86_64-unknown-linux-gnu/sys-include    -c -DHAVE_CONFIG_H -g -O2

> -fprofile-use  -I. -I../../google-main/libiberty/../include  -W -Wall

> -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic  -fpic

> ../../google-main/libiberty/cp-demangle.c -o pic/cp-demangle.o; \

>     else true; fi

> ../../google-main/libiberty/cp-demangle.c: In function

> \u2018is_ctor_or_dtor\u2019:

> ../../google-main/libiberty/cp-demangle.c:5172:1: error: coverage mismatch for

> function \u2018is_ctor_or_dtor\u2019 while reading counter \u2018arcs\u2019

> [-Werror=coverage-mismatch]

> ../../google-main/libiberty/cp-demangle.c:5172:1: note: number of counters is 
> 7

> instead of 8

> ../../google-main/libiberty/cp-demangle.c: In function

> \u2018d_demangle_callback\u2019:

> ../../google-main/libiberty/cp-demangle.c:5172:1: error: coverage mismatch for

> function \u2018d_demangle_callback\u2019 while reading counter 
> \u2018arcs\u2019

> [-Werror=coverage-mismatch]

> ../../google-main/libiberty/cp-demangle.c:5172:1: note: number of counters is

> 25 instead of 26

> ../../google-main/libiberty/cp-demangle.c: In function

> \u2018d_ctor_dtor_name\u2019:

> ../../google-main/libiberty/cp-demangle.c:5172:1: error: coverage mismatch for

> function \u2018d_ctor_dtor_name\u2019 while reading counter \u2018arcs\u2019

> [-Werror=coverage-mismatch]

> ../../google-main/libiberty/cp-demangle.c:5172:1: note: number of counters is

> 20 instead of 18

> ../../google-main/libiberty/cp-demangle.c: In function

> \u2018d_operator_name\u2019:

> ../../google-main/libiberty/cp-demangle.c:5172:1: error: coverage mismatch for

> function \u2018d_operator_name\u2019 while reading counter \u2018arcs\u2019

> [-Werror=coverage-mismatch]

> ../../google-main/libiberty/cp-demangle.c:5172:1: note: number of counters is

> 21 instead of 20

> ../../google-main/libiberty/cp-demangle.c: In function 
> \u2018d_make_name\u2019:

> ../../google-main/libiberty/cp-demangle.c:5172:1: error: coverage mismatch for

> function \u2018d_make_name\u2019 while reading counter \u2018arcs\u2019

> [-Werror=coverage-mismatch]

> ../../google-main/libiberty/cp-demangle.c:5172:1: note: number of counters is 
> 5

> instead of 4

> cc1: some warnings being treated as errors

Reply via email to