FRANK NATHAN YELLIN
Pilots at Beresford Ave, Redwood City, CA

6745386, Jun 1, 2004

Mar 9, 2000

09/522268

Frank N. Yellin - Redwood City CA

Sun Microsystems, Inc. - Palo Alto CA

G06F 944

717166, 717139, 717140

An authoring system prepares a specified set of classes for preloading in client devices lacking a virtual memory manager. The authoring system converts the specified set of classes into a plurality of resource modules, a subset of the resource modules each including items that have pointers to items in other ones of the resource modules. The authoring system generates a load module, for loading into the client devices, that includes the plurality of resource modules, an interpreter and a startup procedure. The interpreter is for executing, on the client devices, programs in a predefined computer language. The specified set of classes includes methods in the predefined computer language. The startup procedure is for execution by the client devices when loading the interpreter for execution. The startup procedure replaces pointers in the resource modules with updated pointers in accordance with actual memory locations of the resource modules in any particular one of the client devices. The resource modules include a class table resource module, a method table resource module, a field table resource module, a constant pool resource module and a string resource module.

6477702, Nov 5, 2002

Nov 9, 2000

09/711053

Frank Yellin - Redwood City CA
James A. Gosling - Woodside CA

Sun Microsystems, Inc. - Santa Clara CA

G06F 945

717126

A program interpreter for computer programs written in a bytecode language, which uses a restricted set of data type specific bytecodes. The interpreter, prior to executing any bytecode program, executes a bytecode program verifier procedure that verifies the integrity of a specified program by identifying any bytecode instruction that would process data of the wrong type for such a bytecode and any bytecode instruction sequences in the specified program that would cause underflow or overflow of the operand stack. If the program verifier finds any instructions that violate predefined stack usage and data type usage restrictions, execution of the program by the interpreter is prevented. After pre-processing of the program by the verifier, if no program faults were found, the interpreter executes the program without performing operand stack overflow and underflow checks and without performing data type checks on operands stored in operand stack. As a result, program execution speed is greatly improved.

5999731, Dec 7, 1999

Mar 24, 1998

9/046719

Frank Yellin - Redwood City CA
James A. Gosling - Woodside CA

Sun Microsystems, Inc. - Palo Alto CA

G06F 945

395704

A program interpreter for computer programs written in a bytecode language, which uses a restricted set of data type specific bytecodes. The interpreter, prior to executing any bytecode program, executes a bytecode program verifier procedure that verifies the integrity of a specified program by identifying any bytecode instruction that would process data of the wrong type for such a bytecode and any bytecode instruction sequences in the specified program that would cause underflow or overflow of the operand stack. If the program verifier finds any instructions that violate predefined stack usage and data type usage restrictions, execution of the program by the interpreter is prevented. After pre-processing of the program by the verifier, if no program faults were found, the interpreter executes the program without performing operand stack overflow and underflow checks and without performing data type checks on operands stored in operand stack. As a result, program execution speed is greatly improved.

6247171, Jun 12, 2001

Dec 6, 1999

9/454821

Frank Yellin - Redwood City CA
James A. Gosling - Woodside CA

Sun Microsystems, Inc. - Mountain View CA

G06F 945

717 4

A program interpreter for computer programs written in a bytecode language, which uses a restricted set of data type specific bytecodes. The interpreter, prior to executing any bytecode program, executes a bytecode program verifier procedure that verifies the integrity of a specified program by identifying any bytecode instruction that would process data of the wrong type for such a bytecode and any bytecode instruction sequences in the specified program that would cause underflow or overflow of the operand stack. If the program verifier finds any instructions that violate predefined stack usage and data type usage restrictions, execution of the program by the interpreter is prevented. After pre-processing of the program by the verifier, if no program faults were found, the interpreter executes the program without performing operand stack overflow and underflow checks and without performing data type checks on operands stored in operand stack. As a result, program execution speed is greatly improved.

7080363, Jul 18, 2006

Nov 5, 2002

10/288323

Frank Yellin - Redwood City CA, US
James A. Gosling - Woodside CA, US

Sun Microsystems, Inc. - Santa Clara CA

G06F 9/45

717139

A program interpreter for computer programs written in a bytecode language, which uses a restricted set of data type specific bytecodes. The interpreter, prior to executing any bytecode program, executes a bytecode program verifier procedure that verifies the integrity of a specified program by identifying any bytecode instruction that would process data of the wrong type for such a bytecode and any bytecode instruction sequences in the specified program that would cause underflow or overflow of the operand stack. If the program verifier finds any instructions that violate predefined stack usage and data type usage restrictions, execution of the program by the interpreter is prevented. After pre-processing of the program by the verifier, if no program faults were found, the interpreter executes the program without performing operand stack overflow and underflow checks and without performing data type checks on operands stored in operand stack. As a result, program execution speed is greatly improved.

6061520, May 9, 2000

Apr 7, 1998

9/055947

Frank Yellin - Redwood City CA
Richard D. Tuck - San Francisco CA

Sun Microsystems, Inc. - Palo Alto CA

G06F 945, G06F 300

395705

The disclosed system represents an improvement over conventional systems for initializing static arrays by reducing the amount of code executed by the virtual machine to statically initialize an array. To realize this reduction, when consolidating class files, the preloader identifies all <clinit> methods and play executes these methods to determine the static initialization performed by them. The preloader then creates an expression indicating the static initialization performed by the <clinit> method and stores this expression in the. mclass file, replacing the <clinit> method. As such, the code of the <clinit> method, containing many instructions, is replaced by a single expression instructing the virtual machine to perform static initialization, thus saving a significant amount of memory. The virtual machine is modified to recognize this expression and perform the appropriate static initialization of an array.

5761513, Jun 2, 1998

Jul 1, 1996

8/671304

Frank Yellin - Redwood City CA
William N. Joy - Aspen CO
Arthur A. Van Hoff - Mountain View CA

Sun Microsystems, Inc. - Mountain View CA

G06F 945

395705

A compiler requires normal exceptions that are throwable by a method to be either explicitly declared or else "caught" by appropriate exception handlers in the method to be compiled. This ensures that all normal exceptions thrown will be handled by a programmer specified exception handler. The compiler inspects all instructions in a specified method that throw exceptions and all instructions that invoke other methods, and determines whether each type of exception throwable by those instructions and invocable methods is (A) a serious exception (i. e. , not a normal exception), (B) is caught by an enclosing exception handler, or (C) is explicitly declared in the method header of the specified method. If any throwable exception cannot be so categorized, that means the throwable exception is a normal exception that is not caught by an enclosing exception and is not explicitly declared in the method header, which means that the method to be compiled is not well formed. As a result, the compiler rejects the specified method, aborting compilation and generating an appropriate error message.

5778231, Jul 7, 1998

Dec 20, 1995

8/575356

Arthur A. van Hoff - Mountain View CA
James A. Gosling - Woodside CA
Frank Yellin - Redwood City CA

Sun Microsystems, Inc. - Mountain View CA

G06F 945

395705

A program compiler identifies each symbol in a source program that references another program. For each identified symbol, the compiler determines whether the symbol is a reference to a remotely located file or to a locally stored file. If the identified symbol is a reference to a remotely located file, it constructs a file location identifier, such as a URL, for the identified symbol, performs a file location identifier based fetch of the remotely locate file, and ads at least a portion of the fetched file to a set of program code to be compiled if the fetch is successfully performed. If the identified symbol is a reference to a locally stored file, it performs a file fetch for the locally stored file, adding at least a portion of the fetched file to the set of program code to be compiled if the file fetch is successfully performed. If the fetch is unsuccessful, compilation of the source program is aborted. When a client computer attempts to initiate execution of a specified program, the program executed determines a source update date associated with a source program associated with the specified program and also determines if a compiled version of the source program is present on the client computer.

7966607, Jun 21, 2011

Dec 22, 2004

11/021148

Ioi K. Lam - Mountain View CA, US
Frank N. Yellin - Redwood City CA, US
Oleg A. Pliss - Santa Clara CA, US

Oracle America, Inc. - Redwood Shores CA

G06F 9/44, G06F 9/445

717148, 717120, 717153, 718 1, 718100, 707813, 707814, 707816, 707817

One embodiment of the present invention provides a system that facilitates managing compiled program methods in a unified heap. The system partitions the unified heap into a first area and a second area. This allows the system to store objects other than compiled program methods and temporary compiler data structures in the first area, and to store compiled program methods and temporary compiler data structures in the second area.

5946489, Aug 31, 1999

Dec 12, 1997

8/989848

Frank Yellin - Redwood City CA
Dean R. E. Long - Boulder Creek CA
Richard D. Tuck - San Francisco CA

Sun Microsystems, Inc. - Palo Alto CA

G06F 9445

395705

A method of cross-compiling computer programs includes the step of extracting constants from an inheriting computer program written in a first computer language. The extracted constants refer to a generating computer program written in a second computer language. A new program in the second computer language is then created using the constants. The new program is then compiled for a target computer to ascertain compiled constant values. The compiled constant values are then substituted into the inheriting computer program to produce a final inheriting computer program.