All Projects → OpenSmalltalk → Opensmalltalk Vm

OpenSmalltalk / Opensmalltalk Vm

Licence: other
Cross-platform virtual machine for Squeak, Pharo, Cuis, and Newspeak.

Programming Languages

50402 projects - #5 most used programming language
420 projects

Projects that are alternatives of or similar to Opensmalltalk Vm

Scripting in C with JIT(x64)/VM.
Stars: ✭ 25 (-92.75%)
Mutual labels:  vm, x86-64, jit
An ARM dynamic recompiler.
Stars: ✭ 675 (+95.65%)
Mutual labels:  x86-64, jit
Grafana On Raspberry
Grafana packages for raspberry pi (armv6/armv7) and aarch64/arm64
Stars: ✭ 318 (-7.83%)
Mutual labels:  raspberry-pi, armv7
Aheui JIT compiler for PC and web
Stars: ✭ 27 (-92.17%)
Mutual labels:  x86-64, jit
A Squeak/Smalltalk VM written in RPython.
Stars: ✭ 78 (-77.39%)
Mutual labels:  vm, jit
Lightweight and optimised PHP-FPM (PHP 7.4, 8.0, 8.1) Docker images with essential extensions on top of latest Alpine Linux.
Stars: ✭ 53 (-84.64%)
Mutual labels:  x86-64, armv7
Simple automated script to build XMRig (dynamic or static) from source on x86-64, ARMv7, and ARMv8 devices.
Stars: ✭ 14 (-95.94%)
Mutual labels:  x86-64, armv7
Cloudflare Ddns
🎉🌩️ Dynamic DNS (DDNS) service based on Cloudflare! Access your home network remotely via a custom domain name without a static IP!
Stars: ✭ 332 (-3.77%)
Mutual labels:  raspberry-pi, armv7
Interpreter experiment. Testing dispatch methods: Switching, Direct/Indirect Threaded Code, Tail-Calls and Inlining
Stars: ✭ 32 (-90.72%)
Mutual labels:  vm, x86-64
Run JVM-based code in Go efficiently
Stars: ✭ 61 (-82.32%)
Mutual labels:  vm, jit
wazero: the zero dependency WebAssembly runtime for Go developers
Stars: ✭ 2,065 (+498.55%)
Mutual labels:  vm, jit
Cuis Smalltalk Dev
Active development of Cuis Smalltalk
Stars: ✭ 276 (-20%)
Mutual labels:  raspberry-pi, x86-64
Language agnostic scripting engine with a custom bytecode JIT
Stars: ✭ 36 (-89.57%)
Mutual labels:  vm, jit
Qemu.js source code with proof-of-concept machine-code-to-WASM JIT.
Stars: ✭ 101 (-70.72%)
Mutual labels:  vm, jit
Minimal, low-level, fast, and self-contained register-based bytecode virtual machine/runtime environment.
Stars: ✭ 101 (-70.72%)
Mutual labels:  vm, x86-64
Vox language compiler. AOT / JIT / Linker. Zero dependencies
Stars: ✭ 288 (-16.52%)
Mutual labels:  x86-64, jit
Machine code generation for C++
Stars: ✭ 2,874 (+733.04%)
Mutual labels:  jit, x86-64
DSP library for signal processing
Stars: ✭ 37 (-89.28%)
Mutual labels:  x86-64, armv7
NordVpn Docker Client
Stars: ✭ 475 (+37.68%)
Mutual labels:  x86-64, armv7
CPU Ultimate Latency Test.
Stars: ✭ 67 (-80.58%)
Mutual labels:  x86-64, jit

The Cog VM source tree

This is the README for the Cog Git source tree:

Download stable Download bleedingEdge Unix Build Status Windows Build status


Builds are tested automatically on each commit on Travis and Appveyor, for Windows 32, Mac OS X 32 and 64, and on Linux 32, 64, and ARM. Squeak, Pharo, and Newspeak VMs are built with and without JIT, with and without Spur, and with and without Sista, as available per platform. All build artifacts are uploaded to Bintray. If you wish to commit without triggering a build, for example if you were to only edit this documentation, then if you add [ci skip] somewhere in your commit message, Travis and Appveyor will not build that commit.

Important notice for Developers:

We rely on source file substitutions in the src tree, specifically, any sq*SCCSVersion.h files anywhere in the tree are processed to replace $Rev$, $Date$, and $URL$ with the current revision (defined as the timestamp %Y%m%d%H%M of the latest commit), the human readable date of that commit, and the url of the origin repository these sources were cloned from.

The first time you clone this repository, you must therefore run this command:


This will install filters, post-commit, and post-merge hooks to update the sq*SCCSVersion.h files anytime you commit or merge.

For easier use, we include the scripts/gitci and scripts/gitciplugins scripts to commit changes to this branch and changes to the Cross and win32 plugins (which are shared with the old Squeak interpreter trunk). If you decide not to use these scripts for checking in sources, you should also run the updateSCCSVersions script anytime you decide to use git-reset or git-checkout to make sure the stamps are updated correctly. Failing to do so will result in incorrect version stamps in your compiled VMs.


  • Overview
  • VM source directories
  • Platform build directories
  • Other directories


First, opensmalltalk-vm (a.k.a. the Cog VM) is the virtual machine beneath the Cuis, Pharo and Squeak Smalltalk dialects and one of the VMs beneath the Newspeak language. For issues related to these systems that are unrelated to the VM itself, please use their forums:

Second, the core VM, which comprises the execution engine and garbage collector, and the core plugins, is developed in Smalltalk, using the VM Simulator. This repository contains the code generated by the Simulator, and the platform support code for the entire VM, its CI infrastructure and so on. The core VM should not be developed by editing the generated code. The core VM should be developed using Smalltalk. The source code repository for the VM is
You can find scripts to build a Smalltalk image in which to do core VM development in the image directory in this repository. You can read about the Simulator here:

Cog is an evolution of the Squeak Back-to-the-future Smalltalk virtual machine that provides a number of different Smalltalk virtual machines. The VMs are developed in Smalltalk, using all the dynamic and reflective facilities of the Squeak/Pharo Smalltalk system. As such, developing in Cog is a delight. The Smalltalk framework comprising the various Cog VMs is translated into C by its Slang component to produce VM source that is combined with platform-specific support sources and compiled via a C compiler to obtain a fast production VM. This directory tree includes the output of Slang for various configurations of "Cog VM" and the associated platform support code, plus build directories that can be used to produce production VMs.

This directory tree also includes an instance of the Smalltalk Cog development system, suitable for developing the VM in Smalltalk, and for generating new VM sources.

The "Cog VM" comes in a bewildering variety of forms. The first distinction is between Squeak/Croquet VMs that run Squeak, Pharo, Cuis, Croquet images and their ilk, and between Newspeak VMs that run Newspeak.

Another distinction is between Stack, Cog and Sista VMs. Stack VMs are those with context-to-stack mapping that optimise message sending by keeping method activations on a stack instead of in contexts. These are pure interpreters but are significantly faster than the standard context-based Interpreter VM. Cog VMs add a JIT to the mix, compiling methods used more than once to machine code on the fly. Sista VMs, as yet unrealised and in development, add support for adaptive optimization that does speculative inlining at the bytecode-to-bytecode level. These are under development and targeted for release in 2015.

Another distinction is between "v3" VMs and Spur VMs. "v3" is the original object representation for Squeak as described in the back-to-the-future paper. Spur, as described on the blog, is a faster object representation which uses generation scavenging, lazy forwarding for fast become, a single object header format common to 32 and 64 bit versions, and a segmented heap that can grow and shrink, releasing memory back to the host OS. Newspeak, Squeak 5.0 and Pharo 5 use Spur.

Another distinction is between normal single-threaded VMs that schedule "green" Smalltalk light-weight processes above a single-threaded VM, and multi-threaded VMs that share the VM between any number of native threads such that only one native thread owns the VM at any one time, switching between threads on FFI calls and callbacks or on Smalltalk process switches when Smalltalk processes are owned by threads. This architecture offers non-blocking FFI calls and interoperability with multiple native threads, but does /not/ provide true concurrency. This multi-threaded support is as yet experimental.

VM source directories

The Slang output of the various VMs are kept in "vm source" directories. These C sources define the core VM (the Smalltalk execution engine and the memory manager), and a substantial set of "plugins" that provide interfaces to various external facilities via Smalltalk primitive methods. Each vm source directory is specific to a particular VM, be it Squeak Cog Spur, or Newspeak Stack, etc. The plugins can be shared between VMs, choosing the set of plugins to include in a VM at build time.

The VM source are in directories such as

	nscogsrc/vm			- Newspeak Cog V3
	nsspursrc/vm		- Newspeak Cog Spur
	nsspurstacksrc/vm	- Newspeak Stack Spur
	nsstacksrc/vm		- Newspeak Stack V3
	sistasrc/vm			- Smalltalk Sista V3
	spursistasrc/vm		- Smalltalk Sista Spur
	spursrc/vm			- Smalltalk Cog Spur
	spur64src/vm		- Smalltalk Cog Spur 64-bit
	spurstacksrc/vm		- Smalltalk Stack Spur
	spurstack64src/vm	- Smalltalk Stack Spur 64-bit
	src/vm				- Smalltalk Cog V3
	stacksrc/vm			- Smalltalk Stack V3

All plugins are in the directory


These contain many, but not all, of the plugins available for the VM. Others can be found in Cog, or in various Monticello packages in various repositories.

Each vm source directory contains several files, a subset of the following:

	cogit.c				- the JIT; a Cogit cooperates with a CoInterpreter.
                          This simply includes a processor-specific JIT file
	cogitIA32.c et al   - relevant processor-specific JIT, selected by cogit.c
	cogit.h				- the Cogit's API, as used by the CoInterpreter
	cogmethod.h			- the structure of a CogMethod, the output of the Cogit
	cointerp.c			- the CoInterpreter's source file
	cointerp.h			- the API of the CoInterpreter, as used by the Cogit
	cointerpmt.c		- the multi-threaded CoInterpreterMT's source file
	cointerpmt.h		- the API of the CoInterpreterMT, as used by the Cogit
	gcc3x-cointerp.c	- cointerp.c massaged to interpret faster if using gcc
	gcc3x-cointerpmt.c	- ditto for cointerpmt.c
	gcc3x-interp.c		- ditto for interp.c
	interp.c			- the StackInterpreter's source file
	interp.h			- defines for the VM configuration, word size, etc
	vmCallback.h		- the structure of the VM's VMCallbackContext

Platform build directories

The current "official" build directories are of the form build.OS_WordSize_Processor, and include

	build.linux32x86	- uses autoconf, gcc and make
	build.macos32x86	- 32-bit Mac OS X using clang and gmake
	build.macos64x64	- 64-bit Mac OS X using clang and gmake
	build.win32x86		- uses cygwin, gcc and gmake

More can be added as required. In each there is a HowToBuild that describes the necessary steps to compile a VM.

Within each build.OS_WordSize_Processor directory are a set of build directories for specific configurations of Cog, and for support code and makefiles. For example, there exist

	build.macos32x86/squeak.cog.spur   - A Cog JIT VM with Squeak branding,
                                         using the Spur memory manager.
	build.macos32x86/squeak.stack.spur - A Stack interpreter VM with Squeak
                                         branding, and the Spur memory manager.
	build.macos32x86/squeak.cog.v3     - A Cog JIT VM with Squeak branding,
                                         using the old Squeak memory manager.
	build.macos32x86/pharo.cog.spur    - A Cog JIT VM with Pharo branding and
                                         plugins (not yet implemented) using the
                                         Spur memory manager.

There exist

    build.macos32x86/bochsx86 - Support libraries for the BochsIA32Plugin which
                                is used to develop Cog itself.
    build.macos32x86/bochsx64 - Support libraries for the BochsX64Plugin which
                                is used to develop Cog itself.
    build.macos32x86/gdbarm32 - Support libraries for the GdbARMPlugin which
                                is used to develop Cog itself.

and the intention is to add such directories to contain e.g. support code for the Pharo Cairo and Freetype plugins, and anything else needed. By placing support directories in each build directory they can be shared between various branded VM builds, avoiding duplication.

There exist

	build.macos32x86/common - Gnu Makefiles for building the various branded VMs
	build.macos64x64/common - Gnu Makefiles for building the various branded VMs
	build.win32x86/common   - Gnu Makefiles for building the various branded VMs

And the intention is to add build.linuxNN????/common as soon as possible to use Gnu Makefiles to build all VMs on all platfrms.

The scripts directory contains various scripts for validating and checking-in generated sources, packaging builds into installable artifacts (tar, msi, zip), and so on. The linux builds and the packaging scripts produce outputs in the products directory tree. The packaging scripts may choose to include Smalltalk source files included in the sources directory.

Other directories

The platforms directory contains the associated platform-specific files that combine with the Slang-generated source to produce complete VMs. The structure is

	platforms/Mac OS/vm
	platforms/Mac OS/plugins

Each vm directory contains support for the core VM. Each plugin directory contains run-time and build-time support for various plugins. The following directories are subtrees that are shared with the old Squeak interpreter source:

Being subtrees, their history is actually merged into the branch, but can be pushed separately as well. If you're not familiar with subtrees or git, the easiest is to use the scripts/gitciplugins script to check in any changes to the subtrees and push them to their respective branches.

The processors directory contains the source for various processor simulators. The JIT is developed in Smalltalk by using one of these processor simulators to execute the code the JIT produces. Currently only the Bochs x86/x86-64 simulator and the gdbarm simulator are in use, for x86 and ARMv5 respectively.

Finally the image directory contains scripts that will build a "VMMaker" image, a Squeak Smalltalk image containing all the packages that comprise the Cog system, suitable for developing the VM and for generating (or updating) the sources in the vm source directories. There is also a script for generating a 64-bit Spur image from a 32-bit Spur image.

Eliot Miranda June 2016

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].