DOCSLIB.ORG

Two Decades of Smalltalk VM Development: Live VM Development Through Simulation Tools Eliot Miranda, Clément Bera, Elisa Gonzalez Boix, Dan Ingalls

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Two Decades of Smalltalk VM Development: Live VM Development Through Simulation Tools Eliot Miranda, Clément Bera, Elisa Gonzalez Boix, Dan Ingalls Two Decades of Smalltalk VM Development: Live VM development through Simulation Tools Eliot Miranda, Clément Bera, Elisa Gonzalez Boix, Dan Ingalls To cite this version: Eliot Miranda, Clément Bera, Elisa Gonzalez Boix, Dan Ingalls. Two Decades of Smalltalk VM Development: Live VM development through Simulation Tools. Virtual Machines and Language Implementations VMIL 2018, 2018, Boston, United States. 10.1145/3281287.3281295. hal-01883380 HAL Id: hal-01883380 https://hal.archives-ouvertes.fr/hal-01883380 Submitted on 8 Oct 2018 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Two Decades of Smalltalk VM Development Live VM development through Simulation Tools Eliot Miranda Clément Béra Feenk Software Languages Lab San Francisco, California Vrije Universiteit Brussel [email protected] Brussel, Belgium [email protected] Elisa Gonzalez Boix Dan Ingalls Software Languages Lab ARCOS Vrije Universiteit Brussel Aptos, California Brussel, Belgium [email protected] [email protected] Abstract [BDN+07], an open-source Smalltalk dialect, and its VM + OpenSmalltalk-VM is a virtual machine (VM) for languages [IKM 97], written in Smalltalk using the code from Smalltalk- in the Smalltalk family (e.g. Squeak, Pharo) which is itself 80 [GR83] as a starting point. Part of the code base was, how- written in a subset of Smalltalk that can easily be translated ever, narrowed down to a subset of Smalltalk, called Slang, to to C. Development is done in Smalltalk, an activity we call allow Smalltalk to C compilation. Development was done in “Simulation”. The production VM is derived by translating Smalltalk, an activity we call "Simulation", and the support the core VM code to C. As a result, two execution models code for which is "The Simulator". The production VM is coexist: simulation, where the Smalltalk code is executed on derived by translating the core VM code to C, combining top of a Smalltalk VM, and production, where the same code this generated C code with a set of platform-specific support is compiled to an executable through a C compiler. files, and compiling with the platform’s C compiler. In this paper, we detail the VM simulation infrastructure Two execution models were effectively available, simu- and we report our experience developing and debugging the lation, where the Smalltalk code is executed on top of a garbage collector and the just-in-time compiler (JIT) within Smalltalk VM, and production, where the same code is com- it. Then, we discuss how we use the simulation infrastructure piled to executable code through the C compiler. Simulation to perform analysis on the runtime, directing some design is used to develop and debug the VM. Production is used 1 decisions we have made to tune VM performance. to release the VM. Dummy Smalltalk message sends were used to embed meta information in the code, such as self var: CCS Concepts • Software and its engineering → Run- ’foo’ type: ’char *’ which have no effect during simulation but time environments; Just-in-time compilers; Interpreters; guide the translation process of the executable Smalltalk. Keywords Just-in-Time compiler, garbage collector, virtual When the Squeak VM was released it consisted mainly in: machine, managed runtime, tools, live development • an interpreter with a spaghetti stack, ACM Reference Format: • a memory manager with a compact but complex object Eliot Miranda, Clément Béra, Elisa Gonzalez Boix, and Dan Ingalls. representation: a pointer-reversing tracing garbage 2018. Two Decades of Smalltalk VM Development: Live VM de- collector and a heap divided into two generations, velopment through Simulation Tools. In Proceedings of the 10th • WarpBlt, a rotation and scaling extension for the bit- ACM SIGPLAN International Workshop on Virtual Machines and based BitBlt graphics engine, Intermediate Languages (VMIL ’18), November 4, 2018, Boston, MA, • external C code and makefiles to support running the USA. ACM, New York, NY, USA, 10 pages. https://doi.org/10.1145/ VM on popular platforms. 3281287.3281295 The first three components of the VM were written en- 1 Introduction tirely in Slang. A few extra features, such as file management, To specify their virtual machine (VM), the Smalltalk-80 team were written both in Smalltalk for simulation purposes and at Xerox PARC wrote a Smalltalk VM entirely in Smalltalk in C for the production VM. [GR83]. In 1995, members of the same team built Squeak VMIL ’18, November 4, 2018, Boston, MA, USA 1 2018. ACM ISBN 978-1-4503-6071-5/18/11...$15.00 We use the Smalltalk terminology, send, to discuss virtual calls since we https://doi.org/10.1145/3281287.3281295 are talking about Smalltalk. VMIL ’18, November 4, 2018, Boston, MA, USA Eliot Miranda, Clément Béra, Elisa Gonzalez Boix, and Dan Ingalls Over the years, the Squeak VM evolved to give birth 2 Virtual Machine Simulation 2 recently to OpenSmalltalk-VM , the default VM for vari- The key idea of the Simulation is to allow developers to reuse + ous Smalltalk-like systems such as Pharo [BDN 09], Squeak the whole Smalltalk IDE including the browser, inspectors + + [BDN 07], Cuis, Croquet and Newspeak [BvdAB 10]. As the and debugger to develop the VM. Most new features can be VM evolved, the original simulator co-evolved as a tool to developed interactively, adding code to the VM at runtime, develop and debug the VM. The metadata used to guide the in the simulation environment, like Smalltalk programming. translation process was replaced by pragmas [DMP16]. But In this section we first briefly introduce the compilation the most significant evolution of the simulator came with the pipeline to generate the production VM and Smalltalk snap- introduction of the Just-In-Time compiler (JIT) [Mir11]. The shots, key elements to understand the design of the simu- spaghetti stack was mapped to a more conventional stack lation infrastructure. Then we describe the memory layout frame organisation in a stack zone of a few hundred kilobytes of both the production and simulation runtimes. Next we organised into small pages, a scheme called context-to-stack detail how VM execution is simulated and the interactions mapping [DS84, Mir99]. A JIT was written. Machine code with the simulated memory. In the following subsection, generated by the JIT was executed by binding multiple pro- we explain specific aspects of the simulation infrastructure cessor simulators (Bochs [Law96] for x86 and x64, SkyEye such as the simulation of the machine code generated by for ARMv6, Smalltalk code for 32-bit MIPS). Support for mul- the JIT through the processor simulator. The last subsection tiple bytecode sets was added, initially to support Newspeak, discusses simulation features related to the development of and more recently to support adaptive optimization. Finally, the JIT. a new object representation and garbage collector was added to improve performance and also to support 64 bits [MB15]. 2.1 Context This required refactoring the interpreter to allow the object 3 VM compilation. The VM executable is generated in a two representation to be chosen at start-up . Slang was also ex- step process. Firstly, the Slang-to-C compiler translates the tended with type inference to allow Smalltalk code that is Slang code (interpreter, JIT and GC code) to C code, generat- independent of word size by virtue of Smalltalk’s infinite ing a few C files. This first step usually takes several seconds. precision arithmetic to be used in both 32 and 64 bit contexts. Secondly, the C compiler (depending on the platform LLVM, One of the key design decisions in OpenSmalltalk-VM was GCC or MSVC) translates all the C files (generated C files to keep the core components (i.e. the interpreter, the JIT and and platform-specific C files) into an executable. This second the memory manager) written in Slang and not in C/C++. step can take up to a few minutes the first time. Subsequent By interpreting the Slang code as Smalltalk code, emulating compilations usually only take a few seconds, since object native code using an external processor simulator and simu- files for unchanged C files do not need to be recreated. lating the memory using a large byte array, it is possible to The VM can be configured in two main flavours, interpreter- simulate the whole VM execution. This allows development only or interpreter+JIT 5. Although the version with the JIT and debugging of the VM with the Smalltalk development is the most widely used in production, the interpreter version tools resulting in a live programming experience for VM 4 is convenient for development purposes and essential on de- development . vices that outlaw JITs. For example, debugging the garbage In this paper, we present key details of the Simulation collector or evaluating new language features can be done infrastructure, give examples that demonstrate its produc- in the interpreter-only VM, avoiding JIT complexity. tivity advantages, and discuss some of its limitations. The paper is structured as follows. Section 2 introduces the sim- Snapshots. Smalltalk is an object system, rather than a lan- ulation infrastructure used to develop and debug the VM. guage. The entire system, including its development tools Section 3 reports our experience developing the VM with the and application code is stored in a snapshot file, which is simulation infrastructure. Section 4 discusses some of the essentially a memory dump of the entire heap.
Load more

Recommended publications
  • Application-Level Virtual Memory for Object-Oriented Systems Mariano Martinez Peck
    Application-Level Virtual Memory for Object-Oriented Systems Mariano Martinez Peck To cite this version: Mariano Martinez Peck. Application-Level Virtual Memory for Object-Oriented Systems. Program- ming Languages [cs.PL]. Université des Sciences et Technologie de Lille - Lille I, 2012. English. tel-00764991 HAL Id: tel-00764991 https://tel.archives-ouvertes.fr/tel-00764991 Submitted on 26 Dec 2012 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. N° d’ordre : 40886 THESE présentée en vue d’obtenir le grade de DOCTEUR en Spécialité : informatique par Mariano MARTINEZ PECK DOCTORAT DELIVRE CONJOINTEMENT PAR MINES DOUAI ET L’UNIVERSITE DE LILLE 1 Titre de la thèse : Application-Level Virtual Memory for Object-Oriented Systems Soutenue le 29/10/2012 à 10h devant le jury d’examen : Président Jean-Bernard STEFANI (Directeur de recherche – INRIA Grenoble- Rhône-Alpes) Directeur de thèse Stéphane DUCASSE (Directeur de recherche – INRIA Lille) Rapporteur Robert HIRSCHFELD (Professeur – Hasso-Plattner-Institut, Universität Potsdam, Allemagne) Rapporteur Christophe DONY (Professeur – Université Montpellier 2) Examinateur Roel WUYTS (Professeur – IMEC & Katholieke Universiteit Leuven, Belgique) co-Encadrant Noury BOURAQADI (Maître-Assistant – Mines de Douai) co-Encadrant Marcus DENKER (Chargé de recherche – INRIA Lille) co-Encadrant Luc FABRESSE (Maître-Assistant – Mines de Douai) Laboratoire(s) d’accueil : Dépt.
    [Show full text]
  • Visualage for Smalltalk Handbook Volume 2: Features
    SG24-2219-00 VisualAge for Smalltalk Handbook Volume 2: Features September 1997 SG24-2219-00 International Technical Support Organization VisualAge for Smalltalk Handbook Volume 2: Features September 1997 IBM Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix A, “Special Notices.” First Edition (September 1997) This edition applies to VisualAge for Smalltalk, Versions 2, 3, and 4, for use with OS/2, AIX, and Microsoft Windows 95/NT. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. QXXE Building 80-E2 650 Harry Road San Jose, California 95120-6099 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1997. All rights reserved. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Preface . xiii How This Redbook Is Organized ....................... xiv ITSO on the Internet ................................ xv VisualAge Support on CompuServe ..................... xvii About the Authors ................................ xvii Acknowledgments . xviii Comments Welcome . xix Chapter 1. AS/400 Connection . 1 Multiple Programs with a Single Remote Procedure Call ......... 1 RPC Part Sets Commit Boundary ........................ 1 Connection Problem with V3R1 ......................... 2 AS/400 Communication Error .......................... 2 Strange Characters on Log-on Window .................... 3 Quick Form from AS/400 Record Classes ................... 3 Communication . 4 Read Next/Previous . 4 SQL Statements . 5 Data Queues and Records ............................ 6 ODBC Requirements .
    [Show full text]
  • Programming-8Bit-PIC
    Foreword Embedded microcontrollers are everywhere today. In the average household you will find them far beyond the obvious places like cell phones, calculators, and MP3 players. Hardly any new appliance arrives in the home without at least one controller and, most likely, there will be several—one microcontroller for the user interface (buttons and display), another to control the motor, and perhaps even an overall system manager. This applies whether the appliance in question is a washing machine, garage door opener, curling iron, or toothbrush. If the product uses a rechargeable battery, modern high density battery chemistries require intelligent chargers. A decade ago, there were significant barriers to learning how to use microcontrollers. The cheapest programmer was about a hundred dollars and application development required both erasable windowed parts—which cost about ten times the price of the one time programmable (OTP) version—and a UV Eraser to erase the windowed part. Debugging tools were the realm of professionals alone. Now most microcontrollers use Flash-based program memory that is electrically erasable. This means the device can be reprogrammed in the circuit—no UV eraser required and no special packages needed for development. The total cost to get started today is about twenty-five dollars which buys a PICkit™ 2 Starter Kit, providing programming and debugging for many Microchip Technology Inc. MCUs. Microchip Technology has always offered a free Integrated Development Environment (IDE) including an assembler and a simulator. It has never been less expensive to get started with embedded microcontrollers than it is today. While MPLAB® includes the assembler for free, assembly code is more cumbersome to write, in the first place, and also more difficult to maintain.
    [Show full text]
  • Toward Harnessing High-Level Language Virtual Machines for Further Speeding up Weak Mutation Testing
    2012 IEEE Fifth International Conference on Software Testing, Verification and Validation Toward Harnessing High-level Language Virtual Machines for Further Speeding up Weak Mutation Testing Vinicius H. S. Durelli Jeff Offutt Marcio E. Delamaro Computer Systems Department Software Engineering Computer Systems Department Universidade de Sao˜ Paulo George Mason University Universidade de Sao˜ Paulo Sao˜ Carlos, SP, Brazil Fairfax, VA, USA Sao˜ Carlos, SP, Brazil [email protected] [email protected] [email protected] Abstract—High-level language virtual machines (HLL VMs) have tried to exploit the control that HLL VMs exert over run- are now widely used to implement high-level programming ning programs to facilitate and speedup software engineering languages. To a certain extent, their widespread adoption is due activities. Thus, this research suggests that software testing to the software engineering benefits provided by these managed execution environments, for example, garbage collection (GC) activities can benefit from HLL VMs support. and cross-platform portability. Although HLL VMs are widely Test tools are usually built on top of HLL VMs. However, used, most research has concentrated on high-end optimizations they often end up tampering with the emergent computation. such as dynamic compilation and advanced GC techniques. Few Using features within the HLL VMs can avoid such problems. efforts have focused on introducing features that automate or fa- Moreover, embedding testing tools within HLL VMs can cilitate certain software engineering activities, including software testing. This paper suggests that HLL VMs provide a reasonable significantly speedup computationally expensive techniques basis for building an integrated software testing environment. As such as mutation testing [6].
    [Show full text]
  • Cobol Pic Clause Example
    Cobol Pic Clause Example Albuminous and sonsie Scarface never apotheosising nae when Nealon mischarges his hogs. Unlawful Ingmar clips contiguously and super, she revering her cookers benefit symmetrically. Trifoliate Chaim sometimes circularize his breaches see and dilly-dallies so dichotomously! Quetelet index file exactly the coefficient is not confuse the input procedure division resets the rerun in another accept message or paragraphs that? Early cobol example of examples are evaluated one having to pic x when clause is considered useless instructions and date formats will be made quickly than one. After a group item is never reserved words cannot be written under different format you can it occupies in an operational sign printed documentation is suppressed. Because they may be a sample program by requesting a short paragraph in each source item can be greater detail report item is impossible in the records. Exit program using pic n it will be only, or more sections into a pic clause is executed as shown in a file to. Duplicate keys or fetch a call to_char with input call to describe data description during execution of examples of this area b it! We delimit by cobol example illustrates this server outputs data division sections having one. Basic cobol example. The individual file is provided for pic x variables being defined by use of messages. The cobol picture indicates a cobol api to cobol pic clause example. This call function is defined width of the usage is to a table can you explicitly searched last sentence and pic clause scales as steps. No cobol example with clause indicates the pic clause specifies that truncation or.
    [Show full text]
  • The Future: the Story of Squeak, a Practical Smalltalk Written in Itself
    Back to the future: the story of Squeak, a practical Smalltalk written in itself Dan Ingalls, Ted Kaehler, John Maloney, Scott Wallace, and Alan Kay [Also published in OOPSLA ’97: Proc. of the 12th ACM SIGPLAN Conference on Object-oriented Programming, 1997, pp. 318-326.] VPRI Technical Report TR-1997-001 Viewpoints Research Institute, 1209 Grand Central Avenue, Glendale, CA 91201 t: (818) 332-3001 f: (818) 244-9761 Back to the Future The Story of Squeak, A Practical Smalltalk Written in Itself by Dan Ingalls Ted Kaehler John Maloney Scott Wallace Alan Kay at Apple Computer while doing this work, now at Walt Disney Imagineering 1401 Flower Street P.O. Box 25020 Glendale, CA 91221 [email protected] Abstract Squeak is an open, highly-portable Smalltalk implementation whose virtual machine is written entirely in Smalltalk, making it easy to debug, analyze, and change. To achieve practical performance, a translator produces an equivalent C program whose performance is comparable to commercial Smalltalks. Other noteworthy aspects of Squeak include: a compact object format that typically requires only a single word of overhead per object; a simple yet efficient incremental garbage collector for 32-bit direct pointers; efficient bulk- mutation of objects; extensions of BitBlt to handle color of any depth and anti-aliased image rotation and scaling; and real-time sound and music synthesis written entirely in Smalltalk. Overview Squeak is a modern implementation of Smalltalk-80 that is available for free via the Internet, at http://www.research.apple.com/research/proj/learning_concepts/squeak/ and other sites. It includes platform-independent support for color, sound, and image processing.
    [Show full text]
  • PIC Assembly Language for the Complete Beginner
    PIC Assembly Language for the Complete Beginner Michael A. Covington Artificial Intelligence Center The University of Georgia Athens, Georgia 30602-7415 http://www.ai.uga.edu/mc This article appeared in Electronics Now Magazine in 1999 and is reprinted here by permission. Some web addresses have been up- dated but the content has not; you will find that MPLAB, for instance, now looks somewhat different. You may print out this article for personal use but not for further pub- lication. Copyright c 1999 Gernsback Publications, Inc. Copyright c 1999, 2004 Michael A. Covington. These days, the field of electronics is divided into “haves” and “have- nots” – people who can program microcontrollers and people who can’t. If you’re one of the “have-nots,” this article is for you. 1 Microcontrollers are one-chip computers designed to control other equip- ment, and almost all electronic equipment now uses them. The average American home now contains about 100 computers, almost all of which are microcontrollers hidden within appliances, clocks, thermostats, and even automobile engines. Although some microcontrollers can be programmed in C or BASIC, you need assembly language to get the best results with the least expensive micros. The reason is that assembly language lets you specify the exact instructions that the CPU will follow; you can control exactly how much time and memory each step of the program will take. On a tiny computer, this can be important. What’s more, if you’re not already an experienced programmer, you may well find that assembly language is simpler than BASIC or C.
    [Show full text]
  • April 22 -- STEPS NSF 2012 Report
    ! 2012 REPORT ! STEPS Toward Expressive Programming Systems ! “A#Science#Experiment”# ! by# (In#random#order)#Yoshiki#Ohshima,#Dan#Amelang,#Ted#Kaehler,#Bert#Freudenberg,# Aran#Lunzer,#Alan#Kay,#Ian#Piumarta,#Takashi#Yamamiya,#Alan#Borning,#Hesam# Samimi,#Bret#Victor,#Kim#Rose*# VIEWPOINTS#RESEARCH#INSTITUTE# # # *These#are#the#STEPS#researchers#for#the#year#2012.#For#a#complete#listing# of#the#participants#over#the#length#of#the#project#see#the#section#on#the# NSF#site#which#contains#this#report.# TABLE OF CONTENTS — The STEPS Project for the General Public Summary of the STEPS project . Origin . STEPS aims at personal computing . What does STEPS look like? . STEPS is a “science project” . General approach . “T-shirt programming” . Overall map of STEPS . General STEPS results . Making “runnable maths” . Assessing STEPS Summary of STEPS research in 2012 . Inventing & building a language for STEPS “UI and applications”, and rewriting Frank in it . Producing a workable “chain of meaning” that extends from the screen all the way to the CPU . Inventing methods that create automatic visualizers for languages created from metalanguages . Continuing the start of “What vs How” programming via “Cooperating Languages and Solvers” Reflections on the STEPS Project to Date References Outreach Activities for final year of NSF part of the STEPS project Publications for the NSF part of the STEPS project Appendix I: KScript and KSWorld Appendix II: Making Applications in KSWorld ——— ! The$STEPS$Project$For$The$General$Public$ If#computing#is#important—for#daily#life,#learning,#business,#national#defense,#jobs,#and#
    [Show full text]
  • Smalltalk's Influence on Modern Programming
    1 Smalltalk’s Influence on Modern Programming Smalltalk’s Influence on Modern Programming Matt Savona. February 1 st , 2008. In September 1972 at Xerox PARC, Alan Kay, Ted Kaeher and Dan Ingalls were discussing programming languages in the hallway of their office building. Ted and Dan had begun to consider how large a language had to be to have “great power.” Alan took a different approach, and “asserted that you could define the "most powerful language in the world" in "a page of code."” Ted and Dan replied, “Put up or shut up” (Kay). And with that, the bet to develop the most powerful language was on. Alan arrived at PARC every morning at 4am for two weeks, and devoted his time from 4am to 8am to the development of the language. That language was Smalltalk. Kay had “originally made the boast because McCarthy's self-describing LISP interpreter was written in itself. It was about "a page", and as far as power goes, LISP was the whole nine- yards for functional languages.” He was sure that he could “do the same for object-oriented languages” and still have a reasonable syntax. By the eighth morning, Kay had a version of Smalltalk developed where “symbols were byte-coded and the receiving of return-values from a send was symmetric” (Kay). Several days later, Dan Ingalls had coded Kay’s scheme in BASIC, added a “token scanner”, “list maker” and many other features. “Over the next ten years he made at least 80 major releases of various flavors of Smalltalk” (Kay).
    [Show full text]
  • Type Feedback for Bytecode Interpreters Position Paper ICOOOLPS 2007
    Type Feedback for Bytecode Interpreters Position Paper ICOOOLPS 2007 Michael Haupt1, Robert Hirschfeld1, and Marcus Denker2 1 Software Architecture Group Hasso-Plattner-Institut University of Potsdam, Germany 2 Software Composition Group Institute of Computer Science and Applied Mathematics University of Berne, Switzerland michael.haupt,hirschfeld @hpi.uni-potsdam.de, [email protected] { } Abstract. This position paper proposes the exploitation of type feed- back mechanisms, or more precisely, polymorphic inline caches, for purely interpreting implementations of object-oriented programming languages. Using Squeak’s virtual machine as an example, polymorphic inline caches are discussed as an alternative to global caching. An implementation proposal for polymorphic inline caches in the Squeak virtual machine is presented, and possible future applications for online optimization are outlined. 1 Introduction Bytecode interpreters are small in size and comparatively easy to implement, but generally execute programs much less efficiently than just-in-time (JIT) compilers. Techniques like threaded interpretation [9, 11, 2] focus on speeding up bytecode interpretation itself, and caching [4, 5, 1] improves the performance of message sends—the most common operation in object-oriented software [7]. It is interesting to observe that, while threading mechanisms are used natu- rally to a varying degree in bytecode interpreter implementations, such systems usually employ only global caching to speed up dynamic method dispatch. A global cache is clearly beneficial with respect to overall performance. Still, it does not provide optimal support for polymorphic message send sites, and it does not allow for exploiting type information (we provide details on these issues in the following section). In our opinion, the employment of polymorphic inline caches (PICs) [5] instead can provide means for achieving significant speedups in bytecode interpreters while exhibiting only a moderate increase in memory footprint and implementation complexity.
    [Show full text]
  • A Tour of the Squeak Object Engine
    A Tour of the Squeak Object Engine A Tour of the Squeak Object Engine Tim Rowledge, [email protected] Introduction This chapter is intended to explain some basics of how a Virtual Machine (VM) works, why a VM is useful, what it does for the Squeak programmer and user, and how the Squeak VM might develop in the future. What is a Virtual Machine and why do we need one? A Virtual Machine provides us with a pretense of being a machine other than the actual hardware in use. Using one allows systems that behave differently than the host hardware to run as if on hardware designed for them. The term Object Engine is less commonly used but is a useful concept that includes the lowest system areas of the langauge environment running on the VM. Since there is often some flux in the definition of which components are within the actual VM and which are part of the supported environment, Object Engine is useful as a more inclusive term. The term Virtual Machine is used in several ways. When IBM refer to VM/CMS they are referring to a way of making a mainframe behave as if it is many machines, so that programs can assume they have total control even though they do not. Intel provide a somewhat similar facility in the x86 architecture(?), referred to as Virtual Mode. This sort of VM is a complete hardware simulation, often supported at the lowest level by the hardware. Another sort of VM is the emulator - SoftWindows for the Mac, Acorn's !PC, Linux's WINE are good examples - where another machine and/or OS is simulated to allow a Mac user to run Windows programs, an Acorn RiscPC or a Linux machine to run Windows98 programs and so on.
    [Show full text]
  • CONFERENCE COMPANION ESUG 2008 - 16Th International Smalltalk Conference
    ESUG-2008 CONFERENCE COMPANION ESUG 2008 - 16th International Smalltalk Conference CONTENTS Platinum Sponsors.......................................................................................................... 3 Gold Sponsors................................................................................................................ 4 Conference Location....................................................................................................... 5 Program Overview........................................................................................................... 8 Saturday, August 23...................................................................................................... 10 Sunday, August 24......................................................................................................... 10 Monday, August 25....................................................................................................... 11 Tuesday, August 26....................................................................................................... 16 Wednesday, August 27.................................................................................................. 20 Thursday, August 28...................................................................................................... 23 Friday, August 29........................................................................................................... 27 Program Overview........................................................................................................
    [Show full text]