public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Godmar Back <gback@cs.utah.edu>
To: abies@pg.gda.pl (Artur Biesiadowski)
Cc: tromey@cygnus.com, mauve-discuss@sourceware.cygnus.com
Subject: Re: VM tests [was Re: Library/VM tests]
Date: Fri, 12 Mar 1999 08:19:00 -0000	[thread overview]
Message-ID: <199903121619.JAA12039@lal.cs.utah.edu> (raw)
In-Reply-To: < 36E8FBAD.F4FA1CF@pg.gda.pl > from "Artur Biesiadowski" at Mar 12, 99 12:34:05 pm

 For a start, we could just use the kaffe/test/regression/TestScript.in
Alexandre Oliva wrote.

It allows compile options and the expected output to be hidden in a
comment in the .java file, runs a test and (optionally) sorts and
diffs the output.

It does not support java assembler, JNI or native tests nor does it
support timeouts.  These are all very useful features.  It's using sh
at this point, but I wouldn't mind using perl.

	- Godmar

> 
> This certainly would reuqire very different handling.
> I think that it can be done by creating some informative directory
> structure and then executing each class in separate VM by command line
> (from makefile or perl or some other script).
> 
> A lot of tests should be written directly in assembler - you cannot be
> sure how compilers will translate given code. With assembler we can test
> verious verify error, some magic combinations of stack/jumps which would
> be impossible from java. This requires java assembler - there are some
> available on the net, with jasmin coming to mind, but it is a bit large
> (450kb packed ?).
> 
> JNI tests would require C compiler and some knowledge about runtime libs
> of given vm. Smart configure script should be enough.
> 
> Some way would have to be defined to kill infinite loops. Maybe second
> process sleeping for few minutes ?
> 
> Artur
> 

WARNING: multiple messages have this Message-ID
From: Godmar Back <gback@cs.utah.edu>
To: abies@pg.gda.pl (Artur Biesiadowski)
Cc: tromey@cygnus.com, mauve-discuss@sourceware.cygnus.com
Subject: Re: VM tests [was Re: Library/VM tests]
Date: Thu, 01 Apr 1999 00:00:00 -0000	[thread overview]
Message-ID: <199903121619.JAA12039@lal.cs.utah.edu> (raw)
Message-ID: <19990401000000.M1sPPGVQJjPBWrlmcTukpDsmz4aR1HSLP4t-nl97x6k@z> (raw)
In-Reply-To: <36E8FBAD.F4FA1CF@pg.gda.pl>

 For a start, we could just use the kaffe/test/regression/TestScript.in
Alexandre Oliva wrote.

It allows compile options and the expected output to be hidden in a
comment in the .java file, runs a test and (optionally) sorts and
diffs the output.

It does not support java assembler, JNI or native tests nor does it
support timeouts.  These are all very useful features.  It's using sh
at this point, but I wouldn't mind using perl.

	- Godmar

> 
> This certainly would reuqire very different handling.
> I think that it can be done by creating some informative directory
> structure and then executing each class in separate VM by command line
> (from makefile or perl or some other script).
> 
> A lot of tests should be written directly in assembler - you cannot be
> sure how compilers will translate given code. With assembler we can test
> verious verify error, some magic combinations of stack/jumps which would
> be impossible from java. This requires java assembler - there are some
> available on the net, with jasmin coming to mind, but it is a bit large
> (450kb packed ?).
> 
> JNI tests would require C compiler and some knowledge about runtime libs
> of given vm. Smart configure script should be enough.
> 
> Some way would have to be defined to kill infinite loops. Maybe second
> process sleeping for few minutes ?
> 
> Artur
> 


  parent reply	other threads:[~1999-03-12  8:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-02 16:06 Library/VM tests Tim Wilkinson
1999-03-03 23:56 ` Tom Tromey
     [not found]   ` < 87bti94rgj.fsf@cygnus.com >
1999-03-04 12:56     ` Moses DeJong
     [not found]       ` < Pine.SGI.4.05.9903041452180.811-100000@neon.cs.umn.edu >
1999-03-04 13:11         ` Godmar Back
1999-04-01  0:00           ` Godmar Back
1999-04-01  0:00       ` Moses DeJong
1999-04-01  0:00   ` Tom Tromey
1999-03-04  7:45 ` Artur Biesiadowski
1999-03-04 10:46   ` Brian Jones
1999-04-01  0:00     ` Brian Jones
1999-03-04 19:03   ` Tim Wilkinson
1999-03-11 23:25     ` Tom Tromey
1999-03-12  3:37       ` VM tests [was Re: Library/VM tests] Artur Biesiadowski
     [not found]         ` < 36E8FBAD.F4FA1CF@pg.gda.pl >
1999-03-12  8:19           ` Godmar Back [this message]
1999-04-01  0:00             ` Godmar Back
1999-04-01  0:00         ` Artur Biesiadowski
1999-04-01  0:00       ` Library/VM tests Tom Tromey
1999-04-01  0:00     ` Tim Wilkinson
1999-04-01  0:00   ` Artur Biesiadowski
1999-04-01  0:00 ` Tim Wilkinson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199903121619.JAA12039@lal.cs.utah.edu \
    --to=gback@cs.utah.edu \
    --cc=abies@pg.gda.pl \
    --cc=mauve-discuss@sourceware.cygnus.com \
    --cc=tromey@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).