Lines Matching full:on

13 | Rationale                       | Elaborates on the rationales behind the decisions.         |
26 1. Program execution via bytecode interpretation should be enabled on all targets.
49 For the rationale on the bytecode type, please see [here](rationale-for-bytecode.md).
51 Rationale on the machine-readable instruction set architecture is following. Since bytecode
88    respective files on demand.
96 for the same application introduces extra duplication of metadata and implies extra burden on
102 select the optimal size based on actual code base.
117 1. Interpreter should be portable enough to run on targets from IoT devices
119 1. Interpreter should not create extra pressure on the host system.
125 1. Interpreter does not depend on C++ standard library. All necessary classes, containers, etc.
137        implemented in another language that runs on the platform may run slower because of
140    for statically typed languages that run on the platform natively, and 15x-20x for L2 languages.
143    on the device. Since static linking with a subset of the library is a pain and may not guarantee
162    to the objects on 32-bit and 64-bit architectures.
173 1. By default virtual stack is not mapped to a host stack, instead it is allocated on heap using
180 1. Although tagged virtual registers occupy more memory (especially on 64-bit architectures),
181    redundant memory consumption is cheaper than ongoing runtime penalties on garbage collector
182    trying to distinguish between objects from non-objects on an "imprecise" stack.
184    or `sizeof(double)` or `sizeof(void *)` on a 64-bit architecture (i.e. theoretical maximum
189    on IoT devices. On such devices the size of the host stack may be severely limited: as a result,