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

--- Comment #23 from Teresa Johnson <tejohnson at google dot com> ---
On Tue, Nov 12, 2013 at 11:06 AM, ubizjak at gmail dot com
<gcc-bugzi...@gcc.gnu.org> wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58862
>
> --- Comment #22 from Uroš Bizjak <ubizjak at gmail dot com> ---
> (In reply to Teresa Johnson from comment #19)
>
>> Since this was blocking my SPEC testing I took a look. The issue is
>> that the new edge_count variable is declared as an int and is
>> overflowing. It should be gcov_type. Here is the patch that fixed the
>> bzip2 failure. I will run regression and lto bootstrap testing on it:
>
> You will need additional patch to libiberty to push the lto-profiledbootstrap
> further.
>
> Unfortunately, the lto profiledbootstrap will later die in stagefeedback with:
>
>   /ssd/uros/gcc-build-profiled/./prev-gcc/xgcc
> -B/ssd/uros/gcc-build-profiled/./prev-gcc/
> -B/usr/local/x86_64-unknown-linux-gnu/bin/
> -B/usr/local/x86_64-unknown-linux-gnu/bin/
> -B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem
> /usr/local/x86_64-unknown-linux-gnu/include -isystem
> /usr/local/x86_64-unknown-linux-gnu/sys-include    -c -DHAVE_CONFIG_H -g -O2
> -flto=jobserver -frandom-seed=1 -fprofile-use  -I.
> -I/home/uros/gcc-svn/trunk/libiberty/../include  -W -Wall -Wwrite-strings
> -Wc++-compat -Wstrict-prototypes -pedantic  -fpic
> /home/uros/gcc-svn/trunk/libiberty/pex-unix.c -o pic/pex-unix.o; \
> else true; fi
> if [ x"-fpic" != x ]; then \
> /home/uros/gcc-svn/trunk/libiberty/pex-unix.c:790:1: error: Missing counts for
> called function pex_child_error.isra.1/75
>  }
>  ^
> gmake[3]: *** [pex-unix.o] Error 1
> gmake[3]: *** Waiting for unfinished jobs....
> gmake[2]: *** [all-stagefeedback-libiberty] Error 2
> gmake[2]: *** Waiting for unfinished jobs....
> gmake[2]: Leaving directory `/ssd/uros/gcc-build-profiled'
> gmake[1]: *** [stagefeedback-bubble] Error 2
> gmake[1]: Leaving directory `/ssd/uros/gcc-build-profiled'
> gmake: *** [profiledbootstrap] Error 2

Yep, I just hit this myself while testing the badness overflow fix. It
is due to my own patch and I just sent a fix to gcc-patches for it -
this should be made into a warning for now.

Teresa

>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

Reply via email to