Lex Spoon wrote:

> Did you start with a new build directory and run "configure" again?

I basically did a (cd build; rm -rf *; ../src/unix/configure) everytime.

> I keep thinking this should be cleaned up, but then I think that we
> should switch to Tim's VM maker and end up working on other things.

> > '54794520 bytecodes/sec; 1623491 sends/sec' "gcc272 -m486 -O3"
> > '41994750 bytecodes/sec; 1424725 sends/sec' "gcc-2.95 -march=i686 -O3"
> > '41157556 bytecodes/sec; 1225389 sends/sec' "gcc-2.95 (default)"
> > '37058482 bytecodes/sec; 1287986 sends/sec' "gcc-3.00"
> > '36467236 bytecodes/sec; 1232651 sends/sec' "gcc-3.00 -march=athlon"

> That is pretty wild.  Did you try gcc-3.00 with -O3, as well?  (I think
> the default is -O2, right?)

As far as I rember I did not, but I will when I have a look at Tim's VM
maker. Without any -O,-O1,-O2,-O3 option gcc (3.00) is not optimizing
at all.

Now I found a benchmark test with similiar results on the web.
http://gcc.gnu.org/ml/gcc/2001-06/msg00422.html


Alex