gcc issue building -current

[Martin Husemann <martin%duskware.de@localhost>]

Hey folks,

I can't cross build -current VAX (from a -current amd64 machine), it
dies with an internal gcc error trying to build lint. The tools build of
lint works, but the vax build fails:

dependall ===> lint1
#   compile  lint1/cgram.o
/work/tools/bin/vax--netbsdelf-gcc -O2 -ftrapv    -g   -std=gnu99    -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign-compare  -Wsystem-headers   -Wno-traditional   -Wa,--fatal-warnings  -Wreturn-type -Wswitch -Wshadow -Wcast-qual -Wwrite-strings -Wextra -Wno-unused-parameter -Wno-sign-compare -Wold-style-definition -Wsign-compare -Wformat=2  -Wno-format-zero-length  -Werror     --sysroot=/work/hosts/vax -DIS_LINT1 -I/work/src/usr.bin/xlint/lint1 -I/work/obj/vax/work/src/usr.bin/xlint/lint1   -I. -I/work/src/usr.bin/xlint/lint1/../arch/vax -I/work/src/usr.bin/xlint/lint1/../common  -c    cgram.c -o cgram.o
during RTL pass: postreload
cgram.c: In function 'yyparse':
cgram.c:5873:1: internal compiler error: in reload_combine_note_use, at postreload.c:1534
 5873 | }
      | ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://www.NetBSD.org/support/send-pr.html> for instructions.

*** Failed target:  cgram.o
*** Failed command: /work/tools/bin/vax--netbsdelf-gcc -O2 -ftrapv -g -std=gnu99 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-sign-compare -Wsystem-headers -Wno-traditional -Wa,--fatal-warnings -Wreturn-type -Wswitch -Wshadow -Wcast-qual -Wwrite-strings -Wextra -Wno-unused-parameter -Wno-sign-compare -Wold-style-definition -Wsign-compare -Wformat=2 -Wno-format-zero-length -Werror --sysroot=/work/hosts/vax -DIS_LINT1 -I/work/src/usr.bin/xlint/lint1 -I/work/obj/vax/work/src/usr.bin/xlint/lint1 -I. -I/work/src/usr.bin/xlint/lint1/../arch/vax -I/work/src/usr.bin/xlint/lint1/../common -c cgram.c -o cgram.o
*** Error code 1

Stop.
nbmake[2]: stopped in /work/src/usr.bin/xlint/lint1


The build cluster has not run into this yet, so I suppose a recentish lint
change in -current triggers this.

Martin