Interrupt handling mechanism in translator from one...

Data processing: software development – installation – and managem – Software program development tool – Translation of code

Reexamination Certificate

Rate now

  [ 0.00 ] – not rated yet Voters 0   Comments 0

Details

C714S034000

Reexamination Certificate

active

06718539

ABSTRACT:

FIELD OF THE INVENTION
The present invention relates to interrupt handling generally and, more particularly, to an apparatus and/or method for seamlessly handling interrupts during translation of one instruction set to another instruction set.
BACKGROUND OF THE INVENTION
Java is a programming language invented by Sun Microsystems, Inc. Applications developed using the Java language can be run on any platform equipped with a Java Virtual Machine (JVM). Applications written with Java can not match the performance of applications written in C/C++ and complied directly into a native code. Several techniques to reduce the performance gap have been developed. However, while the techniques are successful in terms of narrowing the performance gap, the success is at the cost of extra memory foot-print or a lack of compatibility to past designs.
There are several major factors contributing to the lack of performance. Two of the larger factors are the need to perform garbage collection and the stack machine nature of the JVM. Garbage collection can constitute about 20-30% of the overall processing, while Java instruction execution uses the rest, including thread synchronization. Garbage collection consumes a substantial part of the total computing resources of the JVM. Performance could be improved by reducing the MIPS count for the garbage collection.
However, the largest factor contributing to the slow performance is the execution of the Java instructions. The execution of Java instructions uses a stack based architecture. The stack based architecture is well known for having a compact code size. However, the stack based architecture is also notoriously known for poor performance. Such an architecture reduces the options for compiler optimizations, and for runtime optimizations (such as using several functional units, as is done with super-scalar machines).
Three conventional techniques have been devised for speeding up the execution of Java instructions. However, each of the alternatives has a major penalty in some other aspect. The first technique uses Just In Time (JIT) technology to first translate the Java instructions while being downloaded into a processor native machine code. The processor native code version of the Java instructions contains all possible optimizations done by the JIT compiler during load time. The result is a fast executing native code that can require 4 or more times as much code memory (program space). The larger memory requirement almost instantly prohibits the use of JIT for embedded devices, where the memory is an expensive resource.
The second technique (i.e., HotSpot) generates optimized native code only for the parts of the Java instructions that are executed most of the time. Generating native code for only the most executed Java instructions requires on-the-fly profiling, and from time to time compilation tasks, that slow down the execution. The result can be a faster execution of the Java instructions on average. However, although the memory requirements are more reasonable, the speedup is not as good as can be provided by the JIT technique. Generating native code for only the most executed Java instructions might be more suitable for embedded systems, but the memory penalty can still be large without a drastic performance boost.
The third technique involves a full hardware implementation of the JVM (i.e., HW-JVM or a picoJava core). The full hardware implementation of the JVM can provide a very fast executing machine. However, in order to use the full hardware implementation of the JVM, legacy code must be completely rewritten in Java. Therefore, the third technique is not backward compatible with older machines.
It would be desirable to have an apparatus and/or method for providing fast JAVA bytecode execution with a very low memory footprint and without requiring rewriting of code that could seamlessly handle interrupts to a host processor.
SUMMARY OF THE INVENTION
The present invention concerns an apparatus comprising a translator circuit and a cache. The translator circuit may be configured to (i) translate one or more first instruction codes of a first instruction set into second instruction codes of a second instruction set and (ii) present the second instruction codes to a processor and the cache in response to a predetermined number of addresses.
The objects, features and advantages of the present invention include providing an apparatus and/or method for translating an unlimited sequence of instructions using a limited program space of a general purpose processor that may (i) provide for fast execution of Java instructions, (ii) be used in embedded systems, and/or (iii) maintain backward compatibility for legacy code.


REFERENCES:
patent: 5704034 (1997-12-01), Circello
patent: 6035422 (2000-03-01), Hohl et al.
patent: 6467082 (2002-10-01), D'Arcy et al.
patent: 6631514 (2003-10-01), Le
Ozer et al. A Fast Interrupt Handling Scheme for VLIW Processors. IEEE.*
Torng et al. Interrupt Handling for Out-of-Order Execution Processors. IEEE. 1993. pp. 122-127.

LandOfFree

Say what you really think

Search LandOfFree.com for the USA inventors and patents. Rate them and share your experience with other people.

Rating

Interrupt handling mechanism in translator from one... does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Interrupt handling mechanism in translator from one..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Interrupt handling mechanism in translator from one... will most certainly appreciate the feedback.

Rate now

     

Profile ID: LFUS-PAI-O-3195689

  Search
All data on this website is collected from public sources. Our data reflects the most accurate information available at the time of publication.