Lines Matching refs:VM

9 > 1. We need to be clear on our goals for the VM.  Do we want to emphasize
10 >    portability and safety like the Java VM?  Or shall we focus on the
18 1. The VM code is NOT guaranteed safe in a java sense.  Doing so makes it
31      VM.  Performance is not wonderful, but it works right.
36      we could sign the generated VM code with a host specific private
48    for value add.  The nice safe "sandbox" VM can be provided as a layer
58 >    a. A single-assignment VM, which we've both already been thinking
62 however, by the prospect of a minimally allocated VM representation... I
78    VM).  This is the point that disallows java style bytecodes, where all
87 >    b. A strongly-typed VM.  One question is do we need the types to be
93      in the VM representation.  I believe that the number of additional
97      a uniform way for the entire VM... so that C functions can call Java
100 >    c. How do we get more high-level information into the VM while keeping
101 >       to a low-level VM design?
115    to support dynamic loading of VM code as well.  This makes the job of
121 6. Define a set of generally useful annotations to add to the VM