Re: bin/51586: internal compiler error

[DOYASHIKI Shinichi <sdhoya%z-planet.co.jp@localhost>]

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

From: DOYASHIKI Shinichi <sdhoya%z-planet.co.jp@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: bin/51586: internal compiler error
Date: Tue, 1 Nov 2016 12:56:13 +0900

 On Mon, 31 Oct 2016 14:25:00 +0000 (UTC)
 christos%zoulas.com@localhost (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.
 >  
 >  christos
 >  
 
 i usualy run "make build" instead of "build.sh release", and no fetching
 official snapshot binaries.
 
 i learned the libbfd library was not major bumped on current,
 and this is the way of today's NetBSD-current.
 so i backouted binaries on the machine from backup tarball,
 and rebuilding (running "build.sh release") now.
 
 problematic binaries are kept yet to anothor dir for chroot.