[Bug go/89171] FAIL: go/build

2019-02-26 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89171 Andreas Schwab changed: What|Removed |Added Target|riscv64-*-* | --- Comment #5 from Andreas Schwab --

[Bug go/89171] FAIL: go/build

2019-02-26 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89171 --- Comment #4 from Ian Lance Taylor --- To run, say, just the go/build test, cd to the libgo build directory and run "make go/build/check". To keep the test binary around, run "make GOTESTFLAGS=--keep go/build/check". That will leave the test

[Bug go/89171] FAIL: go/build

2019-02-26 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89171 --- Comment #3 from Andreas Schwab --- How can I build and run a single libgo test?

[Bug go/89171] FAIL: go/build

2019-02-16 Thread sch...@linux-m68k.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89171 --- Comment #2 from Andreas Schwab --- There are prebuilt images in that are set up to execute via qemu linux-user emulation.

[Bug go/89171] FAIL: go/build

2019-02-15 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89171 --- Comment #1 from Ian Lance Taylor --- I don't know what is happening here and I don't have access to a riscv64 machine to test on (there doesn't seem to be one in the compile farm). The errors are incorrect in that these are not expected depe