Re: Why is make test so slow?
At 07:12 PM 10/20/2001 -0400, Sam Tregar wrote: On 20 Oct 2001, Gregor N. Purdy wrote: I want to libify everything to the point where Perl wrappers around the libs allow you to pass the .pasm stuff as a string and get back a packfile that you can pass on to the interpreter, without firing off separate processes and writing files. Sounds like a good idea. It'll be necessary to have something like this to support string eval() anyway, right? Something like that, yep. (Though string eval won't fire off an assembler) What'd be really nice, though probably a bad idea for the test suite, was if the test program could run multiple tests sequentially without having to exit after each one. Like: create interpreter load bytecode for interpreter execute bytecode in interpreter destroy interpreter over and over. Certainly be a good test of the GC system. :) Dan --it's like this--- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
Why is make test so slow?
Why is make test so durn slow? Our tools run individually seem pretty snappy on my low-end box (P200/64MB) but running make test is like watching paint dry. I'm seeing something like 1 test per second! Please feel free to point me to TFM if this question is answered there. -sam
Re: Why is make test so slow?
Sam -- Why is make test so durn slow? Our tools run individually seem pretty snappy on my low-end box (P200/64MB) but running make test is like watching paint dry. I'm seeing something like 1 test per second! I think its because each test involves: 1. Write out a .pasm file 2. Run assemble.pl on it to produce a .pbc file 3. Run test_prog on it to produce output I want to libify everything to the point where Perl wrappers around the libs allow you to pass the .pasm stuff as a string and get back a packfile that you can pass on to the interpreter, without firing off separate processes and writing files. Then, all this can happen inside a single process. That should make for some decent savings. I don't know if there's another reason for the speed problem (Most of the tests are pretty trivial code), but this would be nice to have anyway. Regards, -- Gregor _ / perl -e 'srand(-2091643526); print chr rand 90 for (0..4)' \ Gregor N. Purdy [EMAIL PROTECTED] Focus Research, Inc.http://www.focusresearch.com/ 8080 Beckett Center Drive #203 513-860-3570 vox West Chester, OH 45069 513-860-3579 fax \_/
Re: Why is make test so slow?
On 20 Oct 2001, Gregor N. Purdy wrote: I want to libify everything to the point where Perl wrappers around the libs allow you to pass the .pasm stuff as a string and get back a packfile that you can pass on to the interpreter, without firing off separate processes and writing files. Sounds like a good idea. It'll be necessary to have something like this to support string eval() anyway, right? -sam
