Fwd: Gm2 test results on NetBSD 9.2/Sparc

[Gaius Mulley]

Hello John,

not sure about any scripts to extract failures - I generally use
'less' and /FAIL or emacs etc.
But I do run selective test cases - once I know the failure from the above.
Using this script:

 #!/bin/bash

make check-m2 RUNTESTFLAGS="${1}.exp" ; tail gcc/testsuite/gm2/gm2.log

which is sequentially run and easier to analyse,

regards,
Gaius

On Wed, Aug 10, 2022 at 10:33 PM john o goyo <jog37@riddermarkfarm.ca> wrote:
>
> Greetings, Gaius.
>
> On 2022-08-10 07:00, Gaius Mulley wrote:
> > john o goyo <jog37@riddermarkfarm.ca> writes:
> >
> >>                  === gm2 Summary ===
> >>
> >> # of expected passes            11583
> >> # of unexpected failures        97
> >> # of unresolved testcases       73
> >>
> >> This with NetBSD 9.2 sparc64 on an SB2000.
> >>
> >> Sincerely,
> >> john
> > Thanks John - I'm guessing the long set problems still persist?  If so I
> > think a way around this would be to re-implement the longset code
> > without using in indirect function call in M2GenGCC.mod
>
> Actually, 74 failures were due to unsuccesful links.  I am investigating.
>
> By the way, are there some scripts available to print out the failures
> from the log file?  (I mean from the initial FAIL to the next
> FAIL/PASS.)
>
> Sincerely,
> john
>
>
> >
> > regards,
> > Gaius
>
>