Re: [Sablevm-developer] regression testing staging@r1575 and sablevm-classpath@r1575 against 1.0.9

[Chris P. <chr...@ma...>]

Grzegorz B. Prokopski wrote:

> W li=B6cie z czw, 12-02-2004, godz. 13:56, Chris Pickett pisze:=20
>=20
>>I updated sablevm-classpath, but now I can't run configure anymore, eve=
n=20
>>with --no-gtk specified.
>>
>>./configure: line 21672: syntax error near unexpected token=20
>>`PKG_CHECK_MODULES(GTHREAD,'
>>./configure: line 21672: `     PKG_CHECK_MODULES(GTHREAD, gthread-2.0 >=
=3D=20
>>2.2)'
>=20
>=20
> I haven't seen these problems, at least last weekend, and I don't think=

> much has been changed since then. Try these:
>=20
> aclocal-1.7 && libtoolize --force && autoconf && autoheader &&
> automake-1.7 --foreign -a -c
>=20
> If you use Debian, and have the right versions of the tools installed
> - the above programs should be found.
>=20

So, it compiled.  But I couldn't get it to work without dnl'ing the=20
lines in question (I tried the above commands).  It needs to be fixed=20
before moving into bugfree, IMHO, but I don't know how.  Feel free to=20
verify it on one of the Sable machines with the versions I have=20
(aclocal-1.8.2, libtoolize-1.5.2, autoconf-2.59, autoheader-2.59,=20
automake-1.8.2, which are the latest versions -- I just installed them).

You can see the results of the benchmark runs in:

http://sable.mcgill.ca/~cpicke/sablevm/r1575-vs-1.0.9/

*_times_* are the raw benchmark times
*_report_* are reports, with user times and pass/fail status (see first)
*_diff_* are diffs that caused failure in the reports
*_paranoid_diff_* are diffs that don't ignore run-specific information

Basically:

1) I found no regressions
2) mtrt seems to have been fixed for switch-debug (no blank line)
3) JGFSyncBench, JGFLUFactBench, and JGFRayTracerBench fail
      (single- and multi-threaded errors)
4) JGFSerialBench fails, but it fails for java as well
      (verification error)
5) In general things are faster, but there are a couple of exceptions.

*** I didn't run the SizeB and SizeC benchmarks from JGF, since they=20
take too long ***

This is what I think is needed for bugfree:

1) A list of known issues (incl. the above benchmark failures and the=20
fact that synchronized methods may crash the VM)
2) A fix for the classpath configure problem (I think the easiest is to=20
undo Mark's configure.ac patch, since apparently this was only for JamVM)=
=2E

Cheers,
Chris