Lines Matching full:be

20 This section outlines common requirements that should be considered while designing the interpreter
25     1. It should be able to run consuming 64Kb of RAM.
26 1. Program execution via bytecode interpretation should be enabled on all targets.
34 1. Bytecode should be compact in size to avoid bloating application code.
73 1. All entities in the executable file should be encoded and stored compactly to avoid bloating
76    should be kept at minimum to reduce access overhead during runtime.
77 1. Runtime memory footprint of executable files should be low.
85    and foreign (declared elsewhere). Local entities can be accessed directly by the offset
90    require explicitly how structures should be located relative to each other.
117 1. Interpreter should be portable enough to run on targets from IoT devices
132 1. Interpreters are by nature slower than native code execution. Slowdown can be explained by:
139 1. An ideal target would be 5x-10x slowdown factor (compared to native execution)
160 1. Virtual registers should be able to hold following types: unsigned and signed integers with
172    and can be reduced for memory-constrained targets and to 64 bits (using NaN-tagging technique).
175    hardcoded by design, it can be reconfigured for platforms where performance may benefit from
186    and padding. A lot of free space is expected to be in the padding area. Probably we may use it
189    on IoT devices. On such devices the size of the host stack may be severely limited: as a result,
192    constraint, which can be relaxed even further with the stackless interpreter (see above).
216 A general overview of managed assembly languages can be found [here](overview-of-managed-assemblers…