VM-beginners February 2014

vm-beginners@lists.squeakfoundation.org

3 participants
5 discussions

What I would like to do is get a 64 bit VM compiled to native 64 powering a 64 bit image.
by gettimothy 27 Feb '14

27 Feb '14

Hi All. Please excuse any mistakes in terminology as I wrap my feeble mind around this stuff. To my happy surprise, building a VM per http://wiki.squeak.org/squeak/6177 1. builds a standard 32 bit VM 2. The 32 bit VM compiles to native 64 on linux: (ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), not stripped) 3. and powers a 32 bit Squeak4.x image. (I think I stated that correctly) The above runs perfectly on my pure-64 boot partition with no 32 bit compat libs..its a wonderful feeling. What I would like to do next is get a 64 bit VM compiled to native 64 powering a 64 bit image (64x64x64) as that is my goal for StackInterpreter and then Cog going forward. (and then kernel mode, multi-processor ala roarVM...VAX...) With the Squeak4.x build, cmake's configure --help provides a --image64 option that builds a VM for running 64-bit images. That vm builds just fine, but I have not been able to find a compatible 64 bit image that it will run! The instructions to create a 64 bit image using SystemTracer did not pan out (the instructions to file-in System-Tracing.1.cs and All64BitChanges.1.cs don't apply as there is no All64BitChanges.1.cs to file in. I flailed a bit with the other files there, but gave up temporarily ) and scouring the bowels of the internet yielded no appropriate ready made image. I will return to this, but being lazy by nature--I turned to David's work at http://squeakvm.org/squeak64/sq64-20101106-dtl-sources-and-image.zip hoping for an easy way out of this. David's zip runs a Squeak3.8-gamma 64 bit image, but it is powered by a 32 bit VM (?) that is compiled to a native 64 bit executable. So, at this point we are 64x64x32--32 short of the goal. So, I think, ok, compile a 64 bit VM to run the 64 bit image from the 64 bit image--easy-peasy,right?The build worked just fine, but I got the error from the FAQ that states If you try to run a 64-bit image with a VM built for 32-bit images, you will get an error message such as this: This interpreter (vers. 6502) cannot read image file (vers. 68000). where (vers. 6502) displayed as (vers. 0) when I tried to launch the original 64 bit image from which I had just created the vm. The VMMakerTool on the 3.8 gamma does not have the 64 bit vm check box--or if it does, it is well hidden. The CMake configure script for the 3.8 gamma does not support the --image64 option either. So, I am thinking now, to "port" the Squeak3.8-gamma source tree to the squeak4.x Cmake configuration, but I really don't know if this is a valid approach. If there is anything obvious that you see that I am missing, I would appreciate your advice on how to proceed. If not, I will keep poking away! Thank you for your time cordially, tty. Thanks for your time. tty.

3 2

Thanks to the International Order of Squeak Virtual Machine Builders and Knights of the Square Bracket
by gettimothy 25 Feb '14

25 Feb '14

I got the Standard VM per Dave's work at http://wiki.squeak.org/squeak/6177 Works like a charm and has helped me immensely in that I now know I can build on my 64 bit linux with the compat-libs. that is a huge confidence builder. 1. I have the same issues with StackInterpreter on a native 32 bit machine (builds, don't run) as I do on my 64 bit workstation with aformentioned libs--so that is good news as well--I can debug on my powerful workstation with 16Gigs of memory rather than the 32 bit box with 128Mb of memory (: 2. I am going to attempt the pharo process and the 64 bit squeaks next before returning to the StackInterpreter work. 3. Does the CoInterpreter VMMaker on Squeak process currently work? I read a VMMaker.oscog commit a while back where Eliot commented that "he got it to compile" When I attempt to generate the sources, I get a debugger and I don't want to debug this if the code base is in flux while Spur work is going on. cheers! tty. Squeako ergo sum. Artificiosum odi. Noli me vocare, ego ce vocare, ego te vocabo. Fac uc gaudeam. vencis secundis, cene cursum. vescere bracis meis.

1 0

VMMakerTool vs VMMaker file handling for VMMAker.oscog and a hunch
by gettimothy 24 Feb '14

24 Feb '14

Hi All. I noticed that VMMakerTool burps on the oscogvm/platforms file path (on linux) while the scripting approach uses that just fine. (Moving all the subdirectories under osgocvm/ to ./ let's the tool do its thing just fine). My hunch is that scripting is the preferred way to build and VMMakerTool is not used for .oscog True? I just want to be sure for documentation purposes. thx. tty

1 0

StackVM builds...need to debug..asking first
by gettimothy 19 Feb '14

19 Feb '14

Howdy all. I am able to build the source for the StackIntepreter and do a make install. (very gratifying) I had to remove the UUID from plugins.int for the build to succeed (I will be investigating this later)* I tried launching a Squeak 3.0, 2.8 , 4.0 and finally the 4.5 image in that order. I kept getting variants of This interpreter (vers. 6505) cannot read image file (vers. 1712914432). Press CR to quit.. The 4.5 (the image from which it was built) is the only one that attempts to run; no World launches While I am dusting off my ddd manual to debug this, I thought I would post this to get your thoughts in case there are any flashing red lights that are obvious to anybody. My 'working thoughts' at the moment are: 1. UUID could be required for the thing to run, but I don't know that. 2. Since it is StackInterpreter, I assumed it would have to run against an older pre-Cog image, but it refuses to launch the image Thinking about it, this semi-makes sense because StackInterpreter is under NewObjectMemory in the class hierarchy 3. Verify why plugins.int/ext did not get modified from VMMakerTool and had to be hand-edited (which I prefer, btw). I am pretty sure Eliot mentioned this in an email to Tim R. Thanks for your time. tty. *the include /usr/include/uuid/uuid.h is there as is the function definition that burps--probably a 32bit compat lib issue--no big deal for now.

1 0

What squeakvm.org/branch and subdirecty to use to build the StackInterpreter?
by gettimothy 18 Feb '14

18 Feb '14

Howdy, I figured its time to build the StackInterpreter so I can get my hands dirty with plugins and maybe figure out the keyEvents at that level. After a couple of missteps I was able to generate the source using VMMakerTool just fine into the src directory of svn co http://www.squeakvm.org/svn/squeak/branches/Cog tree. (Thanks Tim. R and dtl for the instructions on the wiki http://wiki.squeak.org/squeak/6177) After some failed configures and builds, I am thinking I am in the wrong branch and/or subdirectory To build the StackInterpreter, should I be on the Squeak branch with its structure? Should I build in Cog branch/unixbuild? or Cog branch/stackbuild? (which does not have a unix build directory) http://www.squeakvm.org/svn/squeak/ BRANCH Build Directory Cog unixbuild <---I WAS HERE (seemed to build cog fine, replacing svn src/ directory with VMMakerTool generated sources did not configure) Cog stackbuild <--Should I be here? Squeak platforms/unix <--or here ... <--or someplace else entirely? thx. tty

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

VM-beginners February 2014