2013 International Conference on MOBILe Wireless MiddleWARE, Operating Systems, and Applications 2013
DOI: 10.1109/mobilware.2013.17
|View full text |Cite
|
Sign up to set email alerts
|

A Virtual Machine for the Insense Language

Abstract: The Insense VM is a specialised Java virtual machine for running Insense programs on wireless sensor nodes. The VM runs on top of InceOS, a purpose-built operating system. A split VM architecture is used, in which Insense programs are compiled to Java classes, then linked and compacted on a more powerful machine into a form suitable for execution by the VM. Measurements demonstrate that the virtual machine achieves good performance and memory usage for realistic Insense programs.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2020
2020
2021
2021

Publication Types

Select...
1
1

Relationship

1
1

Authors

Journals

citations
Cited by 2 publications
(3 citation statements)
references
References 41 publications
0
3
0
Order By: Relevance
“…EnsembleS is implemented in C, and supports reference-counted garbage collection and exceltions. Applications are compiled to Java source code, and then to custom Java class files for use with a custom VM [10]. These applications can be executed on the desktop, parallel accelerators (e.g.…”
Section: Methodsmentioning
confidence: 99%
See 1 more Smart Citation
“…EnsembleS is implemented in C, and supports reference-counted garbage collection and exceltions. Applications are compiled to Java source code, and then to custom Java class files for use with a custom VM [10]. These applications can be executed on the desktop, parallel accelerators (e.g.…”
Section: Methodsmentioning
confidence: 99%
“…Next, the boot clause binds the actor's channels together (line 22, discussed later in § 3.3). Once bound, the sender actor sends the contents of value on its channel, increments it, and goes back to the beginning of its behaviour loop (lines [8][9][10][11]. The receiver actor waits for a message, binds the message to data, displays it, and returns to the top of its behaviour loop (lines [14][15][16][17][18].…”
Section: Ensembles: Basic Language Featuresmentioning
confidence: 99%
“…However, this choice often forces to sacrifice features for acceptable resource consumption, leading to partial implementations [ 3 , 4 , 5 , 6 ]. More generally, high-level languages are not easily applicable to embedded devices programming and resource constraints are major issues in developing and debugging such systems [ 7 ].…”
Section: Introductionmentioning
confidence: 99%