Re: Bountysource campaign for gcc-vax

["Maciej W. Rozycki" <macro%linux-mips.org@localhost>]

On Tue, 29 Sep 2020, Maciej W. Rozycki wrote:

> On Fri, 18 Sep 2020, Jason Thorpe wrote:
> 
> > But I have also seen a couple of hints that others are also working on 
> > MODE_CC or are interested in doing so, but have not seen any specific 
> > updates or claims against the bounty.
> 
>  I'm back on track with this effort, however regrettably for some reason 
> NetBSD does not like my 4000/90, which has caused me a month's delay while 
> I was where my 4000/90 resides.

 Sigh, I take it the issues I've observed with my 4000/90 are too obscure 
for anyone to be able to comment.  Well, I have learnt already on many 
occasions that I tend to trigger obscure problems no one else ever does, 
so no surprise here.  Oh well.

>  I'm now back at my lab where my 4000/60 resides and ultimately I will 
> have the setup here configured for full remote operation, so I will be 
> able to continue using 4000/60 even while at another place.  Right now I 
> have succeeded running partial GCC verification (the C language frontend 
> only) with results as follows:
> 
> 		=== gcc Summary ===
> 
> # of expected passes		105263
> # of unexpected failures	6439
> # of unexpected successes	7
> # of expected failures		566
> # of unresolved testcases	32
> # of unsupported tests		3131
> /scratch/vax-netbsd/obj/gcc/gcc/xgcc  version 11.0.0 20200704 (experimental) (GCC)
> 
> make[1]: Leaving directory '/scratch/vax-netbsd/obj/gcc/gcc'
> make: Leaving directory '/scratch/vax-netbsd/obj/gcc/gcc'
> 3947.73user 593.71system 10:15:32elapsed 12%CPU (0avgtext+0avgdata 808572maxresident)k
> 813680inputs+4530568outputs (2909major+217790261minor)pagefaults 0swaps
> 
> These are not stellar, but not catastrophic either, and obviously the 
> primary objective of the effort is not to fix testsuite failures (though 
> some may go away as a side effect, I imagine).  Most importantly the 
> testsuite execucution time is only ~10 hours, which is quite reasonable; I 
> worked with slower configurations before.

 I've now completed lab setup up to being able to use it for this effort, 
and I have rerun testing with a new mighty server (a *proper* server, not 
a laptop).  This time results are not perfect either, but they are much 
better, though the execution time was a bit longer (still acceptable 
though), possibly due to the additional test cases that passed:

		=== gcc Summary ===

# of expected passes		110142
# of unexpected failures	1821
# of unexpected successes	7
# of expected failures		566
# of unresolved testcases	30
# of unsupported tests		3131
/scratch/vol0/vax-netbsd/obj/gcc/gcc/xgcc  version 11.0.0 20200704 (experimental) (GCC)

make[1]: Leaving directory '/scratch/vol0/vax-netbsd/obj/gcc/gcc'
make: Leaving directory '/scratch/vol0/vax-netbsd/obj/gcc/gcc'
7556.83user 1129.03system 12:04:47elapsed 19%CPU (0avgtext+0avgdata 814080maxresident)k
142336inputs+23404672outputs (2major+69725859minor)pagefaults 0swaps

 I'll keep people updated with progress in this thread.

  Maciej