Vm-dev October 2012

vm-dev@lists.squeakfoundation.org

27 participants
45 discussions

Building StackVM on ARM linux meego-hartmann
by Denis Kudriashov 04 Oct '12

04 Oct '12

Hello I try to build StackVM on my phone nokiaN9 by mariano blog http://marianopeck.wordpress.com/2011/04/10/building-the-vm-from-scratch-us… It is specific linux meego-hartmann on ARM. So I just perform all instructions on my phone terminal app. (generated sources from StackUnixConfig I copied to phone prepared dir). CMake command executed successfully. But "make" failed on processing LocalePlugin. I have in console: Building C object LocalePlugin/../...Plugin.c o cc1 error: incorrect key "-m32" cc1 error: incorrect key "-msse2" And I found any plugin cmakelists includes such statement: add_definitions( -DLSB_FIRST=1 -DUSE_GLOBAL_STRUCT=0 -DCOGMTVM=0 -m32 -g0 -O2 -msse2 -D_GNU_SOURCE -DNDEBUG -DITIMER_HEARTBEAT=1 -DNO_VM_PROFILE=1 -DDEBUGVM=0) What do you think? What I can do to fix it? P.S. I'am very beginner on C stuff. Best regards, Denis

5 17

VM Maker: VMMaker-oscog-golubovsky.139.mcz
by commits＠source.squeak.org 04 Oct '12

04 Oct '12

Dmitry Golubovsky uploaded a new version of VMMaker to project VM Maker: http://source.squeak.org/VMMaker/VMMaker-oscog-golubovsky.139.mcz ==================== Summary ==================== Name: VMMaker-oscog-golubovsky.139 Author: golubovsky Time: 3 October 2012, 9:32:06 pm UUID: 4100961e-5bbb-465d-82aa-b89b8a2cd7ea Ancestors: VMMaker-oscog-golubovsky.138 Added openURI primitive =============== Diff against VMMaker-oscog-golubovsky.138 =============== Item was added: + ----- Method: AndroidPlugin>>primOpenURI (in category 'system primitives') ----- + primOpenURI + | msg vmcls vmobj bmmeth jmsg res | + <var: 'msg' type: 'char *'> + <var: 'vmcls' type: 'jclass'> + <var: 'vmobj' type: 'jobject'> + <var: 'bmmeth' type: 'jmethodID'> + <var: 'jmsg' type: 'jstring'> + <export: true> + msg := self stringArgumentAt: 0. + vmcls := self getVMClass. + vmcls ifNil: [^ interpreterProxy primitiveFail]. + vmobj := self getVMObject. + vmobj ifNil: [^ interpreterProxy primitiveFail]. + bmmeth := self getMethod: 'openURI' withSig: '(Ljava/lang/String;)I' inClass: vmcls. + bmmeth ifNil: [^ interpreterProxy primitiveFail]. + jmsg := self asJavaString: msg. + jmsg ifNil: [^ interpreterProxy primitiveFail]. + res := self callIntMethod: bmmeth On: vmobj with:jmsg. + interpreterProxy pop: 2. + interpreterProxy pushInteger: res. + !

1 0

VM Maker: Android-Base-golubovsky.25.mcz
by commits＠source.squeak.org 04 Oct '12

04 Oct '12

Dmitry Golubovsky uploaded a new version of Android-Base to project VM Maker: http://source.squeak.org/VMMaker/Android-Base-golubovsky.25.mcz ==================== Summary ==================== Name: Android-Base-golubovsky.25 Author: golubovsky Time: 3 October 2012, 9:26:40 pm UUID: 52beb7e3-67b9-4eed-bbe8-4d038cd0c5b3 Ancestors: Android-Base-golubovsky.24 Added openURI primitive =============== Diff against Android-Base-golubovsky.24 =============== Item was added: + ----- Method: Android class>>openURI: (in category 'system primitives') ----- + openURI: aString + "open an URI in browser" + <primitive: 'primOpenURI' module: 'AndroidPlugin'> + self primitiveFailed.!

1 0

[Cog] Stack (mis)alignment on windows resolved
by Igor Stasenko 02 Oct '12

02 Oct '12

Hi, Eliot & all, false alarm. The assertion was failing because i hardcoded to use -O1 for gcc3x-interp.c, while when building for debug, it apparently should be -O0, because otherwise gcc does not generates proper stack frame(s) for these functions, which makes assertion failing (because it used condition ebp & 15 == 8) -- Best regards, Igor Stasenko.

1 0

[ARM Compiler & Plugin] Design Decisions
by Lars 02 Oct '12

02 Oct '12

Hello, for documentation purposes, a list of design decisions and alternatives which might be implemented later. In general, the plugin is as similar as possible to the original Bochsplugin. The C functions have the same interface. The Smalltalk GdbARMPlugin class is an exact copy of BochIA32Plugin, to generate the according calls to the handwritten C part. We patched the ARMulator memory system, to enable bounds checking on memory and have direct addresses relative to the memory chunk supplied when calling. The code for that is in armulmem.c. For direct access, like i.a. ldm, stm, we patched GetWord and PutWord. For those, we have memory access boundaries of minimum address and size, or rather minimumWriteAddress and size in case of PutWord. To enable the maxExecAddress, we need a trick using SWIs, because ARM prefetches 2 instruction after the one executed. Thus, we also patched ReLoadInstr, which is eventually called in all instruction fetch cases. Even if I added 8 to the execution bound, there is no stop check after fetching an instruction, thus prohibiting jumping out of the main emulation loop, without patching it. So we instead return a custom software interrupt instruction when fetching illegal addresses. When executed, ARMul_OSHandleSWI is called, which is patched to stop emulation and give a proper error message(at the bottom of sqGdbARMPlugin.c). For the conditional jumps, we use the condition codes as encoded in the first four bits of every ARM instruction. Those condition codes are available in ARMCompiler as class variables. They are set to the according value in ARMCompiler class>>#initialize. IA32 is a variable length instruction set, allowing to encode word constants within an instruction. ARM on the other hand is a fixed length instruction set, and thus we can not encode constant words in one instruction. As a first (simple) version, word constants are included loading them byte by byte into the abstract register RISCTempReg (R10 at the moment). Therefore, all abstract opcodes which have word arguments are at least four ARM instructions long. Changing those word constants means usually changing the lowest 12bit of those four instructions. The generation is done in CogARMCompiler>>#at:moveCw:intoR:. We have to change the last 12bit, because the ARM standard asks for minimal rotation values (higher 4bit). Once the ARMCompiler works, there is the idea of introducing constant tables after the final jump back in each method, allowing PC relative addressing for word constants, thus reducing the number of instructions but increasing random access. Implementing both methods also allows measuring the performance change. Are there any questions? Best, Lars

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Vm-dev October 2012