Lines Matching full:should

20 This section outlines common requirements that should be considered while designing the interpreter
23 1. The platform should scale from microcontrollers to hi-end mobile phones:
24     1. It should fit into 50Kb of ROM.
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.
27 1. The platform should support multiple programming languages
33 1. Bytecode should allow the interpreter to run no slower than state of the art interpreters.
34 1. Bytecode should be compact in size to avoid bloating application code.
35 1. Bytecode description should have a single entry point to simplify maintenance
73 1. All entities in the executable file should be encoded and stored compactly to avoid bloating
75 1. Format should enforce as "flat" layout as possible: referencing metadata from other metadata
76    should be kept at minimum to reduce access overhead during runtime.
77 1. Runtime memory footprint of executable files should be low.
90    require explicitly how structures should be located relative to each other.
116 1. Interpreter should run no slower than state of the art interpreters.
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.
135     1. The "heaviness" of language semantics that interpreters should implement.
141 1. Panda should scale onto a wide range of devices, including IoT devices. Although more and
158 1. All virtual registers should explicitly and precisely distinct between garbage collectable
160 1. Virtual registers should be able to hold following types: unsigned and signed integers with
163 1. Virtual stack should abstract limitations possibly imposed by the host stack.
202 1. Interpreter should allow testing without involving front-ends of concrete languages.
203 1. Interpreter should allow early testing.
204 1. Interpreter should allow early benchmarking.