A low Overhead Per Object Write Barrier ...
Document type :
Communication dans un congrès avec actes
DOI :
Title :
A low Overhead Per Object Write Barrier for the Cog VM
Author(s) :
Bera, Clément [Auteur]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Analyses and Languages Constructs for Object-Oriented Application Evolution [RMOD]
Conference title :
IWST 16
City :
Pragues
Country :
République tchèque
Start date of the conference :
2016
Journal title :
Proceedings of the 11th edition of the International Workshop on Smalltalk Technologies
English keyword(s) :
Store Check
Language Virtual Machine
Just-in-Time Com-pilation
Interpreter
Write Barrier
Language Virtual Machine
Just-in-Time Com-pilation
Interpreter
Write Barrier
HAL domain(s) :
Informatique [cs]/Langage de programmation [cs.PL]
English abstract : [en]
In several Smalltalk implementations, a program can mark any object as read-only (unfortunately incorrectly sometimes miscalled immutable). Such read-only objects cannot be mutated unless the program explicitly revert them ...
Show more >In several Smalltalk implementations, a program can mark any object as read-only (unfortunately incorrectly sometimes miscalled immutable). Such read-only objects cannot be mutated unless the program explicitly revert them to a writable state. This feature, called write barrier, may induce noticeable overhead if not implemented carefully, both in memory footprint and execution time. In this paper I discuss the recent addition of the write barrier in the Cog virtual machine and the support introduced in the Pharo 6 image. I detail specific aspects of the implementation that allows, according to multiple evaluations presented in the paper, to have such a feature with little to no overhead.Show less >
Show more >In several Smalltalk implementations, a program can mark any object as read-only (unfortunately incorrectly sometimes miscalled immutable). Such read-only objects cannot be mutated unless the program explicitly revert them to a writable state. This feature, called write barrier, may induce noticeable overhead if not implemented carefully, both in memory footprint and execution time. In this paper I discuss the recent addition of the write barrier in the Cog virtual machine and the support introduced in the Pharo 6 image. I detail specific aspects of the implementation that allows, according to multiple evaluations presented in the paper, to have such a feature with little to no overhead.Show less >
Language :
Anglais
Peer reviewed article :
Oui
Audience :
Internationale
Popular science :
Non
Collections :
Source :
Files
- https://hal.archives-ouvertes.fr/hal-01356338/document
- Open access
- Access the document
- https://hal.archives-ouvertes.fr/hal-01356338/document
- Open access
- Access the document
- https://hal.archives-ouvertes.fr/hal-01356338/document
- Open access
- Access the document
- document
- Open access
- Access the document
- HAL.pdf
- Open access
- Access the document
- document
- Open access
- Access the document
- HAL.pdf
- Open access
- Access the document