[Vm-dev] Prebuilt 64-bit VM on Linux?

[David T. Lewis]

On Wed, Apr 10, 2013 at 08:11:39PM -0300, Hern?n Morales Durand wrote:
> 
> El 10/04/2013 18:57, David T. Lewis escribi?:
> >
> >On Wed, Apr 10, 2013 at 06:11:53PM -0300, Hern??n Morales Durand wrote:
> >>
> >>I have a 64-bit CentOS server and I want a to measure the peak memory 
> >>usage
> >>with valgrind for a script. For that I need a 64-VM (with a 32-bit Pharo
> >>image).
> >>I have tried with
> >>http://www.mirandabanda.org/files/Cog/VM/VM.r2714/coglinux-13.13.2714.tgzbut
> >>file reports: "squeak: ELF 32-bit LSB executable, Intel 80386, version
> >>1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not
> >>stripped"
> >>
> >>Is there any precompiled linux 64-bit binary available?
> >>
> >
> >As others have pointed out, an interpreter VM compiled for 64-bit will
> >work fine, though not as fast as Cog. However, recent Pharo images will
> >no longer run on a standard interpreter, so you cannot run a Pharo 2.0
> >image on a 64-bit VM.
> 
> Thanks for the information. This is sad news. Because I am comparing 
> avg. execution time against python and perl and cog is the winner for my 
> workflow.
> 

I am not familiar with valgrind, but if you can get a 32-bit version of
valgrind that works with the normal 32-bit Cog executable, I think that
would be the best thing to do. After all, that is your target execution
environment, so it would be good if your profiling tool runs in that same
environment.

If you are interested in memory utilization rather than speed, and if your
application runs in Squeak, then use a 64-bit interpreter VM and Squeak.
If you want speed, then use Cog and find a profiling tool that can support
it. The difference between 32 and 64 bit compiled VMs is of no consequence
with respect to performance, it is really just a matter of installing the
necessary runtime libraries to support 32-bit operations.

Dave