Re: Automated report: NetBSD-current/i386 build failure

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Sat, 17 Mar 2018 18:48:58 +0000 (UTC)
    From:        NetBSD Test Fixture <bracket%NetBSD.org@localhost>
    Message-ID:  <152131253838.18302.6716002747810327512%babylon5.NetBSD.org@localhost>

  | This is an automatically generated notice of a NetBSD-current/i386
  | build failure.

Once again, after this (totally unrelated) build error, and perhaps after
that was fixed, the following build generated:


--- dependall-gpl3 ---
--- dependall-gcc ---
/tmp/bracket/build/2018.03.17.18.22.23-i386/src/external/gpl3/gcc/dist/gcc/config/i386/sse.md: In function 'int internal_dfa_insn_code_bdver4(rtx_insn*)':
/tmp/bracket/build/2018.03.17.18.22.23-i386/src/external/gpl3/gcc/dist/gcc/config/i386/sse.md:15010:112: error: 're' was not declared in this scope
   [(set (match_operand:V4SI 0 "register_operand" "=Yr,*v")
                                                                                                                ^ 
/tmp/bracket/build/2018.03.17.18.22.23-i386/src/external/gpl3/gcc/dist/gcc/config/i386/sse.md:15010:112: error: expected ')' at end of input
/tmp/bracket/build/2018.03.17.18.22.23-i386/src/external/gpl3/gcc/dist/gcc/config/i386/sse.md:15010:112: error: expected ')' at end of input
/tmp/bracket/build/2018.03.17.18.22.23-i386/src/external/gpl3/gcc/dist/gcc/config/i386/sse.md:15010:112: error: expected ')' at end of input
/tmp/bracket/build/2018.03.17.18.22.23-i386/src/external/gpl3/gcc/dist/gcc/config/i386/sse.md:15010:112: error: expected ')' at end of input
/tmp/bracket/build/2018.03.17.18.22.23-i386/src/external/gpl3/gcc/dist/gcc/config/i386/sse.md:15010:112: error: expected statement at end of input
/tmp/bracket/build/2018.03.17.18.22.23-i386/src/external/gpl3/gcc/dist/gcc/config/i386/sse.md:15010:112: error: expected '}' at end of input
/tmp/bracket/build/2018.03.17.18.22.23-i386/src/external/gpl3/gcc/dist/gcc/config/i386/sse.md:15010:112: error: expected '}' at end of input
--- dependall-gpl3 ---
/tmp/bracket/build/2018.03.17.18.22.23-i386/src/external/gpl3/gcc/dist/gcc/config/i386/sse.md:15010:112: error: control reaches end of non-void function [-Werror=return-type]
   [(set (match_operand:V4SI 0 "register_operand" "=Yr,*v")
                                                                                                                ^ 
cc1plus: all warnings being treated as errors
*** [insn-dfatab.o] Error code 1
nbmake[9]: stopped in /tmp/bracket/build/2018.03.17.18.22.23-i386/src/external/gpl3/gcc/usr.bin/backend


There were no changes I could see that looked in any way as
if they could plausibly affect the gcc build.   And like last time, I
expect this error to be gone in a subsequent build - and still with
no commits that could rationally explain it.

Someone who understands the gcc build process, please look and
see if you can work out what might be happening?

Is the gcc build perhaps corrupting the source directories, and leaving
them in an unclean state if the build gets aborted?   Or perhaps leaving
trash in /tmp that is detected during (and breaks) a later build ?

Something is happening here, and it should not be, and needs to be fixed.

kre

ps: it is hard to be certain if the original (earlier) build error had been corrected
when the failure listed above occurred, as this (more recent) one happens
much earlier during the build process than the other did.