On Mon, Jun 3, 2019 at 7:12 AM Maciej Rozycki <ma...@wdc.com> wrote: > > On Thu, 30 May 2019, Jim Wilson wrote: > > > > Here are the test results: > > > http://gcc.gnu.org/ml/gcc-testresults/2019-05/msg02903.html > > > > I tried running RISC-V go checks on my system. I see 7 unexpected > > failures for gcc check-go, 6 unexpected failures for check-gotools, > > and 1 unexpected failure for check-target-libgo. I haven't tried > > building and testing the go support before so I don't have any old > > results to compare against. It seems reasonable for a first attempt > > though. > > I have results as at r270765, taken with QEMU run in the user emulation > mode (I have patches outstanding for configury/Makefiles to correctly > support libgo and other library testing with a build sysroot in such a > setup, pending the completion of my WDC copyright assignment paperwork > with FSF): > > FAIL: go.test/test/args.go execution, -O2 -g
That is a fairly trivial test so if that one fails then something is pretty fundamentally wrong somewhere. You can run just that test by running make RUNTESTFLAGS=go-test.exp=args.go check-gcc-go If it fails you should have an executable gcc/testsuite/go/args.x. Run that executable as `args.x arg1 arg2`. Ian
