Method and apparatus for facilitating lazy type tagging for compiled activations

1. A method for type tagging values in a compiled activation frame to facilitate garbage collection, wherein the method operates in a mixed-mode system that supports both interpretation of byte codes and execution of compiled native code, the method comprising:

receiving an invocation of a method;

creating an activation frame for the method on the execution stack;

interpreting byte code methods;

wherein if the method is executing in interpreted mode, the interpretation involves maintaining a tag for each value in the activation frame during execution, wherein a given tag indicates whether a given value is a reference type or a primitive type; and

wherein if the method is executing in compiled mode,

prior to receiving the invocation for the method, the method further comprises:

compiling byte codes of the method into native code; wherein the compilation process involves gathering type information for each value in the activation frame of the method and embedding the type information into the native code associated with the method, and

creating the activation frame involves allocating space for tags for each value in the activation frame, wherein a given tag indicates whether a given value is a reference type or a primitive type;

wherein operations to store type information into the tags in the activation frame are deferred until a subsequent garbage collection operation takes place.

2. The method of claim 1 , wherein embedding the type information into the native code involves storing the type information as bit vectors, wherein each bit specifies whether a corresponding value in the activation frame is a primitive type or a reference type.

3. The method of claim 2 , wherein the bit vectors are embedded in operands of dummy instructions in the native code.

4. The method of claim 2 , wherein the bit vectors are embedded at locations following instructions in the native code that invoke other methods or the runtime system.

5. The method of claim 1 , further comprising performing a garbage collection operation, wherein the garbage collection operation involves:

retrieving type information from the native code; and

storing the type information in the tags in the activation frame of the method.

6. The method of claim 1 , wherein the activation frame for the method created while executing in compiled mode and the activation frame for the method created while executing in interpreted mode are identical in structure.

7. A computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for type tagging values in a compiled activation frame to facilitate garbage collection, wherein the method operates in a mixed-mode system that supports both interpretation of byte codes and execution of compiled native code, the method comprising:

receiving an invocation of a method;

creating an activation frame for the method on the execution stack;

interpreting byte code methods;

wherein if the method is executing in interpreted mode, the interpretation involves maintaining a tag for each value in the activation frame during execution, wherein a given tag indicates whether a given value is a reference type or a primitive type; and

wherein if the method is executing in compiled mode,

prior to receiving the invocation for the method, the method further comprises:

compiling byte codes of the method into native code; wherein the compilation process involves gathering type information for each value in the activation frame of the method and embedding the type information into the native code associated with the method, and

creating the activation frame involves allocating space for tags for each value in the activation frame, wherein a given tag indicates whether a given value is a reference type or a primitive type;

wherein operations to store type information into the tags in the activation frame are deferred until a subsequent garbage collection operation takes place.

8. The computer-readable storage medium of claim 7 , wherein embedding the type information into the native code involves storing the type information as bit vectors, wherein each bit specifies whether a corresponding value in the activation frame is a primitive type or a reference type.

9. The computer-readable storage medium of claim 8 , wherein the bit vectors are embedded in operands of dummy instructions in the native code.

10. The computer-readable storage medium of claim 8 , wherein the bit vectors are embedded at locations following instructions in the native code that invoke other methods or the runtime system.

11. The computer-readable storage medium of claim 7 , wherein the method further comprises performing a garbage collection operation, wherein the garbage collection operation involves:

retrieving type information from the native code; and

storing the type information in the tags in the activation frame of the method.

12. The computer-readable storage medium of claim 7 , wherein the activation frame for the method created while executing in compiled mode and the activation frame for the method created while executing in interpreted mode are identical in structure.

13. An apparatus for type tagging values in a compiled activation frame to facilitate garbage collection, wherein the apparatus is configured to operate in a mixed-mode system that supports both interpretation of byte codes and execution of compiled native code, comprising:

a receiving mechanism configured to receive an invocation of a method;

a creation mechanism configured to create an activation frame for the method on the execution stack;

an interpretation mechanism configured to interpret byte code methods;

wherein if the method is executing in interpreted mode, the interpretation mechanism is configured to maintain a tag for each value in the activation frame during execution, wherein a given tag indicates whether a given value is a reference type or a primitive type; and

wherein if the method is executing in compiled mode, the compilation mechanism is configured to compile byte codes of the method into native code;

wherein the compilation mechanism includes,

a collection mechanism configured to gather type information for each value in the activation frame of the method; and

an embedding mechanism configured to embed the type information into the native code associated with the method, and

the creation mechanism is configured to allocate space for tags for each value in the activation frame, wherein a given tag indicates whether a given value is a reference type or a primitive type;

wherein operations to store type information into the tags in the activation frame are deferred until a subsequent garbage collection operation takes place.

14. The apparatus of claim 13 , wherein the embedding mechanism is configured to store the type information as bit vectors, wherein each bit specifies whether a corresponding value in the activation frame is a primitive type or a reference type.

15. The apparatus of claim 14 , wherein the bit vectors are embedded in operands of dummy instructions in the native code.

16. The apparatus of claim 14 , wherein the bit vectors are embedded at locations following instructions in the native code that invoke other methods or the runtime system.

17. The apparatus of claim 13 , further comprising a garbage collection mechanism, wherein the garbage collection mechanism includes:

a retrieval mechanism configured to retrieve type information from the native code; and

a storage mechanism configured to store the type information in the tags in the activation frame of the method.

18. The apparatus of claim 13 , wherein the activation frame for the method created while executing in compiled mode and the activation frame for the method created while executing in interpreted mode are identical in structure.