Re: bin/51586: internal compiler error

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

The following reply was made to PR bin/51586; it has been noted by GNATS.

From: Patrick Welche <prlw1%cam.ac.uk@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: prlw1%cam.ac.uk@localhost
Subject: Re: bin/51586: internal compiler error
Date: Mon, 31 Oct 2016 15:45:07 +0000

 On Mon, Oct 31, 2016 at 02:25:00PM +0000, Christos Zoulas wrote:
 > The following reply was made to PR bin/51586; it has been noted by GNATS.
 > 
 > From: christos%zoulas.com@localhost (Christos Zoulas)
 > To: gnats-bugs%NetBSD.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, 
 > 	sdhoya%z-planet.co.jp@localhost
 > Cc: 
 > Subject: Re: bin/51586: internal compiler error
 > Date: Mon, 31 Oct 2016 10:22:11 -0400
 > 
 >  On Oct 31, 10:35am, sdhoya%z-planet.co.jp@localhost (sdhoya) wrote:
 >  -- Subject: Re: bin/51586: internal compiler error
 >  
 >  | The following reply was made to PR bin/51586; it has been noted by GNATS.
 >  | 
 >  | From: sdhoya <sdhoya%z-planet.co.jp@localhost>
 >  | To: gnats-bugs%NetBSD.org@localhost
 >  | Cc: 
 >  | Subject: Re: bin/51586: internal compiler error
 >  | Date: Mon, 31 Oct 2016 18:15:23 +0900
 >  | 
 >  |  On Mon, 31 Oct 2016 03:55:02 +0000 (UTC)
 >  |  David Holland <dholland-bugs%netbsd.org@localhost> wrote:
 >  |  
 >  |  >  Curious... can you extract the generated assembly, and find the exact
 >  |  >  way it's invoking as? If you run as directly on the assembly file with
 >  |  >  the same arguments, does it still crash?
 >  |  >  
 >  |  >  (use -S to compile to assembly, -v to show the invocation)
 >  |  
 >  |  thank you, result follows...
 >  
 >  Did you build the toolchain yourself, or is this with a downloaded binary?
 >  I can't reproduce this.
 
 I just built a fresh release with this morning's HEAD on a working
 -current/amd64 box. That box has
 
 GNU assembler (NetBSD Binutils nb1) 2.26.1
 
 I unpacked the comp.tgz which it generated on the broken -current/amd64 box
 I mentioned on current-users, and
 
 $ gcc -v -o hellow hellow.c -Wall
 ...
 gcc version 5.4.0 (nb1 20160606) 
 ...
 COLLECT_GCC_OPTIONS='-v' '-o' 'hellow' '-Wall' '-mtune=nocona' '-march=x86-64'
  as -v -o /var/tmp//ccsSnHDU.o /var/tmp//ccuDqDqB.s
 GNU assembler version 2.27 (x86_64--netbsd) using BFD version (NetBSD Binutils nb1) 2.27
 ...
 COLLECT_GCC_OPTIONS='-v' '-o' 'hellow' '-Wall' '-mtune=nocona' '-march=x86-64'
  ld -plugin /usr/libexec/liblto_plugin.so -plugin-opt=/usr/libexec/lto-wrapper -plugin-opt=-fresolution=/var/tmp//ccrSXbZ4.res -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --eh-frame-hdr -dc -dp -e _start -dynamic-linker /usr/libexec/ld.elf_so -o hellow /usr/lib/crt0.o /usr/lib/crti.o /usr/lib/crtbegin.o /var/tmp//ccsSnHDU.o -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/lib/crtend.o /usr/lib/crtn.o
 gcc: internal compiler error: Segmentation fault (program ld received signal 11)
 Please submit a full bug report,
 
 I have as.core and ld.core in the build directory.