On Thu, Apr 26, 2018 at 09:56:30AM +0200, Richard Biener wrote:
> On Thu, Apr 26, 2018 at 3:40 AM, David Edelsohn <dje....@gmail.com> wrote:
> > Jakub and Richi,
> >
> > GCC 8.1 is experiencing the same bootstrap failure with GCC 8.1 RC1 as
> > we saw previously.
> >
> > Bootstrap comparison failure!
> > gcc/function-tests.o differs
> >
> > And the same reason: unique, static symbol that includes a random timestamp.
> >
> > 1949c1949
> >
> > < [1936] m 0x00000060 1 1 0x02 0x0000
> >
> > _GLOBAL__F__nasfarm_edelsohn_src_gcc_8.0.1_RC_20180425_gcc_function_tests.c_DFF67DD7_0x4eda2a0ca57bf446
> > ---
> >> [1936] m 0x00000060 1 1 0x02 0x0000
> >> _GLOBAL__F__nasfarm_edelsohn_src_gcc_8.0.1_RC_20180425_gcc_function_tests.c_DFF67DD7_0xbe25963bf76153c
> >
> > The entire file is protected by CHECKING_P. As DEBUG_FUNCTION
> > propagates to more and more header files, this triggers when building
> > without checking.
> >
> > How do you suggest that we try to fix it this time? I'm not certain
> > that we can pull out the one function this time. Should we return to
> > the -frandom-seed patch for self-test files that you proposed last
> > time?
>
> Does
That would be my guess too, but if I try to compile (on x86_64) function-tests.c
with CHECKING_P 0 and put breakpoint on the
*t = ggc_strdup (targetm.strip_name_encoding (IDENTIFIER_POINTER (id)));
line in notice_global_symbol, it is triggered only with _ZNSt9exceptionC2Ev
for weak_global_object_name and nothing else for first_global_object_name.
Jakub
