https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79956
--- Comment #38 from rguenther at suse dot de <rguenther at suse dot de> --- On Tue, 21 Mar 2017, marxin at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79956 > > --- Comment #37 from Martin Liška <marxin at gcc dot gnu.org> --- > (In reply to rguent...@suse.de from comment #8) > > On March 8, 2017 4:43:05 PM GMT+01:00, "marxin at gcc dot gnu.org" > > <gcc-bugzi...@gcc.gnu.org> wrote: > > >https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79956 > > > > > >--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> --- > > >I can also see profiledbootstrap failure in: > > > > > >.././../gcc/simplify-rtx.c:6021:12: error: ‘result_s’ may be used > > >uninitialized > > >in this function [-Werror=maybe-uninitialized] > > > return result_s; > > > ^~~~~~~~ > > > > > >It worked with a revision from 3.3.2017, is it the same issue as seen > > >by > > >Markus? > > > > I've run into this as well but it's slightly non reproducible (repeating the > > compile command sometimes works, sometimes not). From analyzing it looked > > similar and/or threading related. > > > > Richard. > > Good, after couple builds it popped up again. Would it be fine to initialize > the variable to NULL to prevent it? Yes, fine with me.
