On Sun, Mar 28, 2010 at 11:48 AM, Bryce Kampjes <bryce@kampjes.demon.co.uk>wrote:
On Sat, 2010-03-27 at 18:38 +0100, Adrian Lienhard wrote:
On Mar 27, 2010, at 18:21 , laurent laffont wrote:
On Sat, Mar 27, 2010 at 6:13 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
On Mar 27, 2010, at 17:16 , laurent laffont wrote:
I would love that the official Linux VM has:
- that thing about the gnufication I did that when compiling MacOS VM. Read this link (step 4 for example)
http://www.squeakvm.org/cgi-bin/viewcvs.cgi/trunk/platforms/Mac%20OS/vm/Docu...
does it make sense also in Linux VM ? which are the difference in
the
benchmarks compared to do it without this step ?
Isn't it a MacOS issue only ?
No, this is relevant for all GNU C compilers! Without this step, which replaces the switch statement of the interpreter with a jump table, you get a *much* slower VM. I suggest to use the latest SVN source.
Does it mean latest SVN source is already "Gnuified" ? With latest rev. I have a little drop in benchmarks. However I'd rather put a stable release for Pharo 1.0 than latest trunk. What do you think ?
The so-called "gnuification" is a transformation of the interp.c file. So this is done after generating the sources with VMMaker. The cmake configuration that comes with revision 2135 does not have this step enabled, and the more recent version that I used, revision 2151, has it. The magic is in the awk script in unix/cmake/gnuify.awk which produes gnu-interp.c.
The Exupery VMs are gnuified so as your benchmarks are close, I'd say your VM is gnuified too. If it isn't performance drops dramatically, I think to about a tenth the performance.
Bryce
OK, thanks. Lot of things to learn :) Laurent Laffont
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project