Re: toolchain/49425: internal compiler error compiling riscv userland

[Matt Thomas <matt%3am-software.com@localhost>]

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

From: Matt Thomas <matt%3am-software.com@localhost>
To: Dennis Ferguson <dennis.c.ferguson%gmail.com@localhost>
Cc: Martin Husemann <martin%duskware.de@localhost>,
 gnats-bugs%NetBSD.org@localhost,
 toolchain-manager%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost,
 netbsd-bugs%netbsd.org@localhost
Subject: Re: toolchain/49425: internal compiler error compiling riscv userland
Date: Mon, 1 Dec 2014 00:47:15 -0800

 > On Dec 1, 2014, at 12:44 AM, Dennis Ferguson =
 <dennis.c.ferguson%gmail.com@localhost> wrote:
 >=20
 >=20
 > On 1 Dec, 2014, at 16:10 , Martin Husemann <martin%duskware.de@localhost> wrote:
 >> OK, so the list of files differs (see toolchain/49434) and -O1 vs =
 -O0;
 >> these are likely different MD gcc bugs.
 >>=20
 >> Reinoud or you should report this upstream.
 >=20
 > Yes, though for RISC-V compiler it is a bit ambiguous who the upstream
 > is.  As far as I can tell the RISC-V people have only done their MD =
 for
 > gcc 4.6.something and 4.9, so it may be Matt(??) who moved this into =
 4.8.3.
 > If I can get one of the supported RISC-V compilers to build I can try =
 it
 > to see if it gets the same ICE and report that, otherwise the =
 workaround
 > may need to stay until NetBSD moves to a gcc version they also =
 support.
 
 You might also try using the -fno-builtin-<...> to disable the pattern.
 
 I saw that with the gcc4.9 one as well.
 
 I first tried to get <riscv/lock.h> to use the C11 atomic but the =
 compiler blew chuncks.=