U.S. patent application number 11/096183 was filed with the patent office on 2005-12-01 for method frame storage using multiple memory circuits.
Invention is credited to O'Connor, James Michael, Tremblay, Marc.
Application Number | 20050267996 11/096183 |
Document ID | / |
Family ID | 27359254 |
Filed Date | 2005-12-01 |
United States Patent
Application |
20050267996 |
Kind Code |
A1 |
O'Connor, James Michael ; et
al. |
December 1, 2005 |
Method frame storage using multiple memory circuits
Abstract
A memory architecture in accordance with an embodiment of the
present invention improves the speed of method invocation.
Specifically, method frames of method calls are stored in two
different memory circuits. The first memory circuit stores the
execution environment of each method call, and the second memory
circuit stores parameters, variables or operands of the method
calls. In one embodiment the execution environment includes a
return program counter, a return frame, a return constant pool, a
current method vector, and a current monitor address. In some
embodiments, the memory circuits are stacks; therefore, the stack
management unit to cache can be used to cache either or both memory
circuits. The stack management unit can include a stack cache to
accelerate data transfers between a stack-based computing system
and the stacks. In one embodiment, the stack management unit
includes a stack cache, a dribble manager unit, and a stack control
unit. The dribble manager unit includes a fill control unit and a
spill control unit. Since the vast majority of memory accesses to
the stack occur at or near the top of the stack, the dribble
manager unit maintains the top portion of the stack in the stack
cache. When the stack-based computing system is popping data off of
the stack and a fill condition occurs, the fill control unit
transfer data from the stack to the bottom of the stack cache to
maintain the top portion of the stack in the stack cache.
Typically, a fill condition occurs as the stack cache becomes empty
and a spill condition occurs as the stack cache becomes full.
Inventors: |
O'Connor, James Michael;
(Mountain View, CA) ; Tremblay, Marc; (Palo Alto,
CA) |
Correspondence
Address: |
GUNNISON MCKAY & HODGSON, LLP
1900 GARDEN ROAD
SUITE 220
MONTEREY
CA
93940
US
|
Family ID: |
27359254 |
Appl. No.: |
11/096183 |
Filed: |
March 30, 2005 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
11096183 |
Mar 30, 2005 |
|
|
|
10346886 |
Jan 17, 2003 |
|
|
|
10346886 |
Jan 17, 2003 |
|
|
|
08787617 |
Jan 23, 1997 |
|
|
|
6532531 |
|
|
|
|
10346886 |
Jan 17, 2003 |
|
|
|
08647103 |
May 7, 1996 |
|
|
|
10346886 |
Jan 17, 2003 |
|
|
|
08642253 |
May 2, 1996 |
|
|
|
60010527 |
Jan 24, 1996 |
|
|
|
60010527 |
Jan 24, 1996 |
|
|
|
Current U.S.
Class: |
710/1 |
Current CPC
Class: |
G06F 2212/451 20130101;
G06F 9/264 20130101; G06F 9/449 20180201; G06F 15/7846 20130101;
G06F 9/30181 20130101; G06F 9/30021 20130101; G06F 9/345 20130101;
G06F 9/3017 20130101; G06F 9/30145 20130101; G06F 9/3802 20130101;
G06F 9/30174 20130101; G06F 9/30167 20130101; G06F 9/30134
20130101; G06F 9/45516 20130101; G06F 12/0875 20130101; G06F
9/45504 20130101 |
Class at
Publication: |
710/001 |
International
Class: |
G06F 003/00 |
Claims
1-56. (canceled)
57. A method of generating executable code for a computer program
in source code form, said method comprising: determining whether
said executable code is for execution by a microprocessor
communicatively connected to a network and receiving said
executable code therefrom for execution; determining whether said
executable code is for execution by a microprocessor connected to a
local memory and receiving said executable code therefrom for
execution; and generating a first executable code with code
verification in the event said first executable code is to be
received from said network for execution by said microprocessor; or
generating a second executable code without code verification in
the event said second executable code is to be received from said
local memory for execution by said microprocessor.
Description
RELATED APPLICATIONS
[0001] This application claims the benefit of U.S. Provisional
Application No. 60/010,527, filed Jan. 24, 1996, entitled "Methods
and Apparatuses for Implementing the JAVA Virtual Machine" (JAVA is
a trademark of Sun Microsystems, Inc.) and naming Marc Tremblay,
James Michael O'Connor, Robert Garner, and William N. Joy as
inventors, and is a continuation-in-part application of U.S.
application Ser. No. 08/647,103, filed May 7, 1996, entitled
"METHOD AND APPARATUS FOR STACK HARDWARE PARTITIONING FOR A
STACK-BASED TYPE PROCESSOR" naming James Michael O'Connor and Mark
Tremblay as inventors and U.S. application Ser. No. 08/642,253,
filed May 2, 1996, entitled "METHODS AND APPARATUSES FOR
IMPLEMENTING OPERAND STACK CACHE AS A CIRCULAR BUFFER" and naming
Marc Tremblay and James Michael O'Connor as inventors both of which
also claimed the benefit of U.S. Provisional Application No.
60/010,527, filed Jan. 24, 1996, entitled "Methods and Apparatuses
for Implementing the JAVA Virtual Machine" and naming Marc
Tremblay, James Michael O'Connor, Robert Garner, and William N. Joy
as inventors.
REFERENCE TO APPENDIX I
[0002] A portion of the disclosure of this patent document
including Appendix I, The JAVA Virtual Machine Specification and
Appendix A thereto, contains material which is subject to copyright
protection. The copyright owner has no objection to the facsimile
reproduction by anyone of the patent document or the patent
disclosure, as it appears in the U.S. Patent and Trademark Office
patent files or records, but otherwise reserves all copyright
rights whatsoever.
BACKGROUND OF THE INVENTION
[0003] 1. Field of the Invention
[0004] The present invention relates generally to computer systems
and, in particular, to a memory architecture using multiple memory
circuits to store information for a method call.
[0005] 2. Discussion of Related Art
[0006] Many individuals and organizations in the computer and
communications industries tout the Internet as the fastest growing
market on the planet. In the 1990s, the number of users of the
Internet appears to be growing exponentially with no end in sight.
In June of 1995, an estimated 6,642,000 hosts were connected to the
Internet; this represented an increase from an estimated
4,852,000-hosts in January, 1995. The number of hosts appears to be
growing at around 75% per year. Among the hosts, there were
approximately 120,000 networks and over 27,000 web servers. The
number of web servers appears to be approximately doubling every 53
days.
[0007] In July 1995, with over 1,000,000 active Internet users,
over 12,505 usenet news groups, and over 10,000,000 usenet readers,
the Internet appears to be destined to explode into a very large
market for a wide variety of information and multimedia
services.
[0008] In addition, to the public carrier network or Internet, many
corporations and other businesses are shifting their internal
information systems onto an intranet as a way of more effectively
sharing information within a corporate or private network. The
basic infrastructure for an intranet is an internal network
connecting servers and desktops, which may or may not be connected
to the Internet through a firewall. These intranets provide
services to desktops via standard open network protocols which are
well established in the industry. Intranets provide many benefits
to the enterprises which employ them., such as simplified internal
information management and improved internal communication using
the browser paradigm. Integrating Internet technologies with a
company's enterprise infrastructure and legacy systems also
leverages existing technology investment for the party employing an
intranet. As discussed above, intranets and the Internet are
closely related, with intranets being used for internal and secure
communications within the business and the Internet being used for
external transactions between the business and the outside world.
For the purposes of this document, the term "networks" includes
both the Internet and intranets. However, the distinction between
the Internet and an intranet should be born in mind where
applicable.
[0009] In 1990, programmers at Sun Microsystems wrote a universal
programming language. This language was eventually named the JAVA
programming language. (JAVA is a trademark of Sun Microsystems of
Mountain View, Calif.) The JAVA programming language resulted from
programming efforts which initially were intended to be coded in
the C++ programming language; therefore, the JAVA programming
language has many commonalities with the C++ programming language.
However, the JAVA programming language is a simple,
object-oriented, distributed, interpreted yet high performance,
robust yet safe, secure, dynamic, architecture neutral, portable,
and multi-threaded language.
[0010] The JAVA programming language has emerged as the programming
language of choice for the Internet as many large hardware and
software companies have licensed it from Sun Microsystems. The JAVA
programming language and environment is designed to solve a number
of problems in modern programming practice. The JAVA programming
language omits many rarely used, poorly understood, and confusing
features of the C++ programming language. These omitted features
primarily consist of operator overloading, multiple inheritance,
and extensive automatic coercions. The JAVA programming language
includes automatic garbage collection that simplifies the task of
programming because it is no longer necessary to allocated and free
memory as in the C programming language. The JAVA programming
language restricts the use of pointers as defined in the C
programming language, and instead has true arrays in which array
bounds are explicitly checked, thereby eliminating vulnerability to
many viruses and nasty bugs. The JAVA programming language includes
objective-C interfaces and specific exception handlers.
[0011] The JAVA programming language has an extensive library of
routines for coping easily with TCP/IP protocol (Transmission
Control Protocol based on Internet protocol), HTTP (Hypertext
Transfer Protocol) and FTP (File Transfer Protocol). The JAVA
programming language is intended to be used in
networked/distributed environments. The JAVA programming language
enabled the construction of virus-free, tamper-free systems. The
authentication techniques are based on public-key encryption.
[0012] Many computing systems, including those implementing the
JAVA virtual machine, can execute multiple methods each of which
has a method frame. Typically, method invocation significantly
impacts the performance of the computing system due to the
excessive number of memory accesses method invocation requires.
Therefore, a method and memory architecture targeted to reduce the
latency caused by method invocation is desirable.
SUMMARY OF THE INVENTION
[0013] Accordingly, the present invention provides a memory
architecture to improve the speed of method invocation.
Specifically, method frames are stored in two different memory
circuits. The first memory circuit stores the execution environment
of each method call, and the second memory circuit stores
parameters, variables or operands of the method calls. In one
embodiment the execution environment includes a return program
counter, a return frame, a return constant pool, a current method
vector, and a current monitor address. In some embodiments, the
memory circuits are stacks; therefore, the stack management unit to
cache can be used to cache either or both memory circuits.
[0014] The stack management unit including a stack cache to
accelerate data transfers between the stack-based computing system
and the stack. In one embodiment, the stack management unit
includes a stack cache, a dribble manager unit, and a stack control
unit. Since the vast majority of memory accesses to the stack occur
at or near the top of the stack, the dribble manager unit maintains
the top portion of the stack in the stack cache. Specifically, when
the stack-based computing system is pushing data onto the stack and
the stack cache is almost full, the dribble manager unit transfers
data from the bottom of the stack cache to the stack so that the
top portion of the stack remains in the stack cache. When the
stack-based computing system is popping data off of the stack and
the stack cache is becoming empty, the dribble manager unit
transfer data from the stack to the bottom of the stack cache to
maintain the top portion of the stack in the stack cache.
[0015] The stack cache includes a stack cache memory circuit, one
or more read ports, and one or more write ports. In one embodiment
the stack cache memory circuit is a register file configured in a
circular buffer memory architecture. For the circular buffer
architecture the registers can be addressed using modulo
addressing. Typically, an OPTOP pointer is used to define and point
to the top memory location in the stack cache memory circuit and a
bottom pointer is used to define and point to the bottom memory
location in the stack cache memory circuit. To avoid confusion, if
the stack management unit is used for the execution environment a
FRAME pointer is used to define and point to the top memory
location. As data words are pushed or popped off of the stack, the
OPTOP pointer is incremented or decremented, respectively.
Similarly, as data words are spilled or filled between the stack
cache memory circuit and the stack, the bottom pointer is
incremented or decremented, respectively.
[0016] Some embodiments of the stack management unit include a fill
control unit and a spill control unit. If the fill control unit
detects a fill condition, the fill control unit transfers data from
the stack to the stack cache memory circuit. In one embodiment of
the stack management unit a fill condition occurs if a the optop
pointer is greater than a high water mark. In another embodiment, a
fill condition occurs if the number of free memory locations in the
stack cache memory circuit is greater than a low cache threshold or
the number of used memory locations is less than the low cache
threshold. Typically, the low water mark and the low cache
threshold are stored in programmable registers. The number of free
memory locations can be determined with a modulo subtractor.
[0017] In one embodiment of the stack management unit a spill
condition occurs if the optop pointer is less than a low water
mark. In another embodiment a spill condition occurs if the number
of free location in the stack cache memory circuit is less than a
high cache threshold or the number of used memory location is
greater than the high cache threshold. Typically, the low water
mark and the low cache threshold are stored in programmable
registers. The number of free memory locations can be determined
with a modulo subtractor.
BRIEF DESCRIPTION OF THE DRAWINGS
[0018] FIG. 1 is a block diagram of one embodiment of virtual
machine hardware processor that utilizes the memory architecture of
this invention to store method frames.
[0019] FIG. 2 is an process flow diagram for generation of virtual
machine instructions that are used in one embodiment of this
invention.
[0020] FIG. 3 illustrates an instruction pipeline implemented in
the hardware processor of FIG. 1.
[0021] FIG. 4A is an illustration of the one embodiment of the
logical organization of a stack structure where each method frame
includes a local variable storage area, an environment storage
area, and an operand stack utilized by the hardware processor of
FIG. 1.
[0022] FIG. 4B is an illustration of an alternative embodiment of
the logical organization of a stack structure where each method
frame includes a local variable storage area and an operand stack
on the stack, and an environment storage area for the method frame
is included on a separate execution environment stack.
[0023] FIG. 4C is an illustration of an alternative embodiment of
the stack management unit for the stack and execution environment
stack of FIG. 4B.
[0024] FIG. 4D is an illustration of one embodiment of the local
variables look-aside cache in the stack management unit of FIG.
1.
[0025] FIG. 5 illustrates several possible add-ons to the hardware
processor of FIG. 1.
[0026] FIG. 6 illustrates a block diagram of one embodiment of a
stack cache management unit in accordance with this invention.
[0027] FIG. 7 illustrates the memory architecture of one embodiment
of a stack cache in accordance with this invention.
[0028] FIG. 8 illustrates the contents of a register or memory
location of one embodiment of a stack cache in accordance with this
invention.
[0029] FIG. 9 illustrates a block diagram of one embodiment of a
dribble manager unit in accordance with this invention.
[0030] FIG. 10A illustrates a block diagram of another embodiment
of a dribble manager unit in accordance with this invention.
[0031] FIG. 10B illustrates a block diagram of another embodiment
of a dribble manager unit in accordance with this invention.
[0032] FIG. 11 illustrates a block diagram of a portion of an
embodiment of a dribble manager unit in accordance with this
invention.
[0033] FIG. 12 illustrates an pointer generation circuit for one
embodiment of a stack cache in accordance with this invention.
[0034] These and other features and advantages of the present
invention will be apparent from the Figures as explained in the
Detailed Description of the Invention. Like or similar features are
designated by the same reference numeral(s) throughout the drawings
and the Detailed Description of the Invention.
DETAILED DESCRIPTION OF THE INVENTION
[0035] FIG. 1 illustrates one embodiment of a virtual machine
instruction hardware processor 100, hereinafter hardware processor
100, that includes a memory architecture in accordance with the
present invention to store method frames, and that directly
executes virtual machine instructions that are processor
architecture independent. The performance of hardware processor 100
in executing JAVA virtual machine instructions is much better than
high-end CPUs, such as the Intel PENTIUM microprocessor or the Sun
Microsystems ULTRASPARC processor, (ULTRASPARC is a trademark of
Sun Microsystems of Mountain View, Calif., and PENTIUM is a
trademark of Intel Corp. of Sunnyvale, Calif.) interpreting the
same virtual machine instructions with a software JAVA interpreter.
or with a JAVA just-in-time compiler; is low cost; and exhibits low
power consumption. As a result, hardware processor 100 is well
suited for portable applications. Hardware processor 100 provides
similar advantages for other virtual machine stack-based
architectures as well as for virtual machines utilizing features
such as garbage collection, thread synchronization, etc.
[0036] In view of these characteristics, a system based on hardware
processor 100 presents attractive price for performance
characteristics, if not the best overall performance, as compared
with alternative virtual machine execution environments including
software interpreters and just-in-time compilers. Nonetheless, the
present invention is not limited to virtual machine hardware
processor embodiments, and encompasses any suitable stack-based, or
non-stack-based machine implementations, including implementations
emulating the JAVA virtual machine as a software interpreter,
compiling JAVA virtual machine instructions (either in batch or
just-in-time) to machine instruction native to a particular
hardware processor, or providing hardware implementing the JAVA
virtual machine in microcode, directly in silicon, or in some
combination thereof.
[0037] Regarding price for performance characteristics, hardware
processor 100 has the advantage that the 250 Kilobytes to 500
Kilobytes (Kbytes) of memory storage, e.g., read-only memory or
random access memory, typically required by a software interpreter,
is eliminated.
[0038] A simulation of hardware processor 100 showed that hardware
processor 100 executes virtual machine instructions twenty times
faster than a software interpreter running on a variety of
applications on a PENTIUM processor clocked at the same clock rate
as hardware processor 100, and executing the same virtual machine
instructions. Another simulation of hardware processor 100 showed
that hardware processor 100 executes virtual machine instructions
five times faster than a just-in-time compiler running on a PENTIUM
processor running at the same clock rate as hardware processor 100,
and executing the same virtual machine instructions.
[0039] In environments in which the expense of the memory required
for a software virtual machine instruction interpreter is
prohibitive, hardware processor 100 is advantageous. These
applications include, for example, an Internet chip for network
appliances, a cellular telephone processor, other
telecommunications integrated circuits, or other low-power,
low-cost applications such as embedded processors, and portable
devices.
[0040] The present invention increases the speed of method
invocation by using an execution environment memory 440 in
conjunction with stack 400B. The execution environment of various
method calls are stored in execution environment memory 440 while
the operands, variables and parameters of the method calls are
stored in stack 400B. Both execution environment memory 440 and
stack 400B can include a stack management unit 150 that utilizes a
stack cache 155 to accelerate data transfers for execution unit
140. Although, stack management unit 150 can be an integral part of
hardware processor 100 as shown in FIG. 1, many embodiments of
stack management unit 150 are not integrated with a hardware
processor since stack management in accordance with the present
invention can be adapted for use with any stack-based computing
system. In one embodiment, stack management unit 150 includes a
stack cache 155, a dribble manager unit 151, and a stack control
unit 152. When hardware processor 100 is pushing data onto stack
400 (FIG. 4(a)) and stack cache 155 is almost full, dribble manager
unit 151 transfers data from the bottom of stack cache 155 to stack
400 through data cache unit 160, so that the top portion of stack
400 remains in stack cache 155. When hardware processor 100 is
popping data off of stack 400 and stack cache 155 is almost empty,
dribble manager unit 151 transfers data from stack 400 to the
bottom of stack cache 155 so that the top portion of stack 400 is
maintained in stack cache 155.
[0041] As used herein, a virtual machine is an abstract computing
machine that, like a real computing machine, has an instruction set
and uses various memory areas. A virtual machine specification
defines a set of processor architecture independent virtual machine
instructions that are executed by a virtual machine implementation,
e.g., hardware processor 100. Each virtual machine instruction
defines a specific operation that is to be performed. The virtual
computing machine need not understand the computer language that is
used to generate virtual machine instructions or the underlying
implementation of the virtual machine. Only a particular file
format for virtual machine instructions needs to be understood.
[0042] In an exemplary embodiment, the virtual machine instructions
are JAVA virtual machine instructions. Each JAVA virtual machine
instruction includes one or more bytes that encode instruction
identifying information, operands, and any other required
information. Appendix I, which is incorporated herein by reference
in its entirety, includes an illustrative set of the JAVA virtual
machine instructions. The particular set of virtual machine
instructions utilized is not an essential aspect of this invention.
In view of the virtual machine instructions in Appendix I and this
disclosure, those of skill in the art can modify the invention for
a particular set of virtual machine instructions, or for changes to
the JAVA virtual machine specification.
[0043] A JAVA compiler JAVAC, (FIG. 2) that is executing on a
computer platform, converts an application 201 written in the JAVA
computer language to an architecture neutral object file format
encoding a compiled instruction sequence 203, according to the JAVA
Virtual Machine Specification, that includes a compiled instruction
set. However, for this invention, only a source of virtual machine
instructions and related information is needed. The method or
technique used to generate the source of virtual machine
instructions and related information is not essential to this
invention.
[0044] Compiled instruction sequence 203 is executable on hardware
processor 100 as well as on any computer platform that implements
the JAVA virtual machine using, for example, a software interpreter
or just-in-time compiler. However, as described above, hardware
processor 100 provides significant performance advantages over the
software implementations.
[0045] In this embodiment, hardware processor 100 (FIG. 1)
processes the JAVA virtual machine instructions, which include
bytecodes. Hardware processor 100, as explained more completely
below, executes directly most of the bytecodes. However, execution
of some of the bytecodes is implemented via microcode.
[0046] One strategy for selecting virtual machine instructions that
are executed directly by hardware processor 100 is described herein
by way of an example. Thirty percent of the JAVA virtual machine
instructions are pure hardware translations; instructions
implemented in this manner include constant loading and simple
stack operations. The next 50% of the virtual machine instructions
are implemented mostly, but not entirely, in hardware and require
some firmware assistance; these include stack based operations and
array instructions. The next 10% of the JAVA virtual machine
instructions are implemented in hardware, but require significant
firmware support as well; these include function invocation and
function return. The remaining 10% of the JAVA virtual machine
instructions are not supported in hardware, but rather are
supported by a firmware trap and/or microcode; these include
functions such as exception handlers. Herein, firmware means
microcode stored in ROM that when executed controls the operations
of hardware processor 100.
[0047] In one embodiment, hardware processor 100 includes an I/O
bus and memory interface unit 110, an instruction cache unit 120
including instruction cache 125, an instruction decode unit 130, a
unified execution unit 140, a stack management unit 150 including
stack cache 155, a data cache unit 160 including a data cache 165,
and program counter and trap control logic 170. Each of these units
is described more completely below.
[0048] Also, as illustrated in FIG. 1, each unit includes several
elements. For clarity and to avoid distracting from the invention,
the interconnections between elements within a unit are not shown
in FIG. 1. However, in view of the following description, those of
skill in the art will understand the interconnections and
cooperation between the elements in a unit and between the various
units.
[0049] The pipeline stages implemented using the units illustrated
in FIG. 1 include fetch, decode, execute, and write-back stages. If
desired, extra stages for memory access or exception resolution are
provided in hardware processor 100.
[0050] FIG. 3 is an illustration of a four stage pipeline for
execution of instructions in the exemplary embodiment of processor
100. In fetch stage 301, a virtual machine instruction is fetched
and placed in instruction buffer 124 (FIG. 1). The virtual machine
instruction is fetched from one of (i) a fixed size cache line from
instruction cache 125 or (ii) external memory.
[0051] With regard to fetching, aside from instructions tableswitch
and lookupawitch, (See Appendix I.) each virtual machine
instruction is between one and five bytes long. Thus, to keep
things simple, at least forty bits are required to guarantee that
all of a given instruction is contained in the fetch.
[0052] Another alternative is to always fetch a predetermined
number of bytes, for example, four bytes, starting with the opcode.
This is sufficient for 95% of JAVA virtual machine instructions
(See Appendix I). For an instruction requiring more than three
bytes of operands, another cycle in the front end must be tolerated
if four bytes are fetched. In this case, the instruction execution
can be started with the first operands fetched even if the full set
of operands is not yet available.
[0053] In decode stage 302 (FIG. 3), the virtual machine
instruction at the front of instruction buffer 124 (FIG. 1) is
decoded and instruction folding is performed if possible. Stack
cache 155 is accessed only if needed by the virtual machine
instruction. Register OPTOP, that contains a pointer OPTOP to a top
of a stack 400 (FIG. 4), is also updated in decode stage 302 (FIG.
3).
[0054] Herein, for convenience, the value in a register and the
register are assigned the same reference numeral. Further, in the
following discussion, use of a register to store a pointer is
illustrative only of one embodiment. Depending on the specific
implementation of the invention, the pointer may be implemented
using hardware register, a hardware counter, a software counter, a
software pointer, or other equivalent embodiments known to those of
skill in the art. The particular implementation selected is not
essential to the invention, and typically is made based on a price
to performance trade-off.
[0055] In execute stage 303, the virtual machine instruction is
executed for one or more cycles. Typically, in execute stage 303,
an ALU in integer unit 142 (FIG. 1) is used either to do an
arithmetic computation or to calculate the address of a load or
store from data cache unit (DCU) 160. If necessary, traps are
prioritized and taken at the end of execute stage 303 (FIG. 3). For
control flow instructions, the branch address is calculated in
execute stage 303, as well as the condition upon which the branch
is dependent.
[0056] Cache stage 304 is a non-pipelined stage. Data cache 165
(FIG. 1) is accessed if needed during execution stage 303 (FIG. 3).
The reason that stage 304 is non-pipelined is because hardware
processor 100 is a stack-based machine. Thus, the instruction
following a load is almost always dependent on the value returned
by the load. Consequently, in this embodiment, the pipeline is held
for one cycle for a data cache access. This reduces the pipeline
stages, and the die area taken by the pipeline for the extra
registers and bypasses.
[0057] Write-back stage 305 is the last stage in the pipeline. In
stage 305, the calculated data is written back to stack cache
155.
[0058] Hardware processor 100, in this embodiment, directly
implements a stack 400 (FIG. 4A) that supports the JAVA virtual
machine stack-based architecture (See Appendix I). Sixty-four
entries on stack 400 are contained on stack cache 155 in stack
management unit 150. Some entries in stack 400 may be duplicated on
stack cache 150. Operations on data are performed through stack
cache 155.
[0059] Stack 400 of hardware processor 100 is primarily used as a
repository of information for methods. At any point in time,
hardware processor 100 is executing a single method. Each method
has memory space, i.e., a method frame on stack 400, allocated for
a set of local variables, an operand stack, and an execution
environment structure.
[0060] A new method frame, e.g., method frame two 410, is allocated
by hardware processor 100 upon a method invocation in execution
stage 303 (FIG. 3) and becomes the current frame, i.e., the frame
of the current method. Current frame 410 (FIG. 4A), as well as the
other method frames, may contain a part of or all of the following
six entities, depending on various method invoking situations:
[0061] Object reference;
[0062] Incoming arguments;
[0063] Local variables;
[0064] Invoker's method context;
[0065] Operand stack; and
[0066] Return value from method.
[0067] In FIG. 4A, object reference, incoming arguments, and local
variables are included in arguments and local variables area 421.
The invoker's method context is included in execution environment
422, sometimes called frame state, that in turn includes: a return
program counter value 431 that is the address of the virtual
machine instruction, e.g., JAVA opcode, next to the method invoke
instruction; a return frame 432 that is the location of the calling
method's frame; a return constant pool pointer 433 that is a
pointer to the calling method's constant pool table; a current
method vector 434 that is the base address of the current method's
vector table; and a current monitor address 435 that is the address
of the current method's monitor.
[0068] The object reference is an indirect pointer to an
object-storage representing the object being targeted for the
method invocation. JAVA compiler JAVAC (See FIG. 2.) generates an
instruction to push this pointer onto operand stack 423 prior to
generating an invoke instruction. This object reference is
accessible as local variable zero during the execution of the
method. This indirect pointer is not available for a static method
invocation as there is no target-object defined for a static method
invocation.
[0069] The list of incoming arguments transfers information from
the calling method to the invoked method. Like the object
reference, the incoming arguments are pushed onto stack 400 by JAVA
compiler generated instructions-and may be accessed as local
variables. JAVA compiler JAVAC (See FIG. 2.) statically generates a
list of arguments for current method 410 (FIG. 4A), and hardware
processor 100 determines the number of arguments from the list.
When the object reference is present in the frame for a non-static
method invocation, the first argument is accessible as local
variable one. For a static method invocation, the first argument
becomes local variable zero.
[0070] For 64-bit arguments, as well as 64-bit entities in general,
the upper 32-bits, i.e., the 32 most significant bits, of a 64-bit
entity are placed on the upper location of stack 400, i.e., pushed
on the stack last. For example, when a 64-bit entity is on the top
of stack 400, the upper 32-bit portion of the 64-bit entity is on
the top of the stack, and the lower 32-bit portion of the 64-bit
entity is in the storage location immediately adjacent to the top
of stack 400.
[0071] The local variable area on stack 400 (FIG. 4A) for current
method 410 represents temporary variable storage space which is
allocated and remains effective during invocation of method 410.
JAVA compiler JAVAC (FIG. 2) statically determines the required
number of local variables and hardware processor 100 allocates
temporary variable storage space accordingly.
[0072] When a method is executing on hardware processor 100, the
local variables typically reside in stack cache 155 and are
addressed as offsets from pointer VARS (FIGS. 1 and 4A), which
points to the position of the local variable zero. Instructions are
provided to load the values of local variables onto operand stack
423 and store values from operand stack into local variables area
421.
[0073] The information in execution environment 422 includes the
invoker's method context. When a new frame is built for the current
method, hardware processor 100 pushes the invoker's method context
onto newly allocated frame 410, and later utilizes the information
to restore the invoker's method context before returning. Pointer
FRAME. (FIGS. 1 and 4A) is a pointer to the execution environment
of the current method. In the exemplary embodiment, each register
in register set 144 (FIG. 1) is 32-bits wide.
[0074] Operand stack 423 is allocated to support the execution of
the virtual machine instructions within the current method. Program
counter register PC (FIG. 1) contains the address of the next
instruction, e.g., opcode, to be executed. Locations on operand
stack 423 (FIG. 4A) are used to store the operands of virtual
machine instructions, providing both source and target storage
locations for instruction execution. The size of operand stack 423
is statically determined by JAVA compiler JAVAC (FIG. 2) and
hardware processor 100 allocates space for operand stack 423
accordingly. Register OPTOP (FIGS. 1 and 4A) holds a pointer to a
top of operand stack 423.
[0075] The invoked method may return its execution result onto the
invoker's top of stack, so that the invoker can access the return
value with operand stack references. The return value is placed on
the area where an object reference or an argument is pushed before
a method invocation.
[0076] Simulation results on the JAVA virtual machine indicate that
method invocation consumes a significant portion of the execution
time (20-40%). Given this attractive target for accelerating
execution of virtual machine instructions, hardware support for
method invocation is included in hardware processor 100, as
described more completely below.
[0077] The beginning of the stack frame of a newly invoked method,
i.e., the object reference and the arguments passed by the caller,
are already stored on stack 400 since the object reference and the
incoming arguments come from the top of the stack of the caller. As
explained above, following these items on stack 400, the local
variables are loaded and then the execution environment is
loaded.
[0078] One way to speed up this process is for hardware processor
100 to load the execution environment in the background and
indicate what has been loaded so far, e.g., simple one bit
scoreboarding. Hardware processor 100 tries to execute the
bytecodes of the called method as soon as possible, even though
stack 400 is not completely loaded. If accesses are made to
variables already loaded, overlapping of execution with loading of
stack 400 is achieved, otherwise a hardware interlock occurs and
hardware processor 100 just waits for the variable or variables in
the execution environment to be loaded.
[0079] FIG. 4B illustrates another way to accelerate method
invocation. Instead of storing the entire method frame in stack
400, the execution environment of each method frame is stored
separately from the local variable area and the operand stack of
the method frame. Thus, in this embodiment, stack 400B contains
modified method frames, e.g. modified method frame 410B having only
local variable area 421 and operand stack 423. Execution
environment 422 of the method frame is stored in execution
environment memory 440. Storing the execution environment in
execution environment memory 440 reduces the amount of data in
stack cache 155. Therefore, the size of stack cache 155 can be
reduced. Furthermore, execution environment memory 440 and stack
cache 155 can be accessed simultaneously. Thus, method invocation
can be accelerated by loading or storing the execution environment
in parallel with loading or storing data onto stack 400B.
[0080] In one embodiment of stack management unit 150, the memory
architecture of execution environment memory 440 is also a stack.
As modified method frames are pushed onto stack 400b through stack
cache 155, corresponding execution environments are pushed onto
execution environment memory 440. For example, since modified
method frames 0 to 2, as shown in FIG. 4B, are in stack 400B,
execution environments (EE) 0 to 2, respectively, are stored in
execution environment memory circuit 440.
[0081] To further enhance method invocation, an execution
environment cache can be added to improve the speed of saving and
retrieving the execution environment during method invocation. The
architecture described more completely below for stack cache 155,
dribbler manager unit 151, and stack control unit 152 for caching
stack 400, can also be applied to caching execution environment
memory 440.
[0082] FIG. 4C illustrates an embodiment of stack management unit
150 modified to support both stack 400b and execution environment
memory 440. Specifically, the embodiment of stack management unit
150 in FIG. 4C adds an execution environment stack cache 450, an
execution environment dribble manager unit 460, and an execution
environment stack control unit 470. Typically, execution dribble
manager unit 460 transfers an entire execution environment between
execution environment cache 450 and execution environment memory
440 during a spill operation or a fill operation.
[0083] I/O Bus and Memory Interface Unit
[0084] I/O bus and memory interface unit 110 (FIG. 1), sometimes
called interface unit 110, implements an interface between hardware
processor 100 and a memory hierarchy which in an exemplary
embodiment includes external memory and may optionally include
memory storage and/or interfaces on the same die as hardware
processor 100. In this embodiment, I/O controller 111 interfaces
with external I/O devices and memory controller 112 interfaces with
external memory. Herein, external memory means memory external to
hardware processor 100. However, external memory either may be
included on the same die as hardware processor 100, may be external
to the die containing hardware processor 100, or may include both
on- and off-die portions.
[0085] In another embodiment, requests to I/O devices go through
memory controller 112 which maintains an address map of the entire
system including hardware processor 100. On the memory bus of this
embodiment, hardware processor 100 is the only master and does not
have to arbitrate to use the memory bus.
[0086] Hence, alternatives for the input/output bus that interfaces
with I/O bus and memory interface unit 110 include supporting
memory-mapped schemes, providing direct support for PCI, PCMCIA, or
other standard busses. Fast graphics (w/VIS or other technology)
may optionally be included on the die with hardware processor
100.
[0087] I/O bus and memory interface unit 110 generates read and
write requests to external memory. Specifically, interface unit 110
provides an interface for instruction cache and data cache
controllers 121 and 161 to the external memory. Interface unit 110
includes arbitration logic for internal requests from instruction
cache controller 121 and data cache controller 161 to access
external memory and in response to a request initiates either a
read or a write request on the memory bus to the external memory. A
request from data cache controller 121 is always treated as higher
priority relative to a request from instruction cache controller
161.
[0088] Interface unit 110 provides an acknowledgment signal to the
requesting instruction cache controller 121, or data cache
controller 161 on read cycles so that the requesting controller can
latch the data. On write cycles, the acknowledgment signal from
interface unit 110 is used for flow control so that the requesting
instruction cache controller 121 or data cache controller 161 does
not generate a new request when there is one pending. Interface
unit 110 also handles errors generated on the memory bus to the
external memory.
[0089] Instruction Cache Unit
[0090] Instruction cache unit (ICU) 120 (FIG. 1) fetches virtual
machine instructions from instruction cache 125 and provides the
instructions to instruction decode unit 130. In this embodiment,
upon a instruction cache hit, instruction cache-controller 121, in
one cycle, transfers an instruction from instruction cache 125 to
instruction buffer 124 where the instruction is held until integer
execution unit IEU, that is described more completely below, is
ready to process the instruction. This separates the rest of
pipeline 300 (FIG. 3) in hardware processor 100 from fetch stage
301. If it is undesirable to incur the complexity of supporting an
instruction-buffer type of arrangement, a temporary one instruction
register is sufficient for most purposes. However, instruction
fetching, caching, and buffering should provide sufficient
instruction bandwidth to support instruction folding as described
below.
[0091] The front end of hardware processor 100 is largely separate
from the rest of hardware processor 100. Ideally, one instruction
per cycle is delivered to the execution pipeline.
[0092] The instructions are aligned on an arbitrary eight-bit
boundary by byte aligner circuit 122 in response to a signal from
instruction decode unit 130. Thus, the front end of hardware
processor 100 efficiently deals with fetching from any byte
position. Also, hardware processor 100 deals with the problems of
instructions that span multiple cache lines of cache 125. In this
case, since the opcode is the first byte, the design is able to
tolerate an extra cycle of fetch latency for the operands. Thus, a
very simple de-coupling between the fetching and execution of the
bytecodes is possible.
[0093] In case of an instruction cache miss, instruction cache
controller 121 generates an external memory request for the missed
instruction to I/O bus and memory interface unit 110. If
instruction buffer 124 is empty, or nearly empty, when there is an
instruction cache miss, instruction decode unit 13.0 is stalled,
i.e., pipeline 300 is stalled. Specifically, instruction cache
controller 121 generates a stall signal upon a cache miss which is
used along with an instruction buffer empty signal to determine
whether to stall pipeline 300. Instruction cache 125 can be
invalidated to accommodate self-modifying code, e.g., instruction
cache controller 121 can invalidate a particular line in
instruction cache 125.
[0094] Thus, instruction cache controller 121 determines the next
instruction to be fetched, i.e., which instruction in instruction
cache 125 needs to accessed, and generates address, data and
control signals for data and tag RAMs in instruction cache 125. On
a cache hit, four bytes of data are fetched from instruction cache
125 in a single cycle, and a maximum of four bytes can be written
into instruction buffer 124.
[0095] Byte aligner circuit 122 aligns the data out of the
instruction cache RAM and feeds the aligned data to instruction
buffer 124. As explained more completely below, the first two bytes
in instruction buffer 124 are decoded to determine the length of
the virtual machine instruction. Instruction buffer 124 tracks the
valid instructions in the queue and updates the entries, as
explained more completely below.
[0096] Instruction cache controller 121 also provides the data path
and control for handling instruction cache misses. On an
instruction cache miss, instruction cache controller 121 generates
a cache fill request to I/O bus and memory interface unit 110.
[0097] On receiving data from external memory, instruction cache
controller 121 writes the data into instruction cache 125 and the
data are also bypassed into instruction buffer 124. Data are
bypassed to instruction buffer 124 as soon as the data are
available from external memory, and before the completion of the
cache fill.
[0098] Instruction cache controller 121 continues fetching
sequential data until instruction buffer 124 is full or a branch or
trap has taken place. In one embodiment, instruction buffer 124 is
considered full if there are more than eight bytes of valid entries
in buffer 124. Thus, typically, eight bytes of data are written
into instruction cache 125 from external memory in response to the
cache fill request sent to interface unit 110 by instruction cache
unit 120. If there is a branch or trap taken while processing an
instruction cache miss, only after the completion of the miss
processing is the trap or branch executed.
[0099] When an error is generated during an instruction cache fill
transaction, a fault indication is generated and stored into
instruction buffer 124 along with the virtual machine instruction,
i.e., a fault bit is set. The line is not written into instruction
cache 125. Thus, the erroneous cache fill transaction acts like a
non-cacheable transaction except that a fault bit is set. When the
instruction is decoded, a trap is taken.
[0100] Instruction cache controller 121 also services non-cacheable
instruction reads. An instruction cache enable (ICE) bit, in a
processor status register in register set 144, is used to define
whether a load can be cached. If the instruction cache enable bit
is cleared, instruction cache unit 120 treats all loads as
non-cacheable loads. Instruction cache controller 121 issues a
non-cacheable request to interface unit 110 for non-cacheable
instructions. When the data are available on a cache fill bus for
the non-cacheable instruction, the data are bypassed into
instruction buffer 124 and are not written into instruction cache
125.
[0101] In this embodiment, instruction cache 125 is a
direct-mapped, eight-byte line size cache. Instruction cache 125
has a single cycle latency. The cache size is configurable to 0K,
1K, 2K, 4K, 8K and 16K byte sizes where K means kilo. The default
size is 4K bytes. Each line has a cache tag entry associated with
the line. Each cache tag contains a twenty bit address tag field
and one valid bit for the default 4 K byte size.
[0102] Instruction buffer 124, which, in an exemplary embodiment,
is a twelve-byte deep first-in, first-out (FIFO) buffer, de-links
fetch stage 301 (FIG. 3) from the rest of pipeline 300 for
performance reasons. Each instruction in buffer 124 (FIG. 1) has an
associated valid bit and an error bit. When the valid bit is set,
the instruction associated with that valid bit is a valid
instruction. When the error bit is set, the fetch of the
instruction associated with that error bit was an erroneous
transaction. Instruction buffer 124 includes an instruction buffer
control circuit (not shown) that generates signals to pass data to
and from instruction buffer 124 and that keeps track of the valid
entries in instruction buffer 124, i.e., those with valid bits
set.
[0103] In an exemplary embodiment, four bytes can be received into
instruction buffer 124 in a given cycle. Up to five bytes,
representing up to two virtual machine instructions, can be read
out of instruction buffer 124 in a given cycle. Alternative
embodiments, particularly those providing folding of multi-byte
virtual machine instructions and/or those providing folding of more
than two virtual machine instructions, provide higher input and
output bandwidth. Persons of ordinary skill in the art will
recognize a variety of suitable instruction buffer designs
including, for example, alignment logic, circular buffer design,
etc. When a branch or trap is taken, all the entries in instruction
buffer 124 are nullified and the branch/trap data moves to the top
of instruction buffer 124.
[0104] In the embodiment of FIG. 1, a unified execution unit 140 is
shown. However, in another embodiment, instruction decode unit 120,
integer unit 142, and stack management unit 150 are considered a
single integer execution unit, and floating point execution unit
143 is a separate optional unit. In still other embodiments, the
various elements in the execution unit may be implemented using the
execution unit of another processor. In general the various
elements included in the various units of FIG. 1 are exemplary only
of one embodiment. Each unit could be implemented with all or some
of the elements shown. Again, the decision is largely dependent
upon a price vs. performance trade-off.
[0105] Instruction Decode Unit
[0106] As explained above, virtual machine instructions are decoded
in decode stage 302 (FIG. 3) of pipeline 300. In an exemplary
embodiment, two bytes, that can correspond to two virtual machine
instructions, are fetched from instruction buffer 124 (FIG. 1). The
two bytes are decoded in parallel to determine if the two bytes
correspond to two virtual machine instructions, e.g., a first load
top of stack instruction and a second add top two stack entries
instruction, that can be folded into a single equivalent operation.
Folding refers to supplying a single equivalent operation
corresponding to two or more virtual machine instructions.
[0107] In an exemplary hardware processor 100 embodiment, a
single-byte first instruction can be folded with a second
instruction. However, alternative embodiments provide folding of
more than two virtual machine instructions, e.g., two to four
virtual machine instructions, and of multi-byte virtual machine
instructions, though at the cost of instruction decoder complexity
and increased instruction bandwidth. See U.S. patent application
Ser. No. 08/______, entitled "INSTRUCTION FOLDING FOR A STACK-BASED
MACHINE" naming Marc Tremblay and James Michael O'Connor as
inventors, assigned to the assignee of this application, and filed
on even date herewith with Attorney Docket No. SP2036, which is
incorporated herein by reference in its entirety. In the exemplary
processor 100 embodiment, if the first byte, which corresponds to
the first virtual machine instruction, is a multi-byte instruction,
the first and second instructions are not folded.
[0108] An optional current object loader folder 132 exploits
instruction folding, such as that described above, and in greater
detail in U.S. patent application Ser. No. 08/______, entitled
"INSTRUCTION FOLDING FOR A STACK-BASED MACHINE" naming Marc
Tremblay and James Michael O'Connor as inventors, assigned to the
assignee of this application, and filed on even date herewith with
Attorney Docket No. SP2036, which is incorporated herein by
reference in its entirety, in virtual machine instruction sequences
which simulation results have shown to be particularly frequent and
therefore a desirable target for optimization. In particular,
method invocations typically load an object reference for the
corresponding object onto the operand stack and fetch a field from
the object. Instruction folding allow this extremely common virtual
machine instruction sequence to be executed using an equivalent
folded operation.
[0109] Quick variants are not part of the virtual machine
instruction set (See Chapter 3 of Appendix I), and are invisible
outside of a JAVA virtual machine implementation. However, inside a
virtual machine implementation, quick variants have proven to be an
effective optimization. (See Appendix A in Appendix I; which is an
integral part of this specification.) Supporting writes for updates
of various instructions to quick variants in a non-quick to quick
translator cache 131 changes the normal virtual machine instruction
to a quick virtual machine instruction to take advantage of the
large benefits bought from the quick variants. In particular, as
described in more detail in U.S. patent application Ser. No.
08/______, entitled "NON-QUICK INSTRUCTION ACCELERATOR AND METHOD
OF IMPLEMENTING SAME" naming Marc Tremblay and James Michael
O'Connor as inventors, assigned to the assignee of this
application, and filed on even date herewith with Attorney Docket
No. SP2039, which is incorporated herein by reference in its
entirety, when the information required to initiate execution of an
instruction has been assembled for the first time, the information
is stored in a cache along with the value of program counter PC as
tag in non-quick to quick translator cache 131 and the instruction
is identified as a quick-variant. In one embodiment, this is done
with self-modifying code.
[0110] Upon a subsequent call of that instruction, instruction
decode unit 130 detects that the instruction is identified as a
quick-variant and simply retrieves the information needed to
initiate execution of the instruction from non-quick to quick
translator cache 131. Non-quick to quick translator cache is an
optional feature of hardware processor 100.
[0111] With regard to branching, a very short pipe with quick
branch resolution is sufficient for most implementations. However,
an appropriate simple branch prediction mechanism can alternatively
be introduced, e.g., branch predictor circuit 133. Implementations
for branch predictor circuit 133 include branching based on opcode,
branching based on offset, or branching based on a two-bit counter
mechanism.
[0112] The JAVA virtual machine specification defines an
instruction invokenonvirtual, opcode 183, which, upon execution,
invokes methods. The opcode is followed by an index byte one and an
index byte two. (See Appendix I.) Operand stack 423 contains a
reference to an object and some number of arguments when this
instruction is executed.
[0113] Index bytes one and two are used to generate an index into
the constant pool of the current class. The item in the constant
pool at that index points to a complete method signature and class.
Signatures are defined in Appendix I and that description is
incorporated herein by reference.
[0114] The method signature, a short, unique identifier for each
method, is looked up in a method table of the class indicated. The
result of the lookup is a method block that indicates the type of
method and the number of arguments for the method. The object
reference and arguments are popped off this method's stack and
become initial values of the local variables of the new method. The
execution then resumes with the first instruction of the new
method. Upon execution, instructions invokevirtual, opcode 182, and
invokestatic, opcode 184, invoke processes similar to that just
described. In each case, a pointer is used to lookup a method
block.
[0115] A method argument cache 134, that also is an optional
feature of hardware processor 100, is used, in a first embodiment,
to store the method block of a method for use after the first call
to the method, along with the pointer to the method block as a tag.
Instruction decode unit 130 uses index bytes one and two to
generate the pointer and then uses the pointer to retrieve the
method block for that pointer in cache 134. This permits building
the stack frame for the newly invoked method more rapidly in the
background in subsequent invocations of the method. Alternative
embodiments may use a program counter or method identifier as a
reference into cache 134. If there is a cache miss, the instruction
is executed in the normal fashion and cache 134 is updated
accordingly. The particular process used to determine which cache
entry is overwritten is not an essential aspect of this invention.
A least-recently used criterion could be implemented, for
example.
[0116] In an alternative embodiment, method argument cache 134 is
used to store the pointer to the method block, for use after the
first call to the method, along with the value of program counter
PC of the method as a tag. Instruction decode unit 130 uses the
value of program counter PC to access cache 134. If the value of
program counter PC is equal to one of the tags in cache 134, cache
134 supplies the pointer stored with that tag to instruction decode
unit 130. Instruction decode unit 139 uses the supplied pointer to
retrieve the method block for the method. In view of these two
embodiments, other alternative embodiments will be apparent to
those of skill in the art.
[0117] Wide index forwarder 136, which is an optional element of
hardware processor 100, is a specific embodiment of instruction
folding for instruction wide. Wide index forwarder 136 handles an
opcode encoding an extension of an index operand for an immediately
subsequent virtual machine instruction. In this way, wide index
forwarder 136 allows instruction decode unit 130 to provide indices
into local variable storage 421 when the number of local variables
exceeds that addressable with a single byte index without incurring
a separate execution cycle for instruction wide.
[0118] Aspects of instruction decoder 135, particularly instruction
folding, non-quick to quick translator cache 131, current object
loader folder 132, branch predictor 133, method argument cache 134,
and wide index forwarder 136 are also useful in implementations
that utilize a software interpreter or just-in-time compiler, since
these elements can be used to accelerate the operation of the
software interpreter or just-in-time compiler. In such an
implementation, typically, the virtual machine instructions are
translated to an instruction for the processor executing the
interpreter or compiler, e.g., any one of a Sun processor, a DEC
processor, an Intel processor, or a Motorola processor, for
example, and the operation of the elements is modified to support
execution on that processor. The translation from the virtual
machine instruction to the other processor instruction can be done
either with a translator in a ROM or a simple software translator.
For additional examples of dual instruction set processors, see
U.S. patent application Ser. No. 08/______, entitled "A PROCESSOR
FOR EXECUTING INSTRUCTION SETS RECEIVED FROM A NETWORK OR FROM A
LOCAL MEMORY" naming Marc Tremblay and James Michael O'Connor as
inventors, assigned to the assignee of this application, and filed
on even date herewith with Attorney Docket No. SP2042, which is
incorporated herein by reference in its entirety
[0119] Integer Execution Unit
[0120] Integer execution unit IEU, that includes instruction decode
unit 130, integer unit 142, and stack management unit 150, is
responsible for the execution of all the virtual machine
instructions except the floating point related instructions. The
floating point related instructions are executed in floating point
unit 143.
[0121] Integer execution unit IEU interacts at the front end with
instructions cache unit 120 to fetch instructions, with floating
point unit (FPU) 143 to execute floating point instructions, and
finally with data cache unit (DCU) 160 to execute load and store
related instructions. Integer execution unit IEU also contains
microcode ROM 149 which contains instructions to execute certain
virtual machine instructions associated with integer
operations.
[0122] Integer execution unit IEU includes a cached portion of
stack 400, i.e., stack cache 155. Stack cache 155 provides fast
storage for operand stack and local variable entries associated
with a current method, e.g., operand stack 423 and local variable
storage 421 entries. Although, stack cache 155 may provide
sufficient storage for all operand stack and local variable entries
associated with a current method, depending on the number of
operand stack and local variable entries, less than all of local
variable entries or less than all of both local variable entries
and operand stack entries may be represented in stack cache 155.
Similarly, additional entries, e.g., operand stack and or local
variable entries for a calling method, may be represented in stack
cache 155 if space allows.
[0123] Stack cache 155 is a sixty-four entry thirty-two-bit wide
array of registers that is physically implemented as a register
file in one embodiment. Stack cache 155 has three read ports, two
of which are dedicated to integer execution unit IEU and one to
dribble manager unit 151. Stack cache 155 also has two write ports,
one dedicated to integer execution unit IEU and one to dribble
manager unit 151.
[0124] Integer unit 142 maintains the various pointers which are
used to access variables, such as local variables, and operand
stack values, in stack cache 155. Integer unit 142 also maintains
pointers to detect whether a stack cache hit has taken place.
Runtime exceptions are caught and dealt with by exception handlers
that are implemented using information in microcode ROM 149 and
circuit 170.
[0125] Integer unit 142 contains a 32-bit ALU to support arithmetic
operations. The operations supported by the ALU include: add,
subtract, shift, and, or, exclusive or, compare, greater than, less
than, and bypass. The ALU is also used to determine the address of
conditional branches while a separate comparator determines the
outcome of the branch instruction.
[0126] The most common set of instructions which executes cleanly
through the pipeline is the group of ALU instructions. The ALU
instructions read the operands from the top of stack 400 in decode
stage 302 and use the ALU in execution stage 303 to compute the
result. The result is written back to stack 400 in write-back stage
305. There are two levels of bypass which may be needed if
consecutive ALU operations are accessing stack cache 155.
[0127] Since the stack cache ports are 32-bits wide in this
embodiment, double precision and long data operations take two
cycles. A shifter is also present as part of the ALU. If the
operands are not available for the instruction in decode stage 302,
or at a maximum at the beginning of execution stage 303, an
interlock holds the pipeline stages before execution stage 303.
[0128] The instruction cache unit interface of integer execution
unit IEU is a valid/accept interface, where instruction cache unit
120 delivers instructions to integer decode unit 130 in fixed
fields along with valid bits. Instruction decoder 135 responds by
signaling how much byte aligner circuit 122 needs to shift, or how
many bytes instruction decode unit 130 could consume in decode
stage 302. The instruction cache unit interface also signals to
instruction cache unit 120 the branch mis-predict condition, and
the branch address in execution stage 303. Traps, when taken, are
also similarly indicated to instruction cache unit 120. Instruction
cache unit 120 can hold integer unit 142 by not asserting any of
the valid bits to instruction decode unit 130. Instruction decode
unit 130 can hold instruction cache unit 120 by not asserting the
shift signal to byte aligner circuit 122.
[0129] The data cache interface of integer execution unit IEU also
is a valid-accept interface, where integer unit 142 signals, in
execution stage 303, a load or store operation along with its
attributes, e.g., non-cached, special stores etc., to data cache
controller 161 in data cache unit 160. Data cache unit 160 can
return the data on a load, and control integer unit 142 using a
data control unit hold signal. On a data cache hit, data cache unit
160 returns the requested data, and then releases the pipeline.
[0130] On store operations, integer unit 142 also supplies the data
along with the address in execution stage 303. Data cache unit 165
can hold the pipeline in cache stage 304 if data cache unit 165 is
busy, e.g., doing a line fill etc.
[0131] Floating point operations are dealt with specially by
integer execution unit IEU. Instruction decoder 135 fetches and
decodes floating point unit 143 related instructions. Instruction
decoder 135 sends the floating point operation operands for
execution to floating point unit 142 in decode state 302. While
floating point unit 143 is busy executing the floating point
operation, integer unit 142 halts the pipeline and waits until
floating point unit 143 signals to integer unit 142 that the result
is available.
[0132] A floating point ready signal from floating point unit 143
indicates that execution stage 303 of the floating point operation
has concluded. In response to the floating point ready signal, the
result is written back into stack cache 155 by integer unit 142.
Floating point load and stores are entirely handled by integer
execution unit IEU, since the operands for both floating point unit
143 and integer unit 142 are found in stack cache 155.
[0133] Stack Management Unit
[0134] A stack management unit 150 stores information, and provides
operands to execution unit 140. Stack management unit 150 also
takes care of overflow and underflow conditions of stack cache
155.
[0135] In one embodiment, stack management unit 150 includes stack
cache 155 that, as described above, is a three read port, two write
port register file in one embodiment; a stack control unit 152
which provides the necessary control signals for two read ports and
one write port that are used to retrieve operands for execution
unit 140 and for storing data back from a write-back register or
data cache 165 into stack cache 155; and a dribble manager 151
which speculatively dribbles data in and out of stack cache 155
into memory whenever there is an overflow or underflow in stack
cache 155. In the exemplary embodiment of FIG. 1, memory includes
data cache 165 and any memory storage interfaced by memory
interface unit 110. In general, memory includes any suitable memory
hierarchy including caches, addressable read/write memory storage,
secondary storage, etc. Dribble manager 151 also provides the
necessary control signals for a single read port and a single write
port of stack cache 155 which are used exclusively for background
dribbling purposes.
[0136] In one embodiment, stack cache 155 is managed as a circular
buffer which ensures that the stack grows and shrinks in a
predictable manner to avoid overflows or overwrites. The saving and
restoring of values to and from data cache 165 is controlled by
dribbler manager 151 using high- and low-water marks, in one
embodiment.
[0137] Stack management unit 150 provides execution unit 140 with
two 32-bit operands in a given cycle. Stack management unit 150 can
store a single 32-bit result in a given cycle.
[0138] Dribble manager 151 handles spills and fills of stack cache
155 by speculatively dribbling the data in and out of stack cache
155 from and to data cache 165. Dribble manager 151 generates a
pipeline stall signal to stall the pipeline when a stack overflow
or underflow condition is detected. Dribble manager 151 also keeps
track of requests sent to data cache unit 160. A single request to
data cache unit 160 is a 32-bit consecutive load or store
request.
[0139] The hardware organization of stack cache 155 is such that,
except for long operands (long integers and double precision
floating-point numbers), implicit operand fetches for opcodes do
not add latency to the execution of the opcodes. The number of
entries in operand stack 423 (FIG. 4A) and local variable storage
422 that are maintained in stack cache 155 represents a
hardware/performance tradeoff. At least a few operand stack 423 and
local variable storage 422 entries are required to get good
performance. In the exemplary embodiment of FIG. 1, at least the
top three entries of operand stack 423 and the first four local
variable storage 422 entries are preferably represented in stack
cache 155.
[0140] One key function provided by stack cache 155 (FIG. 1) is to
emulate a register file where access to the top two registers is
always possible without extra cycles. A small hardware stack is
sufficient if the proper intelligence is provided to load/store
values from/to memory in the background, therefore preparing stack
cache 155 for incoming virtual machine instructions.
[0141] As indicated above, all items on stack 400 (regardless of
size) are placed into a 32-bit word. This tends to waste space if
many small data items are used, but it also keeps things relatively
simple and free of lots of tagging or muxing. An entry in stack 400
thus represents a value and not a number of bytes. Long integer and
double precision floating-point numbers require two entries. To
keep the number of read and write ports low, two cycles to read two
long integers or two double precision floating point numbers are
required.
[0142] The mechanism for filling and spilling the operand stack
from stack cache 155 out to memory by dribble manager 151 can
assume one of several alternative forms. One register at a time can
be filled or spilled, or a block of several registers filled or
spilled at once. A simple scoreboarded method is appropriate for
stack management. In its simplest form, a single bit indicates if
the register in stack cache 155 is currently valid. In addition,
some embodiments of stack cache 155 use a single bit to indicate
whether the data content of the register is saved to stack 400,
i.e., whether the register is dirty. In one embodiment, a
high-water mark/low-water mark heuristic determines when entries
are saved to and restored from stack 400, respectively (FIG. 4A).
Alternatively, when the top-of-the-stack becomes close to bottom
401 of stack cache 155 by a fixed, or alternatively, a programmable
number of entries, the hardware starts loading registers from stack
400 into stack cache 155. Detailed embodiments of stack management
unit 150 and dribble manager unit 151 are described below and in
U.S. patent application Ser. No. 08/______, entitled "METHODS AND
APPARATI FOR STACK CACHING" naming Mark Tremblay and James Michael
O'Connor as inventors, assigned to the assignee of this
application, and filed on even date herewith with Attorney Docket
No. SP2037, which is incorporated herein by reference in its
entirety.
[0143] In one embodiment, stack management unit 150 also includes
an optional local variable look-aside cache 153. Cache 153 is most
important in applications where both the local variables and
operand stack 423 (FIG. 4A) for a method are not located on stack
cache 155. In such instances when cache 153 is not included in
hardware processor 100, there is a miss on stack cache 155 when a
local variable is accessed, and execution unit 140 accesses data
cache unit 160, which in turn slows down execution. In contrast,
with cache 153, the local variable is retrieved from cache 153 and
there is no delay in execution.
[0144] One embodiment of local variable look-aside cache 153 is
illustrated in FIG. 4D for method 0 to 2 on stack 400. Local
variables zero to M, where M is an integer, for method 0 are stored
in plane 421A_0 of cache 153 and plane 421A_0 is accessed when
method number 402 is zero. Local variables zero to N, where N is an
integer, for method 1 are stored in plane 421A_1 of cache 153 and
plane 421A_1 is accessed when method number 402 is one. Local
variables zero to P, where P is an integer, for method 1 are stored
in plane 421A_2 of cache 153 and plane 421A_2 is accessed when
method number 402 is two. Notice that the various planes of cache
153 may be different sizes, but typically each plane of the cache
has a fixed size that is empirically determined.
[0145] When a new method is invoked, e.g, method 2, . . . a new
plane 421A_2 in cache 153 is loaded with the local variables for
that method, and method number register 402, which in one
embodiment is a counter, is changed, e.g., incremented, to point to
the plane of cache 153 containing the local variables for the new
method. Notice that the local variables are ordered within a plane
of cache 153 so that cache 153 is effectively a direct-mapped
cache. Thus, when a local variable is needed for the current
method, the variable is accessed directly from the most recent
plane in cache 153, i.e., the plane identified by method number
402. When the current method returns, e.g., method 2, method number
register 402 is changed, e.g., decremented, to point at previous
plane 421A-1 of cache 153. Cache 153 can be made as wide and as
deep as necessary.
[0146] Data Cache Unit
[0147] Data cache unit 160 (DCU) manages all requests for data in
data cache 165. Data cache requests can come from dribbling manager
151 or execution unit 140. Data cache controller 161 arbitrates
between these requests giving priority to the execution unit
requests. In response to a request, data cache controller 161
generates address, data and control signals for the data and tags
RAMs in data cache 165. For a data cache hit, data cache controller
161 reorders the data RAM output to provide the right data.
[0148] Data cache controller 161 also generates requests to I/O bus
and memory interface unit 110 in case of data cache misses, and in
case of non-cacheable loads and stores. Data cache controller 161
provides the data path and control logic for processing
non-cacheable requests, and the data path and data path control
functions for handling cache misses.
[0149] For data cache hits, data cache unit 160 returns data to
execution unit 140 in one cycle for loads. Data cache unit 160 also
takes one cycle for write hits. In case of a cache miss, data cache
unit 160 stalls the pipeline until the requested data is available
from the external memory. For both non-cacheable loads and stores,
data cache 161 is bypassed and requests are sent to I/O bus and
memory interface unit 110. Non-aligned loads and stores to data
cache 165 trap in software.
[0150] Data cache 165 is a two-way set associative, write back,
write allocate, 16-byte line cache. The cache size is configurable
to 0, 1, 2, 4, 8, 16 Kbyte sizes. The default size is 8 Kbytes.
Each line has a cache tag store entry associated with the line. On
a cache miss, 16 bytes of data are written into cache 165 from
external memory.
[0151] Each data cache tag contains a 20-bit address tag field, one
valid bit, and one dirty bit. Each cache tag is also associated
with a least recently used bit that is used for replacement policy.
To support multiple cache sizes, the width of the tag fields also
can be varied. If a cache enable bit in processor service register
is not set, loads and stores are treated like non-cacheable
instructions by data cache controller 161.
[0152] A single sixteen-byte write back buffer is provided for
writing back dirty cache lines which need to be replaced. Data
cache unit 160 can provide a maximum of four bytes on a read and a
maximum of four bytes of data can be written into cache 161 in a
single cycle. Diagnostic reads and writes can be done on the
caches.
[0153] Memory Allocation Accelerator
[0154] In one embodiment, data cache unit 165 includes a memory
allocation accelerator 166. Typically, when a new object is
created, fields for the object are fetched from external memory,
stored in data cache 165 and then the field is cleared to zero.
This is a time consuming process that is eliminated by memory
allocation accelerator 166. When a new object is created, no fields
are retrieved from external memory. Rather, memory allocation
accelerator 160 simply stores a line of zeros in data cache 165 and
marks that line of data cache 165 as dirty. Memory allocation
accelerator 166 is particularly advantageous with a write-back
cache. Since memory allocation accelerator 166 eliminates the
external memory access each time a new object is created, the
performance of hardware processor 100 is enhanced.
[0155] Floating Point Unit
[0156] Floating point unit (FPU) 143 includes a microcode
sequencer, input/output section with input/output registers, a
floating point adder, i.e., an ALU, and a floating point
multiply/divide unit. The microcode sequencer controls the
microcode flow and microcode branches. The input/output section
provides the control for input/output data transactions, and
provides the input data loading and output data unloading
registers. These registers also provide intermediate result
storage.
[0157] The floating point adder-ALU includes the combinatorial
logic used to perform the floating point adds, floating point
subtracts, and conversion operations. The floating point
multiply/divide unit contains the hardware for performing
multiply/divide and remainder.
[0158] Floating point unit 143 is organized as a microcoded engine
with a 32-bit data path. This data path is often reused many times
during the computation of the result. Double precision operations
require approximately two to four times the number of cycles as
single precision operations. The floating point ready signal is
asserted one-cycle prior to the completion of a given floating
point operation. This allows integer unit 142 to read the floating
point unit output registers without any wasted interface cycles.
Thus, output data is available for reading one cycle after the
floating point ready signal is asserted.
[0159] Execution Unit Accelerators
[0160] Since the JAVA Virtual Machine Specification of Appendix I
is hardware independent, the virtual machine instructions are not
optimized for a particular general type of processor, e.g., a
complex instruction set computer (CISC) processor, or a reduced
instruction set computer (RISC) processor. In fact, some virtual
machine instructions have a CISC nature and others a RISC nature.
This dual nature complicates the operation and optimization of
hardware processor 100.
[0161] For example, the JAVA virtual machine specification defines
opcode 171 for an instruction lookupswitch, which is a traditional
switch statement.
[0162] The datastream to instruction cache unit 120 includes an
opcode 171, identifying the N-way switch statement, that is
followed zero to three bytes of padding. The number of bytes of
padding is selected so that first operand byte begins at an address
that is a multiple of four. Herein, datastream is used generically
to indicate information that is provided to a particular element,
block, component, or unit.
[0163] Following the padding bytes in the datastream are a series
of pairs of signed four-byte quantities. The first pair is special.
A first operand in the first pair is the default offset for the
switch statement that is used when the argument, referred to as an
integer key, or alternatively, a current match value, of the switch
statement is not equal to any of the values of the matches in the
switch statement. The second operand in the first pair defines the
number of pairs that follow in the datastream.
[0164] Each subsequent operand pair in the datastream has a first
operand that is a match value, and a second operand that is an
offset. If the integer key is equal to one of the match values, the
offset in the pair is added to the address of the switch statement
to define the address to which execution branches. Conversely, if
the integer key is unequal to any of the match values, the default
offset in the first pair is added to the address of the switch
statement to define the address to which execution branches. Direct
execution of this virtual machine instruction requires many
cycles.
[0165] To enhance the performance of hardware processor 100, a
look-up switch accelerator 145 is included in hardware processor
100. Look-up switch accelerator 145 includes an associative memory
which stores information associated with one or more lookup switch
statements. For each lookup switch statement, i.e., each
instruction lookupswitch, this information includes a lookup switch
identifier value, i.e., the program counter value associated with
the lookup switch statement, a plurality of match values and a
corresponding plurality of jump offset values.
[0166] Lookup switch accelerator 145 determines whether a current
instruction received by hardware processor 100 corresponds to a
lookup switch statement stored in the associative memory. Lookup
switch accelerator 145 further determines whether a current match
value associated with the current instruction corresponds with one
of the match values stored in the associative memory. Lookup switch
accelerator 145 accesses a jump offset value from the associative
memory when the current instruction corresponds to a lookup switch
statement stored in the memory and the current match value
corresponds with one of the match values stored in the memory
wherein the accessed jump offset value corresponds with the current
match value.
[0167] Lookup switch accelerator 145 further includes circuitry for
retrieving match and jump offset values associated with a current
lookup switch statement when the associative memory does not
already contain the match and jump offset values associated with
the current lookup switch statement. Lookup switch accelerator 145
is described in more detail in U.S. patent application Ser. No.
08/______, entitled "LOOK-UP SWITCH ACCELERATOR AND METHOD OF
OPERATING SAME" naming Marc Tremblay and James Michael O'Connor as
inventors, assigned to the assignee of this application, and filed
on even date herewith with Attorney Docket No. SP2040, which is
incorporated herein by reference in its entirety.
[0168] In the process of initiating execution of a method of an
object, execution unit 140 accesses a method vector to retrieve one
of the method pointers in the method vector, i.e., one level of
indirection. Execution unit 140 then uses the accessed method
pointer to access a corresponding method, i.e., a second level of
indirection.
[0169] To reduce the levels of indirection within execution unit
140, each object is provided with a dedicated copy of each of the
methods to be accessed by the object. Execution unit 140 then
accesses the methods using a single level of indirection. That is,
each method is directly accessed by a pointer which is derived from
the object. This eliminates a level of indirection which was
previously introduced by the method pointers. By reducing the
levels of indirection, the, operation of execution unit 140 can be
accelerated. The acceleration of execution unit 140 by reducing the
levels of indirection experienced by execution unit 140 is
described in more detail in U.S. patent application Ser. No.
08/______, entitled "REPLICATING CODE TO ELIMINATE A LEVEL OF
INDIRECTION DURING EXECUTION OF AN OBJECT ORIENTED COMPUTER
PROGRAM" naming Marc Tremblay and James Michael O'Connor as
inventors, assigned to the assignee of this application, and filed
on even date herewith with Attorney Docket No. SP2043, which is
incorporated herein by reference in its entirety.
[0170] Getfield-Putfield Accelerator
[0171] Other specific functional units and various translation
lookaside buffer (TLB) types of structures may optionally be
included in hardware processor 100 to accelerate accesses to the
constant pool. For example, the JAVA virtual machine specification
defines an instruction putfield, opcode 181, that upon execution
sets a field in an object and an instruction getfield, opcode 180,
that upon execution fetches a field from an object. In both of
these instructions, the opcode is followed by an index byte one and
an index byte two. Operand stack 423 contains a reference to an
object followed by a value for instruction putfield, but only a
reference to an object for instruction getfield.
[0172] Index bytes one and two are used to generate an index into
the constant pool of the current class. The item in the constant
pool at that index is a field reference to a class name and a field
name. The item is resolved to a field block pointer which has both
the field width, in bytes, and the field offset, in bytes.
[0173] An optional getfield-putfield accelerator 146 in execution
unit 140 stores the field block pointer for instruction getfield or
instruction putfield in a cache, for use after the first invocation
of the instruction, along with the index used to identify the item
in the constant pool that was resolved into the field block pointer
as a tag. Subsequently, execution unit 140 uses index bytes one and
two to generate the index and supplies the index to
getfield-putfield accelerator 146. If the index matches one of the
indexes stored as a tag, i.e., there is a hit, the field block
pointer associated with that tag is retrieved and used by execution
unit 140. Conversely, if a match is not found, execution unit 140
performs the operations described above. Getfield-putfield
accelerator 146 is implemented without using self-modifying code
that was used in one embodiment of the quick instruction
translation described above.
[0174] In one embodiment, getfield-putfield accelerator 146
includes an associative memory that has a first section that holds
the indices that function as tags, and a second section that holds
the field block pointers. When an index is applied through an input
section to the first section of the associative memory, and there
is a match with one of the stored indices, the field block pointer
associated with the stored index that matched in input index is
output from the second section of the associative memory.
[0175] Bounds Check Unit
[0176] Bounds check unit 147 (FIG. 1) in execution unit 140 is an
optional hardware circuit that checks each access to an element of
an array to determine whether the access is to a location within
the array. When the access is to a location outside the array,
bounds check unit 147 issues an active array bound exception signal
to execution unit 140. In response to the active array bound
exception signal, execution unit 140 initiates execution of an
exception handler stored in microcode ROM 141 that in handles the
out of bounds array access.
[0177] In one embodiment, bounds check unit 147 includes an
associative memory element in which is stored a array identifier
for an array, e.g., a program counter value, and a maximum value
and a minimum value for the array. When an array is accessed, i.e,
the array identifier for that array is applied to the associative
memory element, and assuming the array is represented in the
associative memory element, the stored minimum value is a first
input signal to a first comparator element, sometimes called a
comparison element, and the stored maximum value is a first input
signal to a second comparator element, sometimes also called a
comparison element. A second input signal to the first and second
comparator elements is the value associated with the access of the
array's element.
[0178] If the value associated with the access of the array's
element is less than or equal to the stored maximum value and
greater than or equal to the stored minimum value, neither
comparator element generates an output signal. However, if either
of these conditions is false, the appropriate comparator element
generates the active array bound exception signal. A more detailed
description of one embodiment of bounds check unit 147 is provided
in U.S. patent application Ser. No. 08/______, entitled "PROCESSOR
WITH ACCELERATED ARRAY ACCESS BOUNDS CHECKING" naming Marc
Tremblay, James Michael O'Connor, and William N. Joy as inventors,
assigned to the assignee of this application, and filed on even
date herewith with Attorney Docket No. SP2041 which is incorporated
herein by reference in its entirety.
[0179] The JAVA Virtual Machine Specification defines that certain
instructions can cause certain exceptions. The checks for these
exception conditions are implemented, and a hardware/software
mechanism for dealing with them is provided in hardware processor
100 by information in microcode ROM 149 and program counter and
trap control logic 170. The alternatives include having a trap
vector style or a single trap target and pushing the trap type on
the stack so that the dedicated trap handler routine determines the
appropriate action.
[0180] No external cache is required for the architecture of
hardware processor 100. No translation lookaside buffers need be
supported.
[0181] FIG. 5 illustrates several possible add-ons to hardware
processor 100 to create a unique system. Circuits supporting any of
the eight functions shown, i.e., NTSC encoder 501, MPEG 502,
Ethernet controller 503, VIS 504, ISDN 505, I/O controller 506, ATM
assembly/reassembly 507, and radio link 508 can be integrated into
the same chip as hardware processor 100 of this invention.
[0182] FIG. 6 is a block diagram of one embodiment of a stack
management unit 150. Stack management unit 150 serves as a high
speed buffer between stack 400 and hardware processor 100. Hardware
processor 100 accesses stack management unit 150 as if stack
management unit 150 were stack 400. Stack management unit 150
automatically transfers data between stack management unit 150 and
stack 400 as necessary to provide improve the throughput of data
between stack 400 and hardware processor 100. In the embodiment of
FIG. 1, if hardware processor 100 requires a data word which is not
cached in stack management unit 150, data cache unit 160 retrieves
the requested data word and places the requested data word at the
top of stack cache 155.
[0183] Stack management unit 150 contains a stack cache memory
circuit 610. Stack cache memory circuit 610 is typically fast
memory devices such as a register file or SRAM; however, slower
memory devices such as DRAM can also be used. In the embodiment of
FIG. 6, access to stack cache memory circuit 610 is controlled by
stack control unit 152. A write port 630 allows hardware processor
100 to write data on data lines 635 to stack cache memory circuit
610. Read port 640 and read port 650 allow hardware processor 100
to read data from stack cache memory circuit 610 on data lines 645
and 655, respectively. Two read ports are provided to increase
throughput since many operations of stack-based computing systems
require two operands from stack 400. Other embodiments of stack
cache 155 may provide more or less read and write ports.
[0184] As explained above, dribble manager unit 151 controls the
transfer of data between stack 400 (FIG. 4(a)) and stack cache
memory circuit 610. In the embodiment shown in FIG. 1, the transfer
of data between stack 400 and stack cache memory circuit 610 goes
through data cache unit 160. Dribble manager unit 151 includes a
fill control unit 694 and a spill control unit 698. In some
embodiments of dribble manager unit 151, fill control unit 694 and
spill control unit 698 function independently. Fill control unit
694 determines if a fill condition exists. If the fill condition
exists, fill control unit 694 transfers data words from stack 400
to stack cache memory circuit 610 on data lines 675 through a write
port 670. Spill control unit 698 determines if a spill condition
exists. If the spill condition exists, spill control unit 698
transfers data words from stack cache memory circuit 610 to stack
400 through read port 680 on data lines 685. Write port 670 and
read port 680 allows transfers between stack 400 and stack cache
memory circuit 610 to occur simultaneously with reads and writes
controlled by stack control unit 152. If contention for read and
write ports of stack cache memory circuit 610 is not important,
dribble manager unit 151 can share read and write ports with stack
control unit 152.
[0185] Although stack management unit 150 is described in the
context of buffering stack 400 for hardware processor 100, stack
management unit 150 can perform caching for any stack-based
computing system. The details of hardware processor 100, are
provided only as an example of one possible stack-based computing
system for use with the present invention. Thus, one skilled in the
art can use the principles described herein to design a stack
management unit in accordance to the present invention for any
stack-based computing system.
[0186] FIG. 7 shows a conceptual model of the memory architecture
of stack cache memory circuit 610 for one embodiment of stack cache
155. Specifically, in the embodiment of FIG. 7, stack cache memory
circuit 610 is a register file organized in a circular buffer
memory architecture capable of holding 64 data words. Other
embodiments may contain a different number of data words. The
circular memory architecture causes data words in excess of the
capacity of stack cache memory circuit 610 to be written to
previously used registers. If stack cache memory unit 610 uses a
different memory device, such as an SRAM, different registers would
correspond to different memory locations. One technique to address
registers in a circular buffer is to use pointers containing modulo
stack cache size (modulo-SCS) addresses to the various registers of
stack cache memory circuit 610. As used herein, modulo-N operations
have the results of the standard operation mapped to a number
between 0 and SCS-1 using a standard MOD N functions Some common
modulo operations are defined as follows
[0187] Modulo-N addition of X and Y=(X+Y) MOD N,
[0188] Modulo-N subtraction of X and Y=(X-Y) MOD N,
[0189] Modulo-N increment of X by Y=(X+Y) MOD N
[0190] Modulo-N decrement of X by Y=(X-Y) MOD N.
[0191] One embodiment of the pointer addresses of the registers of
stack cache memory circuit 610 are shown in FIG. 7 as numbered 0-63
along the outer edge of stack cache memory circuit 610. Thus for
the embodiment of FIG. 7, if 70 data words (numbered 1 to 70) are
written to stack cache memory circuit 610 when stack cache memory
circuit 610 is empty, data words 1 to 64 are written to registers 0
to 63, respectively and data words 65 to 70 are written
subsequently to registers 0 to 5. Prior to writing data words 65 to
70, dribble manager unit 151, as described below, transfers data
words 1 to 6 which were in registers 0 to 5 to stack 400.
Similarly, as data words 70 to 65 are read out of stack cache
memory circuit 610, data words 1 to 6 can be retrieved from stack
400 and placed in memory locations 0 to 5.
[0192] Since most reads and writes on a stack are from the top of
the stack, a pointer OPTOP contains the location of the top of
stack 400, i.e. the top memory location. In some embodiments of
stack management unit 150, pointer OPTOP is a programmable register
in execution unit 140. However other embodiments of stack
management unit 150 maintain pointer OPTOP in stack control unit
152. Since pointer OPTOP is often increased by one, decreased by
one, or changed by a specific amount, pointer OPTOP, in one
embodiment is a programmable up/down counter.
[0193] Since stack management unit 150 contains the top portion of
stack 400, pointer OPTOP indicates the register of stack cache
memory circuit 610 containing the most recently written data word
in stack cache memory circuit 610, i.e. pointer OPTOP points to the
register containing the most recently written data word also called
the top register. Some embodiments of stack management unit 150
also contains a pointer OPTOP1 (not shown) which points to the
register preceding the register pointed to by pointer OPTOP.
Pointer OPTOP1 can improve the performance of stack management unit
150 since many operations in hardware processor 100 require two
data words from stack management unit 150.
[0194] Pointer OPTOP and pointer OPTOP1 are incremented whenever a
new data word is written to stack cache 155. Pointer OPTOP and
pointer OPTOP1 are decremented whenever a stacked data word, i.e. a
data word already in stack 400, is popped off of stack cache 155.
Since some embodiments of hardware processor 100 may add or remove
multiple data words simultaneously, pointer OPTOP and OPTOP1 are
implemented, in one embodiment as programmable registers so that
new values can be written into the registers rather than requiring
multiple increment or decrement cycles.
[0195] If stack cache 155 is organized using sequential addressing,
pointer OPTOP1 may also be implemented using a modulo SCS
subtractor which modulo-SCS subtracts one from pointer OPTOP. Some
embodiments of stack cache 155 may also include pointers OPTOP2 or
pointer OPTOP3.
[0196] Since data words are stored in stack cache memory circuit
610 circularly, the bottom of stack cache memory circuit 610 can
fluctuate. Therefore, most embodiments of stack cache memory
circuit 610 include a pointer CACHE_BOTTOM to indicate the bottom
memory location of stack cache memory circuit 610. Pointer
CACHE_BOTTOM is typically maintained by dribble manager unit 151.
The process to increment or decrement pointer CACHE_BOTTOM varies
with the specific embodiment of stack management unit 150. Pointer
CACHE_BOTTOM is typically implemented as a programmable up/down
counter.
[0197] Some embodiments of stack management unit 150 also includes
other pointers, such as pointer VARS, which points to a memory
location of a data word that is often accessed. For example, if
hardware processor 100 is implementing the JAVA Virtual Machine,
entire method frames may be placed in stack management unit 150.
The method frames often contain local variables that are accessed
frequently. Therefore, having pointer VARS pointed to the first
local variable of the active method decreases the access time
necessary to read the local variable. Other pointers such as a
pointer VARS1 (not shown) and a pointer VARS2 (not shown) may point
to other often used memory locations such as the next two local
variables of the active method in a JAVA Virtual Machine. In some
embodiments of stack management unit 150, these pointers are
maintained in stack control unit 152. In embodiments adapted for
use with hardware processor 100, pointer VARS is stored in a
programmable register in execution unit 140. If stack cache 155 is
organized using sequential addressing, pointer VARS1 may also be
implemented using a modulo-SCS adder which modulo-SCS adds one to
pointer VARS.
[0198] To determine which data words to transfer between stack
cache memory circuit 610 and stack 400, stack management unit 150,
typically tags, i.e. tracks, the valid data words and the data
words which are stored in both stack cache memory circuit 610 and
stack 400. FIG. 8 illustrates one tagging scheme used in some
embodiments of stack management unit 150. Specifically, FIG. 8
shows a register 810 from stack cache memory circuit 610. The
actual data word is stored in data section 812. A valid bit 814 and
a saved bit 816 are used to track the status of register 810. If
valid bit 814 is at a valid logic state, typically logic high, data
section 812 contains a valid data word. If valid bit 814 is at an
invalid logic state, typically logic low, data section 812 does not
contain a valid data word. If saved bit 816 is at a saved logic
state, typically logic high, the data word contained in data
section 812 is also stored in stack 400. However, if saved bit 816
is at an-unsaved logic state, typically logic low, the data word
contained in data section 812 is not stored in stack 400.
Typically, when stack management unit 150 is powered up or reset,
valid bit 814 of each register is set to the invalid logic state
and saved bit 816 of each register is set to the unsaved logic
state.
[0199] For the embodiment illustrated in FIG. 6 using the tagging
method of FIG. 8, when stack control unit 152 writes a data word to
a register in stack cache memory circuit 610 through write port 630
the valid bit of that register is set to the valid logic state and
the saved bit of that register is set to the unsaved logic state.
When dribble manager unit 151 transfer a data word to a register of
stack cache memory circuit 610 through write port 670, the valid
bit of that register is set to the valid logic state and the saved
bit of that register is set to the saved logic state since the data
word is currently saved in stack 400.
[0200] When hardware processor 100 reads a stacked data word using
a stack popping operation from a register of stack cache memory
circuit 610 through either read port 640 or read port 650 the valid
bit of that register is set to the invalid logic state and the
saved bit of that location is set to the unsaved logic state.
Typically, stack popping operations use the register indicated by
pointer OPTOP or pointer OPTOP1.
[0201] When hardware processor 100 reads a data word with a
non-stack popping operation from a register of stack cache memory
circuit 610 through either read port 640 or read port 650 the valid
bit and saved bit of the register are not changed. For example, if
hardware processor 100 is implementing the JAVA Virtual Machine, a
local variable stored in stack cache memory circuit 610 in the
register indicated by pointer VARS may be used repeatedly and
should not be removed from stack cache 155. When dribble manager
unit 151 copies a data word from a register of stack cache memory
circuit 610 to stack 400 through read port 680, the valid bit of
that register remains in the valid logic state since the saved data
word is still contained in that register and the saved bit of that
register is set to the saved logic state.
[0202] Since stack cache 155 is generally much smaller than the
memory address space of hardware processor 100, the pointers used
to access stack cache memory circuit 610 are generally much smaller
than general memory addresses. The specific technique used to map
stack cache 155 into the memory space of hardware processor 100 can
vary. In one embodiment of hardware processor 100 the pointers used
to access stack cache memory circuit 610 are only the lower bits of
general memory pointers, i.e. the least significant bits. For
example, if stack cache memory circuit 610 comprises 64 registers,
pointers OPTOP, VARS, and CACHE_BOTTOM need only be six bits long.
If hardware processor 100 has a 12 bit address space, pointers
OPTOP, VARS, and CACHE_BOTTOM could be the lower six bits of a
general memory pointer. Thus stack cache memory circuit 610 is
mapped to a specific segment of the address space having a unique
upper six bit combination.
[0203] Some embodiments of stack cache management unit 150 may be
used with purely stacked based computing system so that there is
not a memory address space for the system. In this situation, the
pointers for accessing stack cache 155 are only internal to stack
cache management unit 150.
[0204] As explained above, hardware processor 100 primarily
accesses data near the top of the stack. Therefore, stack
management unit 150 can improve data accesses of hardware processor
100 while only caching the top portion of stack 400. When hardware
processor 100 pushes more data words to stack management unit 150
than stack cache memory circuit 610 is able to store, the data
words near the bottom of stack cache memory circuit 610 are
transferred to stack 400. When hardware processor 100 pops data
words out of stack cache 155, data words from stack 400 are copied
under the bottom of stack cache memory circuit 610, and pointer
CACHE_BOTTOM is decremented to point to the new bottom of stack
cache memory circuit 610.
[0205] Determination of when to transfer data words between stack
400 and stack cache memory circuit 610 as well as how many data
words to transfer can vary. In general, dribble manager unit 151
should transfer data from stack cache memory circuit 610 to stack
400, i.e. a spill operation, as hardware processor fills stack
cache memory circuit 610. Conversely, dribble manager unit 151
should copy data from stack 400 to stack cache memory circuit 610,
i.e. a fill operation, as hardware processor empties stack cache
memory circuit 610.
[0206] FIG. 9 shows one embodiment of dribble manager unit 151 in
which decisions on transferring data from stack cache memory
circuit 610 to stack 400, i.e. spilling data, are based on the
number of free registers in stack cache memory circuit 610. Free
registers includes registers without valid data as well as
registers containing data already stored in stack 400, i.e.
registers with saved bit 816 set to the saved logic state.
Decisions on transferring data from stack 400 to stack cache memory
circuit 610, i.e. filling data, are based on the number of used
registers. A used registers contains a valid but unsaved data word
in stack cache memory circuit 610.
[0207] Specifically in the embodiment of FIG. 9, dribble manager
unit 151 further includes a stack cache status circuit 910 and a
cache bottom register 920, which can be a programmable up/down
counter. Stack cache status circuit 910, receives pointer
CACHE_BOTTOM from cache bottom register 920 and pointer OPTOP to
determine the number of free registers FREE and the number of used
registers USED.
[0208] For a circular buffer using sequential modulo-SCS
addressing, as in FIG. 7, the number of free registers FREE is
defined as
[0209] FREE=SCS-(OPTOP-CACHE_BOTTOM+1) MOD SCS, where SCS is the
size of stack cache 155. Thus, for the specific pointer values
shown in FIG. 7, the number of free registers FREE is 34, as
calculated by:
FREE=64-((27-62+1)MOD64)=34.
[0210] Similarly, for a circular buffer using sequential modulo
addressing, the number of used registers USED defined as
USED=(OPTOP-CACHE.sub.--BOTTOM+1)MODSCS.
[0211] Thus, for the specific pointer values shown in FIG. 7, the
number of used registers USED is 30, as calculated by:
USED=(27-62+1)MOD64.
[0212] Thus, stack cache status circuit 910 can be implemented with
a modulo SCS adder/subtractor. The number of used registers USED
and the number of free registers FREE can also be generated using a
programmable up/down counters. For example, a used register can be
incremented whenever a data word is added to stack cache 155 and
decremented whenever a data word is removed from stack cache 155.
Specifically, if pointer OPTOP is modulo-SCS incremented by some
amount, the used register is incremented by the same amount. If
pointer OPTOP is modulo-SCS decremented by some amount, the used
register is decremented by the same amount. However, if pointer
CACHE_BOTTOM is modulo-SCS incremented by some amount, the used
register is decremented by the same amount. If pointer CACHE_BOTTOM
is modulo-SCS decremented by some amount, the used register is
incremented the same amount. The number of free registers FREE can
be generated by subtracting the number of used registers USED from
the total number of registers.
[0213] Spill control unit 694 (FIGS. 6 and 9) includes a cache high
threshold register 930 and a comparator 940. Comparator 940
compares the value in cache high threshold register 930 to the
number of free registers FREE. If the number of free registers FREE
is less than the value in cache high threshold register 930,
comparator 940 drives a spill signal SPILL to a spill logic level,
typically logic high, to indicate that the spill condition exists
and one or more data words should be transferred from stack cache
memory circuit 610 to stack 400, i.e. a spill operation should be
performed. The spill operation is described in more detail below.
Typically, cache high threshold register 930 is programmable by
hardware processor 100.
[0214] Fill control unit 698 (FIGS. 6 and 9) includes a cache low
threshold register 950 and a comparator 960. Comparator 960
compares the value in cache low threshold register 950 to the
number of used registers USED. If the number of used registers is
less than the value in cache low threshold register 950, comparator
960 drives a fill signal FILL to a fill logic level, typically
logic high, to indicate that the fill condition exists and one or
more data words should be transferred from stack 400 to stack cache
memory circuit 610, i.e. a fill operation should be performed. The
fill operation is described in more detail below. Typically, cache
low threshold register 950 is programmable by hardware processor
100.
[0215] If the value in cache high threshold 930 and cache low
threshold 940 is always the same, a single cache threshold register
can be used. Fill control unit 698 can be modified to use the
number of free registers FREE to drive signal FILL to the fill
logic level if then number of free registers is greater than the
value in cache low threshold 950, with a proper modification of the
value in cache low threshold 950. Alternatively, spill control unit
694 can be modified to use the number of used registers.
[0216] FIG. 10A shows another embodiment of dribble manager unit
151, which uses a high-water mark/low-water mark heuristic to
determine when a spill condition or a fill condition exists. Spill
control unit 694 includes a high water mark register 1010
implemented as a programmable up/down counter. A comparator 1020 in
spill control unit 694 compares the value in high water mark
register 1010, i.e. the high water mark, with pointer OPTOP. If
pointer OPTOP is greater than the high water mark, comparator 1020
drives spill signal SPILL to the spill logic level to indicate a
spill operation should be performed. Since, the high water mark is
relative to pointer CACHE_BOTTOM, the high water mark is modulo-SCS
incremented and modulo-SCS decremented whenever pointer
CACHE_BOTTOM is modulo-SCS incremented or modulo-SCS decremented,
respectively.
[0217] Fill control unit 698 includes a low water mark register
1010 implemented as a programmable up/down counter. A comparator
1030 in fill control unit 698 compares the value in low water mark
register 1030, i.e. the low water mark, with pointer OPTOP. If
pointer OPTOP is less than the low water mark, comparator 1040
drives fill signal FILL to the fill logic level to indicate a fill
operation should be performed. Since the low water mark is relative
to pointer CACHE_BOTTOM, the low water mark register is modulo-SCS
incremented and modulo-SCS decremented whenever pointer
CACHE_BOTTOM is modulo-SCS incremented or modulo-SCS decremented,
respectively.
[0218] FIG. 10B shows an alternative circuit to generate the high
water mark and low water mark. Cache high threshold register 930,
typically implemented as a programmable register, contains the
number of free registers which should be maintained in stack cache
memory circuit 610. The high water mark is then calculated by
modulo-SCS subtractor 1050 by modulo-SCS subtracting the value in
cache high threshold register 930 from pointer CACHE_BOTTOM stored
in cache bottom register 920.
[0219] The low water mark is calculated by doing a modulo-SCS
addition. Specifically, cache low threshold register 950 is
programmed to contain the minimum number of used data registers
desired to be maintained in stack cache memory circuit 610. The low
water mark is then calculated by modulo-SCS adder 1060 by
modulo-SCS adding the value in cache low threshold register 950
with pointer CACHE_BOTTOM stored in cache bottom register 920.
[0220] As described above, a spill operation is the transfer of one
or more data words from stack cache memory circuit 610 to stack
400. In the embodiment of FIG. 1, the transfers occurs though data
cache unit 160. The specific interface between stack management
unit 150 and data cache unit 160 can vary. Typically, stack
management unit 150, and more specifically dribble manager unit
151, sends the data word located at the bottom of stack cache 155,
as indicated by pointer CACHE_BOTTOM from read port 680 to data
cache unit 160. The value of pointer CACHE_BOTTOM is also provided
to data cache unit 160 so that data cache unit 160 can address the
data word appropriately. The saved bit of the register indicated by
pointer CACHE_BOTTOM is set to the saved logic level. In addition,
pointer CACHE_BOTTOM is modulo-SCS incremented by one. Other
registers as described above may also be modulo-SCS incremented by
one. For example, high water mark register 1010 (FIG. 10A) and low
water mark 1030 would be modulo-SCS incremented by one. Some
embodiments of dribble manager unit 151 transfer multiple words for
each spill operation. For these embodiments, pointer CACHE_BOTTOM
is modulo-SCS incremented by the number words transferred to stack
400.
[0221] In embodiments using a saved bit and valid bit, as shown in
FIG. 8, some optimization is possible. Specifically, if the saved
bit of the data register pointed to by pointer CACHE_BOTTOM is at
the saved logic level, the data word in that data register is
already stored in stack 400. Therefore, the data word in that data
register does not need to be copied to stack 400. However, pointer
CACHE_BOTTOM is still modulo-SCS incremented by one.
[0222] A fill operation transfers data words from stack 400 to
stack cache memory circuit 610. In the embodiment of FIG. 1, the
transfers occurs though data cache unit 160. The specific interface
between stack management unit 150 and data cache unit 160 can vary.
Typically, stack management unit 150, and more specifically dribble
manager unit 151, determines whether the data register preceding
the data register pointed by CACHE_BOTTOM is free, i.e. either the
saved bit is in the saved logic state or the valid bit is in the
invalid logic state. If the data register preceding the data
register pointed to by pointer CACHE_BOTTOM is free, dribble
manager unit 151 requests a data word from stack 400 by sending a
request with the value of pointer CACHE_BOTTOM modulo-SCS minus
one. When the data word is received from data cache unit 160,
pointer CACHE_BOTTOM is modulo-SCS decremented by one and the
received data word is written to the data register pointed to by
pointer CACHE_BOTTOM through write port 670. Other registers as
described above may also be modulo-SCS decremented. The saved bit
and valid bit of the register pointed to by pointer CACHE_BOTTOM
are set to the saved logic state and valid logic state,
respectively. Some embodiments of dribble manager unit 151 transfer
multiple words for each spill operation. For these embodiments,
pointer CACHE_BOTTOM is modulo-SCS decremented by the number words
transferred to stack 400.
[0223] In embodiments using a saved bit and valid bit, as shown in
FIG. 8, some optimization is possible. Specifically, if the saved
bit and valid bit of the data register preceding the data register
pointed to by pointer CACHE_BOTTOM is at the saved logic level and
the valid logic level, respectively, then the data word in that
data register was never overwritten.
[0224] Therefore, the data word in that data register does not need
to be copied from stack 400. However, pointer CACHE_BOTTOM is still
modulo-SCS decremented by one.
[0225] As stated above, in one embodiment of stack cache 155,
hardware processor 100 accesses stack cache memory circuit 610
(FIG. 6) through write port 630, read port 640 and read port 650.
Stack control unit 152 generates pointers for write port 630, read
port 640, and read port 650 based on the requests of hardware
processor 100. FIG. 11 shows a circuit to generate pointers for a
typical operation which reads two data words from stack cache 155
and writes one data word to stack cache 155. The most common stack
manipulation for a stack-based computing system is to pop the top
two data words off of the stack and to push a data word onto the
top of the stack. Therefore, the circuit of FIG. 11 is configured
to be able to provide read pointers to the value of pointer OPTOP
and the value of pointer OPTOP modulo-SCS minus one, and a write
pointer to the current value of OPTOP modulo-SCS minus one.
[0226] Multiplexer (MUX) 1110 drives a read pointer RP1 for read
port 640. A select line RS1 controlled by hardware processor 100
determines whether multiplexer 1110 drives the same value as
pointer OPTOP or a read address R_ADDR1 as provided by hardware
processor 100.
[0227] Multiplexer 1120 provides a read pointer RP2 for read port
650. Modulo adder 1140 modulo-SCS adds negative one to the value of
pointer OPTOP and drives the resulting sum to multiplexer 1120. A
select line RS2 controlled by hardware processor 100 determines
whether multiplexer 1120 drives the value from modulo adder 1140 or
a read address R_ADDR2 as provided by hardware processor 100.
[0228] Multiplexer 1130 provides a write pointer WP for write port
630. A modulo adder 1150 modulo-SCS adds one to the value of
pointer OPTOP and drives the resulting sum to multiplexer 1130.
Select lines WS controlled by hardware processor 100 determines
whether multiplexer 1130 drives the value from modulo-SCS adder
1140, the value from modulo-SCS adder 1150, or a write address
W_ADDR as provided by hardware processor 100.
[0229] FIG. 12 shows a circuit that generates a read pointer R for
read port 640 or read port 650 in embodiments allowing accessing
stack cache memory circuit using pointer VARS. Multiplexer 1260
drives read pointer R to one of several input values received on
input ports 1261-1267 as determined by selection signals RS.
Selection signals RS are controlled by hardware processor 100. The
value of pointer OPTOP is driven to input port 1261. Modulo-SCS
adder 1210 drives the modulo-SCS sum of the value of pointer OPTOP
with negative one to input port 1262. Modulo-SCS adder 1210 drives
the modulo-SCS sum of the value of pointer OPTOP with negative two
to input port 1263. The value of pointer VARS is driven to input
port 1264. Modulo-SCS adder 1230 drives the modulo-SCS sum of the
value of pointer VARS with one to input port 1265. Modulo-SCS adder
1240 drives the modulo-SCS sum of the value of pointer VARS with
two to input port 1266. Modulo adder-SCS 1250 drives the modulo-SCS
sum of the value of pointer VARS with three to input port 1263.
Other embodiments may provide other values to the input ports of
multiplexer 1260.
[0230] Thus by using the stack cache according to the principles of
the invention, a dribbling management unit can efficiently control
transfers between the stack cache and the stack. Specifically, the
dribbling management unit is able to transfer data out of the stack
cache to make room for additional data as necessary and transfer
data into the stack cache as room becomes available transparently
to the stack-based computing system using the stack management
unit.
[0231] The various embodiments of the structure and method of this
invention that are described above are illustrative only of the
principles of this invention and are not intended to limit the
scope of the invention to the particular embodiments described. In
view of this disclosure, those skilled-in-the-art can define other
memory circuits, registers, counters, stack-based computing
systems, dribble management units, fill control units, spill
control units, read ports, write ports, and use these alternative
features to create a method or system of stack caching according to
the principles of this invention.
APPENDIX I
[0232] The JAVA Virtual Machine Specification .COPYRGT.1993, 1994,
1995 Sun Microsystems, Inc. 2550 Garcia Avenue, Mountain View,
Calif. 94043-1100 U.S.A.
[0233] All rights reserved. This BETA quality release and related
documentation are protected by copyright and distributed under
licenses restricting its use, copying, distribution, and
decompilation. No part of this release or related documentation may
be reproduced in any form by any means without prior written
authorization of Sun and its licensors, if any.
[0234] Portions of this product may be derived from the UNIX.RTM.
and Berkeley 4.3 BSD systems, licensed from UNIX System
Laboratories, Inc. and the University of California, respectively.
Third-party font software in this release is protected by copyright
and licensed from Sun's Font Suppliers.
[0235] RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by
the United States Government is subject to the restrictions set
forth in DFARS 252.227-7013 (c)(1)(ii) and FAR 52.227-19.
[0236] The release described in this manual may be protected by one
or more U.S. patents, foreign patents, or pending applications.
[0237] TRADEMARKS
[0238] Sun, Sun Microsystems, Sun Microsystems Computer
Corporation, the Sun logo, the Sun Microsystems Computer
Corporation logo, WebRunner, JAVA, FirstPerson and the FirstPerson
logo and agent are trademarks or registered trademarks of Sun
Microsystems, Inc. The "Duke" character is a trademark of Sun
Microsystems, Inc. and Copyright .COPYRGT.1992-1995 Sun
Microsystems, Inc. All Rights Reserved. UNIX.RTM. is a registered
trademark in the United States and other countries, exclusively
licensed through X/Open Company, Ltd. OPEN LOOK is a registered
trademark of Novell, Inc. All other product names mentioned herein
are the trademarks of their respective owners.
[0239] All SPARC trademarks, including the SCD Compliant Logo, are
trademarks or registered trademarks of SPARC International, Inc.
SPARCstation, SPARCserver, SPARCengine, SPARCworks, and
SPARCompiler are licensed exclusively to Sun Microsystems, Inc.
Products bearing SPARC trademarks are based upon an architecture
developed by Sun Microsystems, Inc.
[0240] The OPEN LOOK.RTM. and Sun.TM. Graphical User Interfaces
were developed by Sun Microsystems, Inc. for its users and
licensees. Sun acknowledges the pioneering efforts of Xerox in
researching and developing the concept of visual or graphical user
interfaces for the computer industry. Sun holds a non-exclusive
license from Xerox to the Xerox Graphical User Interface, which
license also covers Sun's licensees who implement OPEN LOOK GUIs
and otherwise comply with Sun's written license agreements.
[0241] X Window System is a trademark and product of the
Massachusetts Institute of Technology.
[0242] THIS PUBLICATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NON-INFRINGEMENT.
[0243] THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR
TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE
INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW
EDITIONS OF THE PUBLICATION. SUN MICROSYSTEMS, INC. MAY MAKE
IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S)
DESCRIBED IN THIS PUBLICATION AT ANY TIME.
[0244] Preface
[0245] This document describes version 1.0 of the JAVA Virtual
Machine and its instruction set. We have written this document to
act as a specification for both compiler writers, who wish to
target the machine, and as a specification for others who may wish
to implement a compliant JAVA Virtual Machine.
[0246] The JAVA Virtual Machine is an imaginary machine that is
implemented by emulating it in software on a real machine. Code for
the JAVA Virtual Machine is stored in .class files, each of which
contains the code for at most one public class.
[0247] Simple and efficient emulations of the JAVA Virtual Machine
are possible because the machine's format is compact and efficient
bytecodes. Implementations whose native code speed approximates
that of compiled C are also possible, by translating the bytecodes
to machine code, although Sun has not released such implementations
at this time.
[0248] The rest of this document is structured as follows:
[0249] Chapter 1 describes the architecture of the JAVA Virtual
Machine;
[0250] Chapter 2 describes the class file format;
[0251] Chapter 3 describes the bytecodes; and
[0252] Appendix A contains some instructions generated internally
by Sun's implementation of the JAVA Virtual Machine. While not
strictly part of the specification we describe these here so that
this specification can serve as a reference for our implementation.
As more implementations of the JAVA Virtual Machine become
available, we may remove Appendix A from future releases.
[0253] Sun will license the JAVA Virtual Machine trademark and logo
for use with compliant implementations of this specification. If
you are considering constructing your own implementation of the
JAVA Virtual Machine please contact us, at the email address below,
so that we can work together to insure 100% compatibility of your
implementation.
[0254] Send comments on this specification or questions about
implementing the JAVA Virtual Machine to our electronic mail
address:JAVA@JAVA.sun.com- .
[0255] 1. JAVA Virtual Machine Architecture
[0256] 1.1 Supported Data Types
[0257] The virtual machine data types include the basic data types
of the JAVA language:
1 byte // 1-byte signed 2's complement integer short // 2-byte
signed 2's complement integer int // 4-byte signed 2's complement
integer long // 8-byte signed 2's complement integer float //
4-byte IEEE 754 single-precision float double // 8-byte IEEE 754
double-precision float char // 2-byte unsigned Unicode
character
[0258] Nearly all JAVA type checking is done at compile time. Data
of the primitive types shown above need not be tagged by the
hardware to allow execution of JAVA. Instead, the bytecodes that
operate on primitive values indicate the types of the operands so
that, for example, the iadd, ladd, fadd, and dadd instructions each
add two numbers, whose types are int, long, float, and double,
respectively
[0259] The virtual machine doesn't have separate instructions for
boolean types. Instead, integer instructions, including integer
returns, are used to operate on boolean values; byte arrays are
used for arrays of boolean.
[0260] The virtual machine specifies that floating point be done in
IEEE 754 format, with support for gradual underflow. Older computer
architectures that do not have support for IEEE format may run JAVA
numeric programs very slowly.
[0261] Other virtual machine data types include:
[0262] object //4-byte reference to a JAVA object
[0263] returnAddress //4 bytes, used with jsr/ret/jsr_w/ret_w
instructions
[0264] Note: JAVA arrays are treated as objects.
[0265] This specification does not require any particular internal
structure for objects. In our implementation an object reference is
to a handle, which is a pair of pointers: one to a method table for
the object, and the other to the data allocated for the object.
Other implementations may use inline caching, rather than method
table dispatch; such methods are likely to be faster on hardware
that is emerging between now and the year 2000.
[0266] Programs represented by JAVA Virtual Machine bytecodes are
expected to maintain proper type discipline and an implementation
may refuse to execute a bytecode program that appears to violate
such type discipline.
[0267] While the JAVA Virtual Machines would appear to be limited
by the bytecode deonition to running on a 32-bit address space
machine, it is possible to build a version of the JAVA Virtual
Machine that automatically translates the bytecodes into a 64-bit
form. A description of this transformation is beyond the scope of
the JAVA Virtual Machine Specification.
[0268] 1.2 Registers
[0269] At any point the virtual machine is executing the code of a
single method, and the pc register contains the address of the next
bytecode to be executed.
[0270] Each method has memory space allocated for it to hold:
[0271] a set of local variables, referenced by a vars register;
[0272] an operand stack, referenced by an optop register; and
[0273] a execution environment structure, referenced by a frame
register.
[0274] All of this space can be allocated at once, since the size
of the local variables and operand stack are known at compile time,
and the size of the execution environment structure is well-known
to the interpreter.
[0275] All of these registers are 32 bits wide.
[0276] 1.3 Local Variables
[0277] Each JAVA method uses a fixed-sized set of local variables.
They are addressed as word offsets from the vars register. Local
variables are all. 32 bits wide.
[0278] Long integers and double precision floats are considered to
take up two local variables but are addressed by the index of the
first local variable. (For example, a local variable with index
containing a double precision float actually occupies storage at
indices n and n+1.) The virtual machine specifcation does not
require 64-bit values in local variables to be 64-bit aligned.
Implementors are free to decide the appropriate way to divide long
integers and double precision floats into two words.
[0279] Instructions are provided to load the values of local
variables onto the operand stack and store values from the operand
stack into local variables.
[0280] 1.4 The Operand Stack
[0281] The machine instructions all take operands from an operand
stack, operate on them, and return results to the stack. We chose a
stack organization so that it would be easy to emulate the machine
efficiently on machines with few or irregular registers such as the
Intel 486 microprocessor.
[0282] The operand stack is 32 bits wide. It is used to pass
parameters to methods and receive method results, as well as to
supply parameters for operations and save operation results.
[0283] For example, execution of instruction iadd adds two integers
together. It expects that the two integers are the top two words on
the operand stack, and were pushed there by previous instructions.
Both integers are popped from the stack, added, and their sum
pushed back onto the operand stack. Subcomputations may be nested
on the operand stack, and result in a single operand that can be
used by the nesting computation.
[0284] Each primitive data type has specialized instructions that
know how to operate on operands of that type. Each operand requires
a single location on the stack, except for long and double
operands, which require two locations.
[0285] Operands must be operated on by operators appropriate to
their type. It is illegal, for example, to push two integers and
then treat them as a long. This restriction is enforced, in the Sun
implementation, by the bytecode verifier. However, a small number
of operations (the dup opcodes and swap) operate on runtime data
areas as raw values of a given width without regard to type.
[0286] In our description of the virtual machine instructions
below, the effect of an instruction's execution on the operand
stack is represented textually, with the stack growing from left to
right, and each 32-bit word separately represented. Thus:
[0287] Stack: . . . , value1, value2 . . . , value3
[0288] shows an operation that begins by having value2 on top of
the stack with value1 just beneath it. As a result of the execution
of the instruction, value1 and value2 are popped from the stack and
replaced by value3, which has been calculated by the instruction.
The remainder of the stack, represented by an ellipsis, is
unaffected by the instruction's execution.
[0289] The types long and double take two 32-bit words on the
operand stack:
[0290] Stack: . . . . . . , value-word1, value-word2
[0291] This specification does not say how the two words are
selected from the 64-bit long or double value; it is only necessary
that a particular implementation be internally consistent.
[0292] 1.5 Execution Environment
[0293] The information contained in the execution environment is
used to do dynamic linking, normal method returns, and exception
propagation.
[0294] 1.5.1 Dynamic Linking
[0295] The execution environment contains references to the
interpreter symbol table for the current method and current class,
in support of dynamic linking of the method code. The class file
code for a method refers to methods to be called and variables to
be accessed symbolically. Dynamic linking translates these symbolic
method calls into actual method calls, loading classes as necessary
to resolve as-yet-undefined symbols, and translates variable
accesses into appropriate offsets in storage structures associated
with the runtime location of these variables.
[0296] This late binding of the methods and variables makes changes
in other classes that a method uses less likely to break this
code.
[0297] 1.5.2 Normal Method Returns
[0298] If execution of the current method completes normally, then
a value is returned to the calling method. This occurs when the
calling method executes a return instruction appropriate to the
return type.
[0299] The execution environment is used in this case to restore
the registers of the caller, with the program counter of the caller
appropriately incremented to skip the method call instruction.
Execution then continues in the calling method's execution
environment.
[0300] 1.5.3 Exception and Error Propagation
[0301] An exceptional condition, known in JAVA as an Error or
Exception, which are subclasses of Throwable, may arise in a
program because of:
[0302] a dynamic linkage failure, such as a failure to find a
needed class file;
[0303] a run-time error, such as a reference through a null
pointer;
[0304] an asynchronous event, such as is thrown by Thread.stop,
from another thread; and
[0305] the program using a throw statement.
[0306] When an exception occurs:
[0307] A list of catch clauses associated with the current method
is examined. Each catch clause describes the instruction range for
which it is active, describes the type of exception that it is to
handle, and has the address of the code to handle it.
[0308] An exception matches a catch clause if the instruction that
caused the exception is in the appropriate instruction range, and
the exception type is a subtype of the type of exception that the
catch clause handles. If a matching catch clause is found, the
system branches to the specified handler. If no handler is found,
the process is repeated until all the nested catch clauses of the
current method have been exhausted.
[0309] The order of the catch clauses in the list is important. The
virtual machine execution continues at the first matching catch
clause. Because JAVA code is structured, it is always possible to
sort all the exception handlers for one method into a single list
that, for any possible program counter value, can be searched in
linear order to find the proper (innermost containing applicable)
exception handler for an exception occurring at that program
counter value.
[0310] If there is no matching catch clause then the current method
is said to have as its outcome the uncaught exception. The
execution state of the method that called this method is restored
from the execution environment, and the propagation of the
exception continues, as though the exception had just occurred in
this caller.
[0311] 1.5.4 Additional Information
[0312] The execution environment may be extended with additional
implementation-specified information, such as debugging
information.
[0313] 1.6 Garbage Collected Heap
[0314] The JAVA heap is the runtime data area from which class
instances (objects) are allocated. The JAVA language is designed to
be garbage collected--it does not give the programmer the ability
to deallocate objects explicitly. The JAVA language does not
presuppose any particular kind of garbage collection; various
algorithms may be used depending on system requirements.
[0315] 1.7 Method Area
[0316] The method area is analogous to the store for compiled code
in conventional languages or the text segment in a UNIX process. It
stores method code (compiled JAVA code) and symbol tables. In the
current JAVA implementation, method code is not part of the
garbage-collected heap, although this is planned for a future
release.
[0317] 1.8 The JAVA Instruction Set
[0318] An instruction in the JAVA instruction set consists of a
one-byte opcode specifying the operation to be performed, and zero
or more operands supplying parameters or data that will be used by
the operation. Many instructions have no operands and consist only
of an opcode.
[0319] The inner loop of the virtual machine execution is
effectively:
2 do { fetch an opcode byte execute an action depending on the
value of the opcode } while (there is more to do);
[0320] The number and size of the additional operands is determined
by the opcode. If an additional operand is more than one byte in
size, then it is stored in big-endian order--high order byte first.
For example, a 16-bit parameter is stored as two bytes whose value
is:
first_byte*256+second_byte
[0321] The bytecode instruction stream is only byte-aligned, with
the exception being the tableswitch and lookupswitch instructions,
which force alignment to a 4-byte boundary within their
instructions.
[0322] These decisions keep the virtual machine code for a compiled
JAVA program compact and reflect a conscious bias in favor of
compactness at some possible cost in performance.
[0323] 1.9 Limitations
[0324] The per-class constant pool has a maximum of 65535 entries.
This acts as an internal limit on the total complexity of a single
class.
[0325] The amount of code per method is limited to 65535 bytes by
the sizes of the indices in the code in the exception table, the
line number table, and the local variable table.
[0326] Besides this limit, the only other limitation of note is
that the number of words of arguments in a method call is limited
to 255.
[0327] 2. Class File Format
[0328] This chapter documents the JAVA class (.class) file
format.
[0329] Each class file contains the compiled version of either a
JAVA class or a JAVA interface. Compliant JAVA interpreters must be
capable of dealing with all class files that conform to the
following specification.
[0330] A JAVA class file consists of a stream of 8-bit bytes. All
16-bit and 32-bit quantities are constructed by reading in two or
four 8-bit bytes, respectively. The bytes are joined together in
network (big-endian) order, where the high bytes come first. This
format is supported by the JAVA JAVA.io.DataInput and
JAVA.io.DataOutput interfaces, and classes such as
JAVA.io.DataInputStream and JAVA.io.DataOutputStream.
[0331] The class file format is described here using a structure
notation. Successive fields in the structure appear in the external
representation without padding or alignment. Variable size arrays,
often of variable sized elements, are called tables and are
commonplace in these structures.
[0332] The types u1, u2, and u4 mean an unsigned one-, two-, or
four-byte quantity, respectively, which are read by method such as
readUnsignedByte, readUnsignedShort and readint of the
JAVA.io.DataInput interface.
[0333] 2.1 Format
[0334] The following pseudo-structure gives a top-level description
of the format of a class file:
3 ClassFile { u4 magic; u2 minor_version; u2 major_version; u2
constant_pool_count; cp_info constant_pool[constant_pool_count -
1]; u2 access_flags; u2 this_class; u2 super_class; u2
interfaces_count; u2 interfaces[interfaces_count]; u2 fields_count;
field_info fields[fields_count]; u2 methods_count; method_info
methods[methods_count]; u2 attributes_count; attribute_info
attributes[attribute_count]; }
[0335] magic
[0336] This field must have the value 0xCAFEBABE.
[0337] minor_version, major_version
[0338] These fields contain the version number of the JAVA compiler
that produced this class file. An implementation of the virtual
machine will normally support some range of minor version numbers
0-n of a particular major version number. If the minor version
number is incremented the new code won't run on the old virtual
machines, but it is possible to make a new virtual machine which
can run versions up to n+1.
[0339] A change of the major version number indicates a major
incompatible change, one that requires a different virtual machine
that may not support the old major version in any way.
[0340] The current major version number is 45; the current minor
version number is 3.
[0341] constant_pool_count
[0342] This field indicates the number of entries in the constant
pool in the class file.
[0343] constant_pool
[0344] The constant pool is a table of values. These values are the
various string constants, class names, field names, and others that
are referred to by the class structure or by the code.
[0345] constant_pool[0] is always unused by the compiler, and may
be used by an implementation for any purpose.
[0346] Each of the constant_pool entries 1 through
constant_pool_count-1 is a variable-length entry, whose format is
given by the first "tag" byte, as described in section 2.3.
[0347] access_flags
[0348] This field contains a mask of up to sixteen modifiers used
with class, method, and field declarations. The same encoding is
used on similar fields in field_info and method info as described
below. Here is the encoding:
4 Flag Name Value Meaning Used By ACC_PUBLIC 0x0001 Visible to
everyone Class, Method, Variable ACC_PRIVATE 0x0002 Visible only to
the Method, defining class Variable ACC_PROTECTED 0x0004 Visible to
Method, subclasses Variable ACC_STATIC 0x0008 Variable or method
Method, is static Variable ACC_FINAL 0x0010 No further sub- Class,
classing, over- Method, riding, or assign- Variable ment after ini-
tialization ACC_SYNCHRONIZED 0x0020 Wrap use in monitor Method lock
ACC_VOLATILE 0x0040 Can't cache Variable ACC_TRANSIENT 0x0080 Not
to be written Variable or read by a per- sistent object manager
ACC_NATIVE 0x0100 Implemented in a Method language other than JAVA
ACC_INTERFACE 0x0200 Is an interface Class ACC_ABSTRACT 0x0400 No
body provided Class, Method
[0349] this_class
[0350] This field is an index into the constant pool; constant_pool
[this_class] must be a CONSTANT_class.
[0351] super_class
[0352] This field is an index into the constant pool. If the value
of super_class is nonzero, then constant_pool [super_class] must be
a class, and gives the index of this class's superclass in the
constant pool.
[0353] If the value of super_class is zero, then the class being
defined must be JAVA.lang.Object, and it has no superclass.
[0354] interfaces_count
[0355] This field gives the number of interfaces that this class
implements.
[0356] interfaces
[0357] Each value in this table is an index into the constant pool.
If a table value is nonzero (interfaces[i] !=0, where
0<=i<interfaces_co- unt), then constant_pool [interfaces[i]]
must be an interface that this class implements.
[0358] fields_count This field gives the number of instance
variables, both static and dynamic, defined by this class. The
fields table includes only those variables that are defined
explicitly by this class. It does not include those instance
variables that are accessible from this class but are inherited
from superclasses.
[0359] fields
[0360] Each value in this table is a more complete description of a
field in the class. See section 2.4 for more information on the
field_info structure.
[0361] methods_count
[0362] This field indicates the number of methods, both static and
dynamic, defined by this class. This table only includes those
methods that are explicitly defined by this class. It does not
include inherited methods.
[0363] methods
[0364] Each value in this table is a more complete description of a
method in the class. See section 2.5 for more information on the
method_info structure.
[0365] attributes_count
[0366] This field indicates the number of additional attributes
about this class.
[0367] attributes
[0368] A class can have any number of optional attributes
associated with it. Currently, the only class attribute recognized
is the "SourceFile" attribute, which indicates the name of the
source file from which this class file was compiled. See section
2.6 for more information on the attribute_info structure.
[0369] 2.2 Signatures
[0370] A signature is a string representing a type of a method,
field or array.
[0371] The field signature represents the value of an argument to a
function or the value of a variable. It is a series of bytes
generated by the following grammar:
5 <field_signature> ::= <field_type> <field_type>
::=<base_type>.vertline.<object_type>.vert- line.
<array_type> <base_type> ::=
B.vertline.C.vertline.D.vertline.F.vertline.I.vertline.J.vertline.S.vertl-
ine.Z <object_type> ::= L<fullclassname>;
<array_type> ::=[<optional_size><field_type>
<optional_size> ::= [0-9]
[0372] The meaning of the base types is as follows:
6 B byte signed byte C char character D double double precision
IEEE float F float single precision IEEE float I int integer J long
long integer L<fullclassname>; . . . an object of the given
class S short signed short Z boolean true or false [<field
sig> . . . array
[0373] A return-type signature represents the return value from a
method. It is a series of bytes in the following grammar:
[0374] <return_signature>::=<field_type>.vertline.V
[0375] The character V indicates that the method returns no value.
Otherwise, the signature indicates the type of the return
value.
[0376] An argument signature represents an argument passed to a
method:
[0377] <argument_signature>::=<field_type>
[0378] A method signature represents the arguments that the method
expects, and the value that it returns.
7 <method_signature> ::= (<arguments_signature&- gt;)
<return_signature> <arguments_signature> ::=
<argument_signature>*
[0379] 2.3 Constant Pool
[0380] Each item in the constant pool begins with a 1-byte tag:.
The table below lists the valid tags and their values.
8 Constant Type Value CONSTANT_Class 7 CONSTANT_Fieldref 9
CONSTANT_Methodref 10 CONSTANT_InterfaceMethodref 11
CONSTANT_String 8 CONSTANT_Integer 3 CONSTANT_Float 4 CONSTANT_Long
5 CONSTANT_Double 6 CONSTANT_NameAndType 12 CONSTANT_Utf8 1
CONSTANT_Unicode 2
[0381] Each tag byte is then followed by one or more bytes giving
more information about the specific constant.
[0382] 2.3.1 CONSTANT_Class
[0383] CONSTANT_Class is used to represent a class or an
interface.
9 CONSTANT_Class_info { u1 tag; u2 name_index; }
[0384] tag
[0385] The tag will have the value CONSTANT_Class
[0386] name_index
[0387] constant_pool[name_index] is a CONSTANT_Utf8
[0388] giving the string name of the class.
[0389] Because arrays are objects, the opcodes anewarray and
multianewarray can reference array "classes" via CONSTANT_Class
items in the constant pool. In this case, the name of the class is
its signature. For example, the class name for
[0390] int[ ][ ]
[0391] is
[0392] [[I
[0393] The class name for
[0394] Thread[ ]
[0395] is
[0396] "[LJAVA.lang.Thread;"
[0397] 2.3.2 CONSTANT_{Fieldref, Methodref, InterfaceMethodref}
[0398] Fields, methods, and interface methods are represented by
similar structures.
10 CONSTANT_Fieldref_info { u1 tag; u2 class_index; u2
name_and_type_index; } CONSTANT_Methodref_info { u1 tag; u2
class_index; u2 name_and_type_index; }
CONSTANT_InterfaceMethodref_inf- o { u1 tag; u2 class_index; u2
name_and_type_index; }
[0399] tag
[0400] The tag will have the value CONSTANT_Fieldref,
CONSTANT_Methodref, or CONSTANT_InterfaceMethodref.
[0401] class_index
[0402] constant_pool[class_index] will be an entry of type
CONSTANT_Class giving the name of the class or interface containing
the field or method.
[0403] For CONSTANT Fieldref and CONSTANT_Methodref, the
CONSTANT_Class item must be an actual class. For
CONSTANT_InterfaceMethodref, the item must be an interface which
purports to implement the given method.
[0404] name_and_type_index
[0405] constant_pool [name_and_type_index] will be an entry of type
CONSTANT_NameAndType. This constant pool entry indicates the name
and signature of the field or method.
[0406] 2.3.3 CONSTANT_String
[0407] CONSTANT_String is used to represent constant objects of the
built-in type String.
11 CONSTANT_String_info { u1 tag; u2 string_index; }
[0408] tag
[0409] The tag will have the value CONSTANT_String
[0410] string_index
[0411] constant_pool [string_index] is a CONSTANT_Utf8 string
giving the value to which the String object is initialized.
[0412] 2.3.4 CONSTANT_Integer and CONSTANT_Float
[0413] CONSTANT_Integer and CONSTANT_Float represent four-byte
constants.
12 CONSTANT_Integer_info { u1 tag; u4 bytes; } CONSTANT_Float_info
{ u1 tag; u4 bytes; }
[0414] tag
[0415] The tag will have the value CONSTANT_Integer or
CONSTANT_Float
[0416] bytes
[0417] For integers, the four bytes are the integer value. For
floats, they are the IEEE 754 standard representation of the
floating point value. These bytes are in network (high byte first)
order.
[0418] 2.3.5 CONSTANT_Long and CONSTANT_Double
[0419] CONSTANT_Long and CONSTANT_Double represent eight-byte
constants.
13 CONSTANT_Long_info { u1 tag; u4 high_bytes; u4 low_bytes; }
CONSTANT_Double_info { u1 tag; u4 high_bytes; u4 low_bytes; }
[0420] All eight-byte constants take up two spots in the constant
pool. If this is the n.sup.th item in the constant pool, then the
next item will be numbered n+2.
[0421] tag
[0422] The tag will have the value CONSTANT_Long or
CONSTANT_Double.
[0423] high_bytes, low_bytes
[0424] For CONSTANT_Long, the 64-bit value is
(high_bytes<<32)+low bytes.
[0425] For CONSTANT_Double, the 64-bit value; high bytes and
low_bytes together represent the standard IEEE 754 representation
of the double-precision floating point number.
[0426] 2.3.6 CONSTANT_NameAndType
[0427] CONSTANT_NameAndType is used to represent a field or method,
without indicating which class it belongs to.
14 CONSTANT_NameAndType_info { u1 tag; u2 name_index; u2
signature_index; }
[0428] tag
[0429] The tag will have the valueCONSTANT_NameAndType.
[0430] name_index
[0431] constant_pool [name_index] is a CONSTANT_Utf8 string giving
the name of the field or method.
[0432] signature_index
[0433] constant_pool [signature_index] is a CONSTANT_Utf8 string
giving the signature of the field or method.
[0434] 2.3.7 CONSTANT_Utf8 and CONSTANT_Unicode
[0435] CONSTANT_Utf8 and CONSTANT_Unicode are used to represent
constant string values.
[0436] CONSTANT_Utf8 strings are "encoded" so that strings
containing only non-null ASCII characters, can be represented using
only one byte per character, but characters of up to 16 bits can be
represented:
[0437] All characters in the range 0x0001 to 0x007F are represented
by a single byte: 1
[0438] The null character (0x0000) and characters in the range
0x0080 to 0x07FF are represented by a pair of two bytes: 2
[0439] Characters in the range 0x0800 to 0XFFFF are represented by
three bytes: 3
[0440] There are two differences between this format and the
"standard" UTF-8 format. First, the null byte (0.times.00) is
encoded in two-byte format rather than one-byte, so that our
strings never have embedded nulls. Second, only the one-byte,
two-byte, and three-byte formats are used. We do not recognize the
longer formats.
15 CONSTANT_Utf8_info { u1 tag; u2 length; u1 bytes[length]; }
CONSTANT_Unicode_info { u1 tag; u2 length; u2 bytes [length]; }
[0441] tag
[0442] The tag will have the value CONSTANT_Utf8 or CONSTANT
Unicode.
[0443] length
[0444] The number of bytes in the string. These strings are not
null terminated.
[0445] bytes
[0446] The actual bytes of the string.
[0447] 2.4 Fields
[0448] The information for each field immediately follows the
field_count field in the class file. Each field is described by a
variable length field_info structure. The format of this structure
is as follows:
16 field_info { u2 access_flags; u2 name_index; u2 signature_index;
u2 attributes_count; attribute_info attributes[attribute_count];
}
[0449] access_flags
[0450] This is a set of sixteen flags used by classes, methods, and
fields to describe various properties and how they many be accessed
by methods in other classes. See the table "Access Flags" which
indicates the meaning of the bits in this field.
[0451] The possible fields that can be set for a field are
ACC_PUBLIC, ACC_PRIVATE, ACC_PROTECTED, ACC_STATIC, ACC_FINAL,
ACC_VOLATILE, and ACC_TRANSIENT.
[0452] At most one of ACC_PUBLIC, ACC_PROTECTED, and ACC_PRIVATE
can be set for any method.
[0453] name_index
[0454] constant_pool [name_index] is a CONSTANT_Utf8 string which
is the name of the field.
[0455] signature_index
[0456] constant_pool [signature_index] is a CONSTANT_Utf8 string
which is the signature of the field. See the section "Signatures'
for more information on signatures.
[0457] attributes_count
[0458] This value indicates the number of additional attributes
about this field.
[0459] attributes
[0460] A field can have any number of optional attributes
associated with it. Currently, the only field attribute recognized
is the "ConstantValue" attribute, which indicates that this field
is a static numeric constant, and indicates the constant value of
that field.
[0461] Any other attributes are skipped.
[0462] 2.5 Methods
[0463] The information for each method immediately follows the
method_count field in the class file. Each method is described by a
variable length method_info structure. The structure has the
following format:
17 method_info { u2 access_flags; u2 name_index; u2
signature_index; u2 attributes_count; attribute_info attributes
[attribute_count]; }
[0464] access_flags
[0465] This is a set of sixteen flags used by classes, methods, and
fields to describe various properties and how they many be accessed
by methods in other classes. See the table "Access Flags" which
gives the various bits in this field.
[0466] The possible fields that can be set for a method are
ACC_PUBLIC, ACC_PRIVATE, ACC_PROTECTED, ACC_STATIC, ACC_FINAL,
ACC_SYNCHRONIZED, ACC_NATIVE, and ACC_ABSTRACT.
[0467] At most one of ACC_PUBLIC, ACC_PROTECTED, and ACC_PRIVATE
can be set for any method.
[0468] name_index
[0469] constant_pool[name_index] is a CONSTANT_Utf8 string giving
the name of the method.
[0470] signature_index
[0471] constant_pool [signature_index] is a CONSTANT_Utf8 string
giving the signature of the field. See the section "Signatures" for
more information on signatures.
[0472] attributes_count
[0473] This value indicates the number of additional attributes
about this field.
[0474] attributes
[0475] A field can have any number of optional attributes
associated with it. Each attribute has a name, and other additional
information. Currently, the only field attributes recognized are
the "Code" and "Exceptions" attributes, which describe the
bytecodes that are executed to perform this method, and the JAVA
Exceptions which are declared to result from the execution of the
method, respectively.
[0476] Any other attributes are skipped.
[0477] 2.6 Attributes
[0478] Attributes are used at several different places in the class
format. All attributes have the following format:
18 GenericAttribute_info { u2 attribute_name; u4 attribute_length;
u1 info[attribute_length]; }
[0479] The attribute_name is a 16-bit index into the class's
constant_pool; the value of constant_pool [attribute_name] is a
CONSTANT_Utf8 string giving the name of the attribute. The field
attribute_length indicates the length of the subsequent information
in bytes. This length does not include the six bytes of the
attribute_name and attribute length.
[0480] In the following text, whenever we allow attributes, we give
the name of the attributes that are currently understood. In the
future, more attributes will be added. Class file readers are
expected to skip over and ignore the information in any attribute
they do not understand.
[0481] 2.6.1 SourceFile
[0482] The "SourceFile" attribute has the following format:
19 SourceFile_attribute { u2 attribute_name_index; u4
attribute_length; u2 sourcefile_index; }
[0483] attribute_name_index
[0484] constant_pool [attribute_name_index] is the CONSTANT_Utf8
string "SourceFile".
[0485] attribute_length
[0486] The length of a SourceFile_attribute must be 2.
[0487] sourcefile_index
[0488] constant_pool [sourcefile_index] is a CONSTANT_Utf8 string
giving the source file from which this class file was compiled.
[0489] 2.6.2 ConstantValue
[0490] The "ConstantValue" attribute has the following format:
20 ConstantValue_attribute { u2 attribute_name_index; u4
attribute_length; u2 constantvalue_index; }
[0491] attribute_name_index
[0492] constant_pool [attribute_name_index] is the CONSTANT_Utf8
string "ConstantValue".
[0493] attribute_length
[0494] The length of a ConstantValue_attribute must be 2.
[0495] constantvalue_index
[0496] constant_pool [constantvalue_index] gives the constant value
for this field.
[0497] The constant pool entry must be of a type appropriate to the
field, as shown by the following table:
21 long CONSTANT_Long float CONSTANT_Float double CONSTANT_Double
int, short, char, byte, boolean CONSTANT_Integer
[0498] 2.6.3 Code
[0499] The "Code" attribute has the following format:
22 Code_attribute { u2 attribute_name_index; u4 attribute_length;
u2 max_stack; u2 max_locals; u4 code_length; u1 code[code_length];
u2 exception_table_length; { u2 start_pc; u2 end_pc; u2 handler_pc;
u2 catch_type; } exception_table[exception- _table_length]; u2
attributes_count; attribute_info attributes [attribute_count];
}
[0500] attribute_name_index
[0501] constant_pool [attribute_name_index] is the CONSTANT_Utf8
string "Code".
[0502] attribute_length
[0503] This field indicates the total length of the "Code"
attribute, excluding the initial six bytes.
[0504] max_stack
[0505] Maximum number of entries on the operand stack that will be
used during execution of this method. See the other chapters in
this spec for more information on the operand stack.
[0506] max_locals
[0507] Number of local variable slots used by this method. See the
other chapters in this spec for more information on the local
variables.
[0508] code_length
[0509] The number of bytes in the virtual machine code for this
method.
[0510] code
[0511] These are the actual bytes of the virtual machine code that
implement the method. When read into memory, if the first byte of
code is aligned onto a multiple-of-four boundary the tableswitch
and tablelookup opcode entries will be aligned; see their
description for more information on alignment requirements.
[0512] exception_table_length
[0513] The number of entries in the following exception table.
[0514] exception_table
[0515] Each entry in the exception table describes one exception
handler in the code.
[0516] start_pc, end_pc
[0517] The two fieldsstart_pc and end_pc indicate the ranges in the
code at which the exception handler is active. The values of both
fields are offsets from the start of the code.start_pc is
inclusive.end_pc is exclusive.
[0518] handler_pc
[0519] This field indicates the starting address of the exception
handler. The value of the field is an offset from the start of the
code.
[0520] catch_type
[0521] If catch_type is nonzero, then constant_pool [catch_type]
will be the class of exceptions that this exception handler is
designated to catch. This exception handler should only be called
if the thrown exception is an instance of the given class.
[0522] If catch_type is zero, this exception handler should be
called for all exceptions.
[0523] attributes_count
[0524] This field indicates the number of additional attributes
about code. The "Code" attribute can itself have attributes.
[0525] attributes
[0526] A "Code" attribute can have any number of optional
attributes associated with it. Each attribute has a name, and other
additional information. Currently, the only code attributes
[0527] defined are the "LineNumberTable" and "LocalVariableTable,"
both of which contain debugging information.
[0528] 2.6.4 Exceptions Table
[0529] This table is used by compilers which indicate which
Exceptions a method is declared to throw:
23 Exceptions_attribute { u2 attribute_name_index; u4
attribute_length; u2 number_of_exceptions; u2 exception_index_table
[number_of_ex- ceptions]; }
[0530] attribute_name_index
[0531] constant_pool [attribute_name_index] will be the
CONSTANT_Utf8 string "Exceptions".
[0532] attribute_length
[0533] This field indicates the total length of the
Exceptions_attribute, excluding the initial six bytes.
[0534] number_of_exceptions
[0535] This field indicates the number of entries in the following
exception index_table.
[0536] exception_index_table
[0537] Each value in this table is an index into the constant pool.
For each table element (exception_index_table [i] !=0, where
0<=i <number_of_exceptions), then constant_pool
[exception_index+table [i]] is a Exception that this class is
declared to throw.
[0538] 2.6.5 LineNumberTable
[0539] This attribute is used by debuggers and the exception
handler to determine which part of the virtual machine code
corresponds to a given location in the source. The
LineNumberTable_attribute has the following format.:
24 LineNumberTable_attribute { u2 attribute_name_index; u4
attribute_length; u2 line_number_table_length; { u2 start_pc; u2
line_number; } line_number_table[line.sub.-- number_table_length];
}
[0540] attribute_name_index
[0541] constant_pool [attribute_name_index] will be the
CONSTANT_Utf8 string "LineNumberTable".
[0542] attribute_length
[0543] This field indicates the total length of the
LineNumberTable_attribute, excluding the initial six bytes.
[0544] line_number_table_length
[0545] This field indicates the number of entries in the following
line number table.
[0546] line_number_table
[0547] Each entry in the line number table indicates that the line
number in the source file changes at a given point in the code.
[0548] start_pc
[0549] This field indicates the place in the code at which the code
for a new line in the source begins. source_pc <<SHOULD THAT
BEstart_pc?>> is an offset from the beginning of the
code.
[0550] line_number
[0551] The line number that begins at the given location in the
file.
[0552] 2.6.6 LocalVariableTable
[0553] This attribute is used by debuggers to determine the value
of a given local variable during the dynamic execution of a method.
The format of the LocalVariableTable_attribute is as follows:
25 LocalVariableTable_attribute { u2 attribute_name_index; u4
attribute_length; u2 local_variable_table_length; { u2 start_pc; u2
length; u2 name_index; u2 signature_index; u2 slot; }
local_variable_table[local.sub.-- variable_table_length]; }
[0554] attribute_name_index
[0555] constant_pool [attribute_name_index] will be the
CONSTANT_Utf8 string "LocalVariableTable".
[0556] attribute_length
[0557] This field indicates the total length of the
LineNumberTable_attribute, excluding the initial six bytes.
[0558] local_variable_table_length
[0559] This field indicates the number of entries in the following
local variable table.
[0560] local_variable_table
[0561] Each entry in the local variable table indicates a code
range during which a local variable has a value. It also indicates
where on the stack the value of that variable can be found.
[0562] start_pc, length
[0563] The given local variable will have a value at the code
between start_pc andstart_pc+length. The two values are both
offsets from the beginning of the code.
[0564] name_index, signature_index
[0565] constant_pool[name_index] and constant_pool
[signature_index] are CONSTANT_Utf8 strings giving the name and
signature of the local variable.
[0566] slot
[0567] The given variable will be the slot.sup.th local variable in
the method's frame.
[0568] 3. The Virtual Machine Instruction Set
[0569] 3.1 Format for the Instructions
[0570] JAVA Virtual Machine instructions are represented in this
document by an entry of the following form.
[0571] instruction name
[0572] Short description of the Instruction
[0573] Syntax: 4
[0574] Stack: . . . , value1, value2 . . . , value3
[0575] A longer description that explains the functions of the
instruction and indicates any exceptions that might be thrown
during execution.
[0576] Each line in the syntax table represents a single 8-bit
byte.
[0577] Operations of the JAVA Virtual Machine most often take their
operands from the stack and put their results back on the stack. As
a convention, the descriptions do not usually mention when the
stack is the source or destination of an operation, but will always
mention when it is not. For instance, instruction iload has the
short description "Load integer from local variable." Implicitly,
the integer is loaded onto the stack. Instruction iadd is described
as "Integer add"; both its source and destination are the
stack.
[0578] Instructions that do not affect the control flow of a
computation may be assumed to always advance the virtual machine
program counter to the opcode of the following instruction. Only
instructions that do affect control flow will explicitly mention
the effect they have on the program counter.
[0579] 3.2 Pushing Constants onto the Stack
[0580] bipush
[0581] Push One-Byte Signed Integer
[0582] Syntax: 5
[0583] Stack: . . . => . . . , value
[0584] byte1 is interpreted as a signed 8-bit value. This value is
expanded to an integer and pushed onto the operand stack.
[0585] sipush
[0586] Push Two-Byte Signed Integer
[0587] Syntax: 6
[0588] Stack: . . . => . . . , item
[0589] byte1 and byte2 are assembled into a signed 16-bit value.
This value is expanded to an integer and pushed onto the operand
stack.
[0590] ldc1
[0591] Push Item from Constant Pool
[0592] Syntax: 7
[0593] Stack: . . . => . . . , item
[0594] indexbyte1 is used as an unsigned 8-bit index into the
constant pool of the current class. The item at that index is
resolved and pushed onto the stack. If a String is being pushed and
there isn't enough memory to allocate space for it then an
OutOfMemoryError is thrown.
[0595] Note: A String push results in a reference to an object.
[0596] ldc2
[0597] Push Item from Constant Pool
[0598] Syntax: 8
[0599] Stack: . . . => . . . , item
[0600] indexbyte1 and indexbyte2 are used to construct an unsigned
16-bit index into the constant pool of the current class. The item
at that index is resolved and pushed onto the stack. If a String is
being pushed and there isn't enough memory to allocate space for it
then an OutOfMemoryError is thrown.
[0601] Note: A String push results in a reference to an object.
[0602] ldc2w
[0603] Push Long or Double from Constant Pool
[0604] Syntax: 9
[0605] Stack: . . . =< . . . , constant-word1,
constant-word2
[0606] indexbyte1 and indexbyte2 are used to construct an unsigned
16-bit index into the constant pool of the current class. The
two-word constant that index is resolved and pushed onto the
stack.
[0607] aconst_null
[0608] Push Null Object Reference
[0609] Syntax: 10
[0610] Stack: . . . => . . . , null
[0611] Push the null object reference onto the stack.
[0612] iconst_m1
[0613] Push integer constant -1
[0614] Syntax: 11
[0615] Stack: . . . => . . . , 1
[0616] Push the integer -1 onto the stack.
[0617] iconst_<n>
[0618] Push Integer Constant
[0619] Syntax: 12
[0620] Stack: . . . => . . . , <n>
[0621] Forms: iconst.sub.--0=3, iconst.sub.--=4, iconst.sub.--2=5,
iconst.sub.--3=6, iconst.sub.--4=7, iconst.sub.--5=8
[0622] Push the integer <n> onto the stack.
[0623] const.sub.--<1>
[0624] Push Long Integer Constant
[0625] Syntax: 13
[0626] Stack: . . . => . . . <1>-word1, <1>-word2
Forms: lconst.sub.--0=9, lconst.sub.--1=10
[0627] Push the long integer <1> onto the stack.
[0628] fconst_<f>
[0629] Push Single Float
[0630] Syntax: 14
[0631] Stack: . . . => . . . , f>
[0632] Forms: fconst.sub.--0=11, fconst.sub.--1=12,
fconst.sub.--2=13
[0633] Push the single-precision floating point number <f>
onto the stack.
[0634] dconst_<d>
[0635] Push Double Float
[0636] Syntax: 15
[0637] Stack: . . . => . . . , <d>-word1,
<d>-word2
[0638] Forms: dconst.sub.--0=14, dconst.sub.--1=15
[0639] Push the double-precision floating point number <d>
onto the stack.
[0640] 3.3 Loading Local Variables onto the Stack
[0641] lload
[0642] Load Integer from Local Variable
[0643] Syntax: 16
[0644] Stack: . . . => . . . , value
[0645] The value of the local variable at vindex in the current
JAVA frame is pushed onto the operand stack.
[0646] iload_<n>
[0647] Load Integer from Local Variable
[0648] Syntax: 17
[0649] Stack: . . . => . . . , value
[0650] Forms: iload.sub.--0=26, iload.sub.--1=27, iload.sub.--2=28,
iload.sub.--3=29
[0651] The value of the local variable at <n> in the current
JAVA frame is pushed onto the operand stack.
[0652] This instruction is the same as iload with a vindex of
<n>, except that the operand <n> is implicit.
[0653] iload
[0654] Load Long Integer from Local Variable
[0655] Syntax: 18
[0656] Stack: . . . => . . . , value-word1, value-work2
[0657] The value of the local variables at vindex and vindex+1 in
the current JAVA frame is pushed onto the operand stack.
[0658] lload_<n>
[0659] Load Long Integer from Local Variable
[0660] Syntax: 19
[0661] Stack: . . . => . . . , value-word1, value-word2
[0662] Forms: lload.sub.--0=30, lload.sub.--1=31, lload.sub.--2=32,
lload.sub.--3=33
[0663] The value of the local variables at <n> and
<n>+1 in the current JAVA frame is pushed onto the operand
stack.
[0664] This instruction is the same as lload with a vindex of
<n>, except that the operand <n> is implicit.
[0665] fload
[0666] Load Single Float from Local Variable
[0667] Syntax: 20
[0668] Stack: . . . => . . . , value
[0669] The value of the local variable at vindex in the current
JAVA frame is pushed onto the opera and stack.
[0670] fload_<n>
[0671] Load Single Float from Local Variable
[0672] Syntax: 21
[0673] Stack: . . . => . . . , value
[0674] Forms: fload.sub.--0=34, fload.sub.--1=35, fload.sub.--2=36,
fload.sub.--3=37
[0675] The value of the local variable at <n> in the current
JAVA frame is pushed onto the operand stack.
[0676] This instruction is the same as fload with a vindex of
<n>, except that the operand <n> is implicit.
[0677] dload
[0678] Load Double Float from Local Variable
[0679] Syntax: 22
[0680] Stack: . . . => . . . , value-word1, value-word2
[0681] The value of the local variables at vindex and vindex+1 in
the current JAVA frame is pushed onto the operand stack.
[0682] dload_<n>
[0683] Load Double Float from Local Variable
[0684] Syntax: 23
[0685] Stack: . . . => . . . , value-word1, value-word2
[0686] Forms: dload.sub.--0=38, dload.sub.--1=39, dload.sub.--2=40,
dload.sub.--3=41
[0687] The value of the local variables at <n> and
<n>+1 in the current JAVA frame is pushed onto the operand
stack.
[0688] This instruction is the same as dload with a vindex of
<n>, except that the operand <n> is implicit.
[0689] aload
[0690] Load Object Reference from Local Variable
[0691] Syntax: 24
[0692] Stack: . . . => . . . , value
[0693] The value of the local variable at vindex in the current
JAVA frame is pushed onto the operand stack.
[0694] aload_<n>
[0695] Load Object Reference from Local Variable
[0696] Syntax: 25
[0697] Stack: . . . => . . . , value
[0698] Forms: aload.sub.--0=42, aload.sub.--1=43, aload.sub.--2=44,
aload.sub.--3=45
[0699] The value of the local variable at <n> in the current
JAVA frame is pushed onto the operand stack.
[0700] This instruction is the same as aload with a vindex of
<n>, except that the operand <n> is implicit.
[0701] 3.4 Storing Stack Values into Local Variables
[0702] istore
[0703] Store Integer into Local Variable
[0704] Syntax: 26
[0705] Stack: . . . , value=> . . .
[0706] value must be an integer. Local variable vindex in the
current JAVA frame is set to value.
[0707] istore_<n>
[0708] Store Integer into Local Variable
[0709] Syntax: 27
[0710] Stack: . . . , value=> . . .
[0711] Forms: istore.sub.--0=59, istore.sub.--1=60,
istore.sub.--2=61, istore.sub.--3=62
[0712] value must be an integer. Local variable <n> in the
current JAVA frame is set to value.
[0713] This instruction is the same as istore with a vindex of
<n>, except that the operand <n> is implicit.
[0714] lstore
[0715] Store Long Integer into Local Variable
[0716] Syntax: 28
[0717] Stack: . . . , value-word1, value-word2=> . . .
[0718] value must be a long integer. Local variables vindex+1 in
the current JAVA frame are set to value.
[0719] lstore_<n>
[0720] Store Long Integer into Local Variable
[0721] Syntax: 29
[0722] Stack: . . . , value-word1, value-word2=>
[0723] Forms: lstore.sub.--0=63, lstore.sub.--1=64,
lstore.sub.--2=65, lstore.sub.--3=66
[0724] value must be a long integer. Local variables <n>and
<n>+1 in the current JAVA frame are set to value.
[0725] This instruction is the same as lstore with a vindex of
<n>, except that the operand <n> is implicit.
[0726] fstore
[0727] Store Single Float into Local Variable
[0728] Syntax: 30
[0729] Stack: . . . , value=> . . .
[0730] value must be a single-precision floating point number.
Local variable vindex in the current JAVA frame is set to
value.
[0731] fstore_<n>
[0732] Store Single Float into Local Variable
[0733] Syntax: 31
[0734] Stack: . . . , value=> . . .
[0735] Forms: fstore.sub.--0=67, fstore.sub.--1=68,
fstore.sub.--2=69, fstore.sub.--3=70
[0736] value must be a single-precision floating point number.
Local variable <n> in the current JAVA frame is set to
value.
[0737] This instruction is the same as fstore with a vindex of
<n>, except that the operand <n> is implicit.
[0738] dstore
[0739] Store Double Float into Local Variable
[0740] Syntax: 32
[0741] Stack: . . . , value-word1, value-word2=> . . .
[0742] value must be a double-precision floating point number.
Local variables vindex and vindex+1 in the current JAVA frame are
set to value.
[0743] dstore_<n>
[0744] Store Double Float into Local Variable
[0745] Syntax: 33
[0746] Stack: . . . , value-word1, value-word2=> . . .
[0747] Forms: dstore.sub.--0=71, dstore.sub.--1=72,
dstore.sub.--2=73, dstore.sub.--3=74
[0748] value must be a double-precision floating point number.
Local variables <n> and <n>+1 in the current JAVA frame
are set to value.
[0749] This instruction is the same as dstore with a vindex of
<n>, except that the operand <n> is implicit.
[0750] astore
[0751] Store Object Reference into Local Variable
[0752] Syntax: 34
[0753] Stack: . . . , value=> . . .
[0754] value must be a return address or a reference to an object.
Local variable vindex in the current JAVA frame is set to
value.
[0755] astore_<n>
[0756] Store Object Reference into Local Variable
[0757] Syntax: 35
[0758] Stack: . . . , value=> . . .
[0759] Forms: astore.sub.--0=75, astore.sub.--1=76,
astore.sub.--2=77, astore.sub.--3=78
[0760] value must be a return address or a reference to an object.
Local variable <n> in the current JAVA frame is set to
value.
[0761] This instruction is the same as astore with a vindex of
<n>, except that the operand <n> is implicit.
[0762] iinc
[0763] Increment Local Variable by Constant
[0764] Syntax: 36
[0765] Stack: no change
[0766] Local variable vindex in the current JAVA frame must contain
an integer. Its value is incremented by the value const, where
const is treated as a signed 8-bit quantity.
[0767] 3.5 Wider Index for Loading, Storing and Incrementing
Wide
[0768] Wider Index for Accessing Local Variables in Load, Store and
Increment.
[0769] Syntax: 37
[0770] Stack: no change
[0771] This bytecode must precede one of the following bytecodes:
iload, lload, fload, dload, aload, istore, lstore, fstore, dstore,
astore, iinc. The vindex of the following bytecode and vindex2 from
this bytecode are assembled into an unsigned 16-bit index to a
local variable in the current JAVA frame. The following bytecode
operates as normal except for the use of this wider index.
[0772] 3.6 Managing Arrays
[0773] newarray
[0774] Allocate New Array
[0775] Syntax: 38
[0776] Stack: . . . , size=>result
[0777] size must be an integer. It represents the number of
elements in the new array.
[0778] atype is an internal code that indicates the type of array
to allocate. Possible values for atype are as follows:
26 T_BOOLEAN 4 T_CHAR 5 T_FLOAT 6 T_DOUBLE 7 T_BYTE 8 T_SHORT 9
T_INT 10 T_LONG 11
[0779] A new array of atype, capable of holding size elements, is
allocated, and result is a reference to this new object. Allocation
of an array large enough to contain size items of atype is
attempted. All elements of the array are initialized to zero.
[0780] If size is less than zero, a NegativeArraySizeException is
thrown. If there is not enough memory to allocate the array,
anOutOfMemoryError is thrown.
[0781] anewarray
[0782] Allocate New Array of References to Objects
[0783] Syntax: 39
[0784] Stack: . . . , size=>result
[0785] size must be an integer. It represents the number of
elements in the new array.
[0786] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The item at that index
is resolved. The resulting entry must be a class.
[0787] A new array of the indicated class type and capable of
holding size elements is allocated, and result is a reference to
this new object. Allocation of an array large enough to contain
size items of the given class type is attempted. All elements of
the array are initialized to null.
[0788] If size is less than zero, a NegativeArraySizeException is
thrown. If there is not enough memory to allocate the array, an
OutOfMemoryError is thrown.
[0789] anewarray is used to create a single dimension of an array
of object references. For example, to create new Thread[7]
[0790] the following code is used:
[0791] bipush 7
[0792] anewarray <Class "JAVA.lang.Thread">anewarray can also
be used to create the first dimension of a multi-dimensional array.
For example, the following array declaration:
[0793] new int[6][ ]
[0794] is created with the following code:
[0795] bipush 6
[0796] anewarray <Class "[I">
[0797] See CONSTANT_Class in the "Class File Format" chapter for
information on array class names.
[0798] multianewarray
[0799] Allocate New Multi-Dimensional Array
[0800] Syntax: 40
[0801] Stack: . . . , size1 size2 . . . sizen=>result
[0802] Each size must be an integer. Each represents the number of
elements in a dimension of the array.
[0803] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The item at that index
is resolved. The resulting entry must be an array class of one or
more dimensions.
[0804] dimensions has the following aspects:
[0805] It must be an integer .gtoreq.1.
[0806] It represents the number of dimensions being created. It
must be .ltoreq.the number of dimensions of the array class.
[0807] It represents the number of elements that are popped off the
stack. All must be integers greater than or equal to zero. These
are used as the sizes of the dimension.
[0808] For example, to create
[0809] new int[6][3][ ]
[0810] the following code is used:
[0811] bipush 6
[0812] bipush 3
[0813] multianewarray <Class "[[[I">2
[0814] If any of the size arguments on the stack is less than zero,
a NegativeArraySizeException is thrown. If there is not enough
memory to allocate the array, an OutOfMemoryError is thrown.
[0815] The result is a reference to the new array object.
[0816] Note: It is more efficient to use newarray or anewarray when
creating a single dimension.
[0817] See CONSTANT_Class in the "Class File Format" chapter for
information on array class names.
[0818] arraylength
[0819] Get Length of Array
[0820] Syntax: 41
[0821] Stack: . . . , objectref=> . . . , length
[0822] objectref must be a reference to an array object. The length
of the array is determined and replaces objectref on the top of the
stack.
[0823] If the objectref is null, a NullPointerException is
thrown.
[0824] iaload
[0825] Load Integer from Array
[0826] Syntax: 42
[0827] Stack: . . . , arrayref, index=> . . . , value
[0828] arrayref must be a reference to an array of integers.index
must be an integer. The integer value at position number index in
the array is retrieved and pushed onto the top of the stack.
[0829] If arrayref is null a NullPointerException is thrown. If
index is not within the bounds of the array an
ArrayIndexOutOfBoundsException is thrown.
[0830] laload
[0831] Load Long Integer from Array
[0832] Syntax: 43
[0833] Stack: . . . , arrayref, index=> . . . , value-word1,
[0834] value-word2
[0835] arrayref must be a reference to an array of long integers.
index must be an integer. The long integer value at position number
index in the array is retrieved and pushed onto the top of the
stack.
[0836] If arrayref is null a NullPointerException is thrown. If
index is not within the bounds of the array an
ArrayIndexOutOfBoundsException is thrown.
[0837] faload
[0838] Load Single Float from Array
[0839] Syntax: 44
[0840] Stack: . . . , arrayref, index=> . . . , value
[0841] arrayref must be a reference to an array of single-precision
floating point numbers. index must be an integer. The
single-precision floating point number value at position number
index in the array is retrieved and pushed onto the top of the
stack.
[0842] If arrayref is null a NullPointerException is thrown. If
index is not within the bounds of the array an
ArrayIndexOutOfBoundsException is thrown.
[0843] daload
[0844] Load Double Float from Array
[0845] Syntax: 45
[0846] Stack: . . . , arrayref, index=> . . . , value-word1,
value-word2
[0847] arrayref must be a reference to an array of double-precision
floating point numbers. index must be an integer. The
double-precision floating point number value at position number
index in the array is retrieved and pushed onto the top of the
stack.
[0848] If arrayref is null a NullPointerException is thrown. If
index is not within the bounds of the array an
ArrayIndexOutOfBoundsException is thrown.
[0849] aaload
[0850] Load Object Reference from Array
[0851] Syntax: 46
[0852] Stack: . . . , arrayref, index=> . . . , value
[0853] arrayref must be a reference to an array of references to
objects. index must be an integer. The object reference at position
number index in the array is retrieved and pushed onto the top of
the stack.
[0854] If arrayref is null a NullPointerException is thrown. If
index is not within the bounds of the array an
ArrayIndexOutOfBoundsException is thrown.
[0855] baload
[0856] Load Signed Byte from Array.
[0857] Syntax: 47
[0858] Stack: . . . , arrayref, index=> . . . , value
[0859] arrayref must be a reference to an array of signed bytes.
index must be an integer. The signed byte value at position number
index in the array is retrieved, expanded to an integer, and pushed
onto the top of the stack.
[0860] If arrayref is null a NullPointerException is thrown. If
index is not within the bounds of the array an
ArrayIndexOutOfBoundsException is thrown.
[0861] caload
[0862] Load Character from Array
[0863] Syntax: 48
[0864] Stack: . . . , arrayref, index=> . . . , value
[0865] arrayref must be a reference to an array of characters.
index must be an integer. The character value at position number
index in the array is retrieved, zero-extended to an integer, and
pushed onto the top of the stack.
[0866] If arrayref is null a NullPointerException is thrown. If
index is not within the bounds of the array an
ArrayIndexOutOfBoundsException is thrown.
[0867] saload
[0868] Load Short from Array
[0869] Syntax: 49
[0870] Stack: . . . , arrayref, index=> . . . , value
[0871] arrayref must be a reference to an array of short integers.
index must be an integer. The; signed short integer value at
position number index in the array is retrieved, expanded to an
integer, and pushed onto the top of the stack.
[0872] If arrayref is null, a NullPointerException is thrown. If
index is not within the bounds of the array an
ArrayIndexOutOfBoundsException is thrown.
[0873] iastore
[0874] Store into Integer Array
[0875] Syntax: 50
[0876] Stack: . . . , arrayref, index, value=> . . .
[0877] arrayref must be a reference to an array of integers, index
must be an integer, and value an integer. The integer value is
stored at position index in the array.
[0878] If arrayref is null, a NullPointerException is thrown. If
index is not within the bounds of the array an
ArrayIndexOutOfBoundsException is thrown.
[0879] lastore
[0880] Store into Long Integer Array
[0881] Syntax: 51
[0882] Stack: . . . ., arrayref, index, value-word1,
value-word2=> . . .
[0883] arrayref must be a reference to an array of long integers,
index must be an integer, and value a long integer. The long
integer value is stored at position index in the array.
[0884] If arrayref is null, a NullPointerException is thrown. If
index is not within the bounds of the array, an
ArrayIndexOutOfBoundsException is thrown.
[0885] fastore
[0886] Store into Single Float Array
[0887] Syntax: 52
[0888] Stack: . . . , arrayref, index, value=> . . .
[0889] arrayref must be an array of single-precision floating point
numbers, index must be an integer, and value a single-precision
floating point number. The single float value is stored at position
index in the array.
[0890] If arrayref is null, a NullPointerException is thrown. If
index is not within the bounds of the array an
ArrayIndexOutOfBoundsException is thrown.
[0891] dastore
[0892] Store into Double Float Array
[0893] Syntax: 53
[0894] Stack: . . . , arrayref, index, value-word1,
value-word2=> . . .
[0895] arrayref must be a reference to an array of double-precision
floating point numbers, index must be an integer, and value a
double-precision floating point number. The double float value is
stored at position index in the array.
[0896] If arrayref is null, a NullPointerException is thrown. If
index is not within the bounds of the array an
ArrayIndexOutOfBoundsException is thrown.
[0897] aastore
[0898] Store into Object Reference Array
[0899] Syntax: 54
[0900] Stack: . . . , arrayref, index, value=> . . .
[0901] arrayref must be a reference to an array of references to
objects, index must be an integer, and value a reference to an
object. The object reference value is stored at position index in
the array.
[0902] If arrayref is null, a NullPointerException is thrown. If
index is not within the bounds of the array, an
ArrayIndexOutOfBoundsException is thrown.
[0903] The actual type of value must be conformable with the actual
type of the elements of the array. For example, it is legal to
store an instance of class Thread in an array of class Object, but
not vice versa. An ArrayStoreException is thrown if an attempt is
made to store an incompatible object reference.
[0904] bastore
[0905] Store into Signed Byte Array
[0906] Syntax: 55
[0907] Stack: . . . , arrayref, index, value=> . . .
[0908] arrayref must be a reference to an array of signed bytes,
index must be an integer, and value an integer. The integer value
is stored at position index in the array. If value is too large to
be a signed byte, it is truncated.
[0909] If arrayref is null, a NullPointerException is thrown. If
index is not within the bounds of the array an
ArrayIndexOutOfBoundsException is thrown.
[0910] castore
[0911] Store into Character Array
[0912] Syntax: 56
[0913] Stack: . . . , arrayref, index, value=> . . .
[0914] arrayref must be an array of characters, index must be an
integer, and value an integer. The integer value is stored at
position index in the array. If value is too large to be a
character, it is truncated.
[0915] If arrayref is null, a NullPointerException is thrown. If
index is not within the bounds of [the array an
ArrayIndexOutOfBoundsException is thrown.
[0916] sastore
[0917] Store into Short Array
[0918] Syntax: 57
[0919] Stack: . . . , array, index, value=> . . .
[0920] arrayref must be an array of shorts, index must be an
integer, and value an integer. The integer value is stored at
position index in the array. If value is too large to be an short,
it is truncated.
[0921] If arrayref is null, a NuilPointerException is thrown. If
index is not within the bounds of the array an
ArrayIndexOutOfBoundsException is thrown.
[0922] 3.7 Stack Instructions
[0923] nop
[0924] Do Nothing
[0925] Syntax: 58
[0926] Stack: no change
[0927] Do nothing.
[0928] pop
[0929] Pop Top Stack Word
[0930] Syntax: 59
[0931] Stack: . . . , any=> . . .
[0932] Pop the top word from the stack.
[0933] pop2
[0934] Pop Top Two Stack Words
[0935] Syntax: 60
[0936] Stack: . . . , any2, any1=> . . .
[0937] Pop the top two words from the stack.
[0938] dup
[0939] Duplicate Top Stack Word
[0940] Syntax: 61
[0941] Stack: . . . , any=> . . . , any, any
[0942] Duplicate the top word on the stack.
[0943] dup2
[0944] Duplicate Top Two Stack Words
[0945] Syntax: 62
[0946] Stack: . . . , any2, any1=> . . . , any2, any1, any2,
any1
[0947] Duplicate the top two words on the stack.
[0948] dup_x1
[0949] Duplicate Top Stack Word and Put Two Down
[0950] Syntax: 63
[0951] Stack: . . . , any2, any1=> . . . , any1, any2, any1
[0952] Duplicate the top word on the stack and insert the copy two
words down in the stack.
[0953] dup2_x1
[0954] Duplicate Top Two Stack Words and Put Two Down
[0955] Syntax: 64
[0956] Stack: . . . , any3, any2, any1=> . . . , any2, any1,
any3, any2, any1
[0957] Duplicate the top two words on the stack and insert the
copies two words down in the stack.
[0958] dup.sub.--.times.2
[0959] Duplicate Top Stack Word and Put Three Down
[0960] Syntax: 65
[0961] Stack: . . . , any3, any2, any1=> . . . , any1, any3,
any2, any1
[0962] Duplicate the top word on the stack and insert the copy
three words down in the stack.
[0963] dup2_x2
[0964] Duplicate Top Two Stack Words and Put Three Down
[0965] Syntax: 66
[0966] Stack: . . . , any4, any3, any2, any1=> . . . , any2,
any1, any4, any3, any2, any1
[0967] Duplicate the top two words on the stack and insert the
copies three words down in the stack.
[0968] swap
[0969] Swap Top Two Stack Words
[0970] Syntax: 67
[0971] Stack: . . . , any2, any1=> . . . , any2, any1
[0972] Swap the top two elements on the stack.
[0973] 3.8 Arithmetic Instructions
[0974] iadd
[0975] Integer Add
[0976] Syntax: 68
[0977] Stack: . . . , value1, value2=> . . . , result
[0978] value1 and value 2 must be integers. The values are added
and are replaced on the stack by their integer sum.
[0979] ladd
[0980] Long Integer Add
[0981] Syntax: 69
[0982] Stack: . . . , value1-word1, value1-word2, value2-word1,
value2-word2=> . . . , result-word1, result-word2
[0983] value1 and value 2 must be long integers. The values are
added and are replaced on the stack by their long integer sum.
[0984] fadd
[0985] Single Floats Add
[0986] Syntax: 70
[0987] Stack: . . . , value1, value2=> . . . , result
[0988] value1 and value 2 must be single-precision floating point
numbers. The values are added and are replaced on the stack by
their single-precision floating point sum.
[0989] dadd
[0990] Double Floats Add
[0991] Syntax: 71
[0992] Stack: . . . , value1-word1, value1-word2, value2-word1,
value2-word2=> . . . , result-word1, result-word2
[0993] value1 and value 2 must be double-precision floating point
numbers. The values are added and are replaced on the stack by
their double-precision floating point sum.
[0994] isub
[0995] Integer Subtract
[0996] Syntax: 72
[0997] Stack: . . . , value1, value2=> . . . , result
[0998] value1 and value 2 must be integers. value2 is subtracted
from value1, and both values are replaced on the stack by their
integer difference.
[0999] lsub
[1000] Long Integer Subtract
[1001] Syntax: 73
[1002] Stack: . . . , value1-word1, value1-word2, value2-word1,
value2-word2=> . . . , result-word1, result-word2
[1003] value1 and value 2 must be long integers. value2 is
subtracted from value1, and both values are replaced on the stack
by their long integer difference.
[1004] fsub
[1005] Single Float Subtract
[1006] Syntax: 74
[1007] Stack: . . . , value1, value2=> . . . , result value1 and
value 2 must be single-precision floating point numbers. value2 is
subtracted from value1, and both values are replaced on the stack
by their single-precision floating point difference.
[1008] dsub
[1009] Double Float Subtract
[1010] Syntax: 75
[1011] Stack: . . . value1-word1, value1-word2, value2-word1,
value2-word2=> . . . , result-word1, result-word2
[1012] value1 and value 2 must be double-precision floating point
numbers. value2 is subtracted from value1, and both values are
replaced on the stack by their double-precision floating point
difference.
[1013] imul
[1014] Integer Multiply
[1015] Syntax: 76
[1016] Stack: . . . , value1, value2=> . . . , result
[1017] value1 and value 2 must be integers. Both values are
replaced on the stack by their integer product.
[1018] lmul
[1019] Long Integer Multiply
[1020] Syntax: 77
[1021] Stack: . . . , value1-word1, value1-word2, value2-word1,
value2-word2=> . . . , result-word1, result-word2
[1022] value1 and value 2 must be long integers. Both values are
replaced on the stack by their long integer product.
[1023] fmul
[1024] Single Float Multiply
[1025] Syntax: 78
[1026] Stack: . . . , value1, value2=> . . . , result
[1027] value1 and value 2 must be single-precision floating point
numbers. Both values are replaced on the stack by their
single-precision floating point product.
[1028] dmul
[1029] Double Float Multiply
[1030] Syntax: 79
[1031] Stack: . . . , value1-word1, value1-word2, value2-word1,
value2-word2=> . . . , result-word1, result-word2
[1032] value1 and value 2 must be double-precision floating point
numbers. Both values are replaced on the stack by their
double-precision floating point product.
[1033] idiv
[1034] Integer Divide
[1035] Syntax: 80
[1036] Stack: . . . , value1, value2=> . . . , result
[1037] value1 and value 2 must be integers. value1 is divided by
value2, and both values are replaced on the stack by their integer
quotient.
[1038] The result is truncated to the nearest integer that is
between it and 0. An attempt to divide by zero results in a "/by
zero" ArithmeticException being thrown.
[1039] ldiv
[1040] Long Integer Divide
[1041] Syntax: 81
[1042] Stack: . . . , value1-word1, value1-word2, value2-word1,
value2-word2=> . . . , result-word1, result-word2
[1043] value1 and value 2 must be long integers. value1 is divided
by value2, and both values are replaced on the stack by their long
integer quotient.
[1044] The result is truncated to the nearest integer that is
between it and 0. An attempt to divide by zero results in a "/ by
zero" ArithmeticException being thrown.
[1045] fdiv
[1046] Single Float Divide
[1047] Syntax: 82
[1048] Stack: . . . , value1, value2=> . . . , result
[1049] value1 and value 2 must be single-precision floating point
numbers. value1 is divided by value2, and both values are replaced
on the stack by their single-precision floating point quotient.
[1050] Divide by zero results in the quotient being NaN.
[1051] ddiv
[1052] Double Float Divide
[1053] Syntax: 83
[1054] Stack: . . . , value1-word1, value1-word2, value2-word1,
value2-word2=> . . . , result-word1, result-word2
[1055] value1 and value 2 must be double-precision floating point
numbers. value1 is divided by value2, and both values are replaced
on the stack by their double-precision floating point quotient.
[1056] Divide by zero results in the quotient being NaN.
[1057] irem
[1058] Integer Remainder
[1059] Syntax: 84
[1060] Stack: . . . , value1, value2=> . . . , result
[1061] value1 and value 2 must both be integers. value1 is divided
by value2, and both values are replaced on the stack by their
integer remainder.
[1062] An attempt to divide by zero results in a "/ by zero"
ArithmeticException being thrown.
[1063] lrem
[1064] Long Integer Remainder
[1065] Syntax: 85
[1066] Stack: . . . , value1-word1, value1-word2, value2-word1,
value2-word2=> . . . , result-word1, result-word2
[1067] value1 and value 2 must both be long integers. value1 is
divided by value2, and both values are replaced on the stack by
their long integer remainder.
[1068] An attempt to divide by zero results in a "/ by zero"
ArithmeticException being thrown.
[1069] frem
[1070] Single Float Remainder
[1071] Syntax: 86
[1072] Stack: . . . , value1, value2=> . . . ., result
[1073] value1 and value 2 must both be single-precision floating
point numbers. value1 is divided by value2, and the quotient is
truncated to an integer, and then multiplied by value2. The product
is subtracted from value1. The result, as a single-precision
floating point number, replaces both values on the stack.
result=value1-(integral_part(value1/value2)* value2), where
integral_part( ) rounds to the nearest integer, with a tie going to
the even number.
[1074] An attempt to divide by zero results in NaN.
[1075] drem
[1076] Double Float Remainder
[1077] Syntax: 87
[1078] Stack: . . . , value1-word1, value1-word2, value2-word1,
value2-word2=> . . . , result-word1, result-word2
[1079] value1 and value 2 must both be double-precision floating
point numbers. value1 is divided by value2, and the quotient is
truncated to an integer, and then multiplied by value2. The product
is subtracted from value1. The result, as a double-precision
floating point number, replaces both values on the stack.
result=value1-(integral_part(value1/value2)*val- ue2), where
integral_part( ) rounds to the nearest integer, with a tie going to
the even number.
[1080] An attempt to divide by zero results in NaN.
[1081] ineg
[1082] Integer Negate
[1083] Syntax: 88
[1084] Stack: . . . , value=> . . . , result
[1085] value must be an integer. It is replaced on the stack by its
arithmetic negation.
[1086] lneg
[1087] Long Integer Negate
[1088] Syntax: 89
[1089] Stack: . . . , value-word1, value-word2=> . . . .
result-word1, result-word2
[1090] value must be a long integer. It is replaced on the stack by
its arithmetic negation.
[1091] fneg
[1092] Single Float Negate
[1093] Syntax: 90
[1094] Stack: . . . , value=> . . . , result
[1095] value must be a single-precision floating point number. It
is replaced on the stack by its arithmetic negation.
[1096] dneg
[1097] Double Float Negate
[1098] Syntax: 91
[1099] Stack: . . . , value-word1, value-word2=> . . . ,
result-word1, result-word2
[1100] value must be a double-precision floating point number. It
is replaced on the stack by its arithmetic negation.
[1101] 3.9 Logical Instructions
[1102] ishl
[1103] Integer Shift Left
[1104] Syntax: 92
[1105] Stack: . . . , value1, value2=> . . . , result
[1106] value1 and value 2 must be integers. value1 is shifted left
by the amount indicated by the low five bits of value2. The integer
result replaces both values on the stack.
[1107] ishr
[1108] Integer Arithmetic Shift Right
[1109] Syntax: 93
[1110] Stack: . . . , value1, value2=> . . . , result
[1111] value1 and value 2 must be integers. value1 is shifted right
arithmetically (with sign extension) by the amount indicated by the
low five bits of value2. The integer result replaces both values on
the stack.
[1112] iushr
[1113] Integer Logical Shift Right
[1114] Syntax: 94
[1115] Stack: . . . , value1, value2=> . . . , result
[1116] value1 and value 2 must be integers. value1 is shifted right
logically (with no sign extension) by the amount indicated by the
low five bits of value2. The integer result replaces both values on
the stack.
[1117] lshl
[1118] Long Integer Shift Left
[1119] Syntax: 95
[1120] Stack: . . . , value1-word1, value1-word2, value2=> . . .
, result-word1, result-word2
[1121] value1 must be a long integer and value 2 must be an
integer. value1 is shifted left by the amount indicated by the low
six bits of value2. The long integer result replaces both values on
the stack.
[1122] lshr
[1123] Long Integer Arithmetic Shift Right
[1124] Syntax: 96
[1125] Stack: . . . , value1-word1, value1-word2, value2=>. . .
, result-word1, result-word2
[1126] value1 must be a long integer and value 2 must be an
integer. value1 is shifted right arithmetically (with sign
extension) by the amount indicated by the low six bits of value2.
The long integer result replaces both values on the stack.
[1127] lushr
[1128] Long Integer Logical Shift Right
[1129] Syntax: 97
[1130] Stack: . . . , value1-word1, value1-word2, value2-word1,
value2-word2=> . . . , result-word1, result-word2
[1131] value1 must be a long integer and value 2 must be an
integer. value1 is shifted right logically (with no sign extension)
by the amount indicated by the low six bits of value2. The long
integer result replaces both values on the stack.
[1132] iand
[1133] Integer Boolean AND
[1134] Syntax: 98
[1135] Stack: . . . , value1, value2=> . . . , result
[1136] value1 and value 2 must both be integers. They are replaced
on the stack by their bitwise logical and (conjunction).
[1137] land
[1138] Long Integer Boolean AND
[1139] Syntax: 99
[1140] Stack: . . . , value1-word1, value1-word2, value2-word1,
value2-word2=> . . . , result-word1, result-word2
[1141] value1 and value 2 must both be long integers. They are
replaced on the stack by their bitwise logical and
(conjunction).
[1142] ior
[1143] Integer Boolean OR
[1144] Syntax: 100
[1145] Stack: . . . , value1, value2=> . . . , result
[1146] value1 and value 2 must both be integers. They are replaced
on the stack by their bitwise logical or (disjunction)
[1147] lor
[1148] Long Integer Boolean OR
[1149] Syntax: 101
[1150] Stack: . . . , value1-word1, value1-word2, value2-word1,
value2-word2=> . . . , result-word1, result-word2
[1151] value1 and value 2 must both be long integers. They are
replaced on the stack by their bitwise logical or
(disjunction).
[1152] ixor
[1153] Integer Boolean XOR
[1154] Syntax: 102
[1155] Stack: . . . , value1, value2=> . . . , result
[1156] value1 and value 2 must both be integers. They are replaced
on the stack by their bitwise exclusive or (exclusive
disjunction).
[1157] lxor
[1158] Long Integer Boolean XOR
[1159] Syntax: 103
[1160] Stack: . . . . value1-word1, value1-word2, value2-word1,
value2-word2=> . . . , result-word1, result-word2
[1161] value1 and value 2 must both be long integers. They are
replaced on the stack by their bitwise exclusive or (exclusive
disjunction).
[1162] 3.10 Conversion Operations
[1163] i2l
[1164] Integer to Long Integer Conversion
[1165] Syntax: 104
[1166] Stack: . . . , value=> . . . , result-word1,
result-word2
[1167] value must be an integer. It is converted to a long integer.
The result replaces value on the stack.
[1168] i2f
[1169] Integer to Single Float
[1170] Syntax: 105
[1171] Stack: . . . , value=> . . . , result
[1172] value must be an integer. It is converted to a
single-precision floating point number. The result replaces value
on the stack.
[1173] i2d
[1174] Integer to Double Float
[1175] Syntax: 106
[1176] Stack: . . . , value=> . . . , result-word1,
result-word2
[1177] value must be an integer. It is converted to a
double-precision floating point number. The result replaces value
on the stack.
[1178] l2i
[1179] Long Integer to Integer
[1180] Syntax: 107
[1181] Stack: . . . , value-word1, value-word2=>result value
must be a long integer. It is converted to an integer by taking the
low-order 32 bits. The result replaces value on the stack.
[1182] l2f
[1183] Long Integer to Single Float
[1184] Syntax: 108
[1185] Stack: . . . , value-word1, value-word2=> . . . ,
result
[1186] value must be a long integer. It is converted to a
single-precision floating point number. The result replaces value
on the stack.
[1187] l2d
[1188] Long Integer to Double Float
[1189] Syntax: 109
[1190] Stack: . . . , value-word1, value-word2=> . . . ,
result-word1, result-word2
[1191] value must be a long integer. It is converted to a
double-precision floating point number. The result replaces value
on the stack.
[1192] f2i
[1193] Single Float to Integer
[1194] Syntax: 110
[1195] Stack: . . . , value=> . . . , result
[1196] value must be a single-precision floating point number. It
is converted to an integer. The result replaces value on the
stack.
[1197] f2l
[1198] Single Float to Long Integer
[1199] Syntax: 111
[1200] Stack: . . . , value=> . . . , result-word1,
result-word2
[1201] value must be a single-precision floating point number. It
is converted to a long integer. The result replaces value on the
stack.
[1202] f2d
[1203] Single Float to Double Float
[1204] Syntax: 112
[1205] Stack: . . . , value=> . . . , result-word1,
result-word2
[1206] value must be a single-precision floating point number. It
is converted to a double-precision floating point number. The
result replaces value on the stack.
[1207] d2i
[1208] Double Float to Integer
[1209] Syntax: 113
[1210] Stack: . . . , value-word1, value-word2=> . . . ,
result
[1211] value must be a double-precision floating point number. It
is converted to an integer. The result replaces value on the
stack.
[1212] d2l
[1213] Double Float to Long Integer
[1214] Syntax: 114
[1215] Stack: . . . , value-word1, value-word2=> . . . ,
result-word1, result-word2
[1216] value must be a double-precision floating point number. It
is converted to a long integer. The result replaces value on the
stack.
[1217] d2f
[1218] Double Float to Single Float
[1219] Syntax: 115
[1220] Stack: . . . , value-word1, value-word2=> . . . ,
result
[1221] value must be a double-precision floating point number. It
is converted to a single-precision floating point number. If
overflow occurs, the result must be infinity with the same sign as
value. The result replaces value on the stack.
[1222] int2 byte
[1223] Integer to Signed Byte
[1224] Syntax: 116
[1225] Stack: . . . , value=> . . . , result
[1226] value must be an integer. It is truncated to a signed 8-bit
result, then sign extended to an integer. The result replaces value
on the stack.
[1227] int2char
[1228] Integer to Char
[1229] Syntax: 117
[1230] Stack: . . . , value=> . . . , result
[1231] value must be an integer. It is truncated to an unsigned
16-bit result, then zero extended to an integer. The result
replaces value on the stack.
[1232] int2short
[1233] Integer to Short
[1234] Syntax: 118
[1235] Stack: . . . , value=> . . . , result
[1236] value must be an integer. It is truncated to a signed 16-bit
result, then sign extended to an integer. The result replaces value
on the stack.
[1237] 3.11 Control Transfer Instructions
[1238] ifeq
[1239] Branch if Equal to 0
[1240] Syntax: 119
[1241] Stack: . . . , value=>
[1242] value must be an integer. It is popped from the stack. If
value is zero, branchbyte1 and branchbyte2 are used to construct a
signed 16-bit offset. Execution proceeds at that offset from the
address of this instruction. Otherwise execution proceeds at the
instruction following the ifeq.
[1243] ifnull
[1244] Branch if Null
[1245] Syntax: 120
[1246] Stack: . . . , value=> . . .
[1247] value must be a reference to an object. It is popped from
the stack. If value is null, branchbyte1 and branchbyte2 are used
to construct a signed 16-bit offset. Execution proceeds at that
offset from the address of this instruction. Otherwise execution
proceeds at the instruction following the ifnull.
[1248] iflt
[1249] Branch if Less than 0
[1250] Syntax: 121 122
[1251] Stack: . . . , value=> . . .
[1252] value must be an integer. It is popped from the stack. If
value is less than zero, branchbyte1 and branchbyte2 are used to
construct a signed 16-bit offset. Execution proceeds at that offset
from the address of this instruction. Otherwise execution proceeds
at the instruction following the iflt.
[1253] ifle
[1254] Branch if Less than or Equal to 0
[1255] Syntax: 123
[1256] Stack: . . . , value=> . . .
[1257] value must be an integer. It is popped from the stack. If
value is less than or equal to zero, branchbyte1 and branchbyte2
are used to construct a signed 16-bit offset. Execution proceeds at
that offset from the address of this instruction. Otherwise
execution proceeds at the instruction following the ifle.
[1258] ifne
[1259] Branch if not Equal to 0
[1260] Syntax: 124
[1261] Stack: . . . , value=> . . .
[1262] value must be an integer. It is popped from the stack. If
value is not equal to zero, branchbyte1 and branchbyte2 are used to
construct a signed 16-bit offset. Execution proceeds at that offset
from the address of this instruction. Otherwise execution proceeds
at the instruction following the ifne.
[1263] ifnormull
[1264] Branch if not Null
[1265] Syntax: 125
[1266] Stack: . . . , value=> . . .
[1267] value must be a reference to an object. It is popped from
the stack. If value is notnull, branchbyte1 and branchbyte2 are
used to construct a signed 16-bit offset. Execution proceeds at
that offset from the address of this instruction. Otherwise
execution proceeds at the instruction following the ifnormull.
[1268] ifgt
[1269] Branch if Greater than 0
[1270] Syntax: 126
[1271] Stack: . . . , value=> . . .
[1272] value must be an integer. It is popped from the stack. If
value is greater than zero, branchbyte1 and branchbyte2 are used to
construct a signed 16-bit offset. Execution proceeds at that offset
from the address of this instruction. Otherwise execution proceeds
at the instruction following the ifgt.
[1273] ifge
[1274] Branch if Greater than or Equal to 0
[1275] Syntax: 127
[1276] Stack: . . . , value=> . . .
[1277] value must be an integer. It is popped from the stack. If
value is greater than or equal to zero, branchbyte1 and branchbyte2
are used to construct a signed 16-bit offset. Execution proceeds at
that offset from the address of this instruction. Otherwise
execution proceeds at the instruction following instruction
ifge.
[1278] if_icmpeq
[1279] Branch if Integers Equal
[1280] Syntax: 128
[1281] Stack: . . . , value1, value2=> . . .
[1282] value1 and value2 must be integers. They are both popped
from the stack. If values is equal to value2, branchbyte1 and
branchbyte2 are used to construct a signed 16-bit offset. Execution
proceeds at that offset from the address of this instruction.
Otherwise execution proceeds at the instruction following
instruction if_icmpeq.
[1283] if_icmpne
[1284] Branch if Integers not Equal
[1285] Syntax: 129 130
[1286] Stack: . . . , value1, value2=> . . .
[1287] value1 and value2 must be integers. They are both popped
from the stack. If value1 is not equal to value2, branchbyte1 and
branchbyte2 are used to construct a signed 16-bit offset. Execution
proceeds at that offset from the address of this instruction.
Otherwise execution proceeds at the instruction following
instruction if_icmpne.
[1288] if_icmplt
[1289] Branch if Integer Less than
[1290] Syntax: 131
[1291] Stack: . . . , value1, value2=> . . .
[1292] value1 and value2 must be integers. They are both popped
from the stack. If value1 is less than value2, branchbyte1 and
branchbyte2 are used to construct a signed 16-bit offset. Execution
proceeds at that offset from the address of this instruction.
Otherwise execution proceeds at the instruction following
instruction if_icmplt.
[1293] if_icmpgt
[1294] Branch if Integer Greater than
[1295] Syntax: 132
[1296] Stack: . . . , value1, value2=> . . .
[1297] value1 and value2 must be integers. They are both value2,
branchbyte1 and branchbyte2 are used to construct a signed 16-bit
offset. Execution proceeds at that offset from the address of this
instruction. Otherwise execution proceeds at the instruction
following instruction if_icmpgt.
[1298] if_icmple
[1299] Branch if Integer Less than or Equal to
[1300] Syntax: 133
[1301] Stack: . . . , value1, value2=> . . .
[1302] value1 and value2 must be integers. They are both popped
from the stack. If value1 is less than or equal to value2,
branchbyte1 and branchbyte2 are used to construct a signed 16-bit
offset. Execution proceeds at that offset from the address of this
instruction. Otherwise execution proceeds at the instruction
following instruction if_icmple.
[1303] if_icmpge
[1304] Branch if Integer Greater than or Equal to
[1305] Syntax: 134
[1306] Stack: . . . , value1, value2=> . . .
[1307] value1 and value2 must be integers. They are both popped
from the stack. If value1 is greater than or equal to value2,
branchbyte1 and branchbyte2 are used to construct a signed 16-bit
offset. Execution proceeds at that offset from the address of this
instruction. Otherwise execution proceeds at the instruction
following instruction if_icmpge.
[1308] lcmp
[1309] Long Integer Compare
[1310] Syntax: 135
[1311] Stack: . . . , value1-word1,
[1312] value1-word2, value2-word1, value2-word1=> . . . ,
result
[1313] value1 and value2 must be long integers. They are both
popped from the stack and compared. If value1 is greater than
value2, the integer value1 is pushed onto the stack. If value1 is
equal to value2, the value 0 is pushed onto the stack. If value1 is
less than value2, the value -1 is pushed onto the stack.
[1314] fcmpl
[1315] Single Float Compare (1 on NaN)
[1316] Syntax: 136
[1317] Stack: . . . , value1, value2=> . . . , result
[1318] value1 and value2 must be single-precision floating point
numbers. They are both popped from the stack and compared. If
value1 is greater than value2, the integer value 1 is pushed onto
the stack. If value1 is equal to value2, the value 0 is pushed onto
the stack. If value1 is less than value2, the value -1 is pushed
onto the stack.
[1319] If either value1 or value2 is NaN, the value -1 is pushed
onto the stack.
[1320] fcmpg
[1321] Single Float Compare (1 on NaN)
[1322] Syntax: 137
[1323] Stack: . . . , value1, value2=> . . . , result
[1324] value1 and value2 must be single-precision floating point
numbers. They are both popped from the stack and compared. If
value1 is greater than value2, the integer value 1 is pushed onto
the stack. If value1 is equal to value2, the value 0 is pushed onto
the stack. If value1 is less than value2, the value -1 is pushed
onto the stack.
[1325] If either value1 or value2 is NaN, the value 1 is pushed
onto the stack.
[1326] dcmpl
[1327] Double Float Compare (-1 on NaN)
[1328] Syntax: 138
[1329] Stack: . . . , value1-word1, value1-word2, value2-word1,
value2-word1=> . . . , result
[1330] value1 and value2 must be double-precision floating point
numbers. They are both popped from the stack and compared. If
value1 is greater than value2, the integer value 1 is pushed onto
the stack. If value1 is equal to value2, the value 0 is pushed onto
the stack. If value1 is less than value2, the value is pushed onto
the stack.
[1331] If either value1 or value2 is NaN, the value 1 is pushed
onto the stack.
[1332] dcmpg
[1333] Double Float Compare (1 on NaN)
[1334] Syntax: 139
[1335] Stack: . . . , value1-word1, value1-word2, value2-word1,
value2-word1=> . . . , result
[1336] value1 and value2 must be double-precision floating point
numbers. They are both popped from the stack and compared. If
value1 is greater than value2, the integer value 1 is pushed onto
the stack. If value1 is equal to value2, the value 0 is pushed onto
the stack. If value1 is less than value2, the value -1 is pushed
onto the stack.
[1337] If either value1 or value2 is NaN, the value 1 is pushed
onto the stack.
[1338] if_acmpeg
[1339] Branch if Object References are Equal
[1340] Syntax: 140
[1341] Stack: . . . , value1, value2=> . . .
[1342] value1 and value2 must be references to objects. They are
both popped from the stack. If the objects referenced are not the
same, branchbyte1 and branchbyte2 are used to construct a signed
16-bit offset.
[1343] Execution proceeds at that offset from the Address of this
instruction. Otherwise execution proceeds at the instruction
following the if_acmpeq.
[1344] if_acmpne
[1345] Branch if Object References not Equal
[1346] Syntax: 141
[1347] Stack: . . . , value1, value2=> . . .
[1348] value1 and value2 must be references to objects. They are
both popped from the stack. If the objects referenced are not the
same, branchbyte1 and ranchbyte2 are used to construct a signed
16-bit offset.
[1349] Execution proceeds at that offset from the address of this
instruction. Otherwise execution proceeds at the instruction
following instruction if_acmpne.
[1350] goto
[1351] Branch Always
[1352] Syntax: 142
[1353] Stack: no change
[1354] branchbyte1 and branchbyte2 are used to construct a signed
16-bit offset. Execution proceeds at that offset from the address
of this instruction.
[1355] goto_w
[1356] Branch Always (Wide Index)
[1357] Syntax: 143
[1358] Stack: no change
[1359] branchbyte1, branchbyte2, branchbyte3, and branchbyte4 are
used to construct a signed 32-bit offset.
[1360] Execution proceeds at that offset from the address of this
instruction.
[1361] jar
[1362] Jump Subroutine
[1363] Syntax: 144
[1364] Stack: . . . => . . . , return-address
[1365] branchbyte1 and branchbyte2 are used to construct a signed
16-bit offset. The address of the instruction immediately following
the jsr is pushed onto the stack.
[1366] Execution proceeds at the offset from the address of this
instruction.
[1367] jsr_w
[1368] Jump Subroutine (Wide Index)
[1369] Syntax: 145
[1370] Stack: . . . => . . . , return-address
[1371] branchbyte1, branchbyte2, branchbyte3, and branchbyte4 are
used to construct a signed 32-bit offset. The address of the
instruction immediately following the jsr_w is pushed onto the
stack. Execution proceeds at the offset from the address of this
instruction.
[1372] ret
[1373] Return from Subroutine
[1374] Syntax: 146
[1375] Stack: no change
[1376] Local variable vindex in the current JAVA frame must contain
a return address. The contents of the local variable are written
into the pc.
[1377] Note that jsr pushes the address onto the stack, and ret
gets it out of a local variable. This asymmetry is intentional.
[1378] ret_w
[1379] Return from Subroutine (wide index)
[1380] Syntax: 147
[1381] Stack: no change
[1382] vindexbyte1 and vindexbyte2 are assembled into an unsigned
16-bit index to a local variable in the current JAVA frame. That
local variable must contain a return address. The contents of the
local variable are written into the pc. See the ret instruction for
more information.
[1383] 3.12 Function Return
[1384] ireturn
[1385] Return Integer from Function
[1386] Syntax: 148
[1387] Stack: . . . , value=>[empty]
[1388] value must be an integer. The value value is pushed onto the
stack of the previous execution environment. Any other values on
the operand stack are discarded. The interpreter then returns
control to its caller.
[1389] lreturn
[1390] Return Long Integer from Function
[1391] Syntax: 149
[1392] Stack: . . . , value-word1, value-word2=>[empty]
[1393] value must be a long integer. The value value is pushed onto
the stack of the previous execution environment. Any other values
on the operand stack are discarded. The interpreter then returns
control to its caller.
[1394] freturn
[1395] Return Single Float from Function
[1396] Syntax: 150
[1397] Stack: . . . , value=>[empty]
[1398] value must be a single-precision floating point number. The
value value is pushed onto the stack of the previous execution
environment. Any other values on the operand stack are discarded.
The interpreter then returns control to its caller.
[1399] dreturn
[1400] Return Double Float from Function
[1401] Syntax: 151
[1402] Stack: . . . , value-word1, value-word2=>[empty] value
must be a double-precision floating point number. The value value
is pushed onto the stack of the previous execution environment. Any
other values on the operand stack are discarded. The interpreter
then returns control to its caller.
[1403] areturn
[1404] Return Object Reference from Function
[1405] Syntax: 152
[1406] Stack: . . . , value=>[empty]
[1407] value must be a reference to an object. The value value is
pushed onto the stack of the previous execution environment. Any
other values on the operand stack are discarded. The interpreter
then returns control to its caller.
[1408] return
[1409] Return (Void) from Procedure
[1410] Syntax: 153
[1411] Stack: . . . =>[empty]
[1412] All values on the operand stack are discarded.
[1413] The interpreter then returns control to its caller.
[1414] breakpoint
[1415] Stop and pass control to breakpoint handler
[1416] Syntax: 154
[1417] Stack: no change
[1418] 3.13 Table Jumping
[1419] tableswitch
[1420] Access Jump Table by Index and Jump
[1421] Syntax: 155
[1422] Stack: . . . , index=> . . .
[1423] tableswitch is a variable length instruction. Immediately
after the tableswitch opcode, between zero and three 0's are
inserted as padding so that the next byte begins at an address that
is a multiple of four. After the padding follow a series of signed
4-byte quantities: default-offset, low, high, and then high-low+1
further signed 4-byte offsets. The high-low+1 signed 4-byte offsets
are treated as a 0-based jump table.
[1424] The index must be an integer. If index is less than low or
index is greater than high, then default-offset is added to the
address of this instruction. Otherwise, low is subtracted from
index, and the index-low'th element of the jump table is extracted,
and added to the address of this instruction.
[1425] lookupswitch
[1426] Access Jump Table by Key Match and Jump
[1427] Syntax: 156
[1428] Stack: . . . , key=> . . .
[1429] lookupswitch is a variable length instruction. Immediately
after the lookupswitch opcode, between zero and three 0's are
inserted as padding so that the next byte begins at an address that
is a multiple of four.
[1430] Immediately after the padding are a series of pairs of
signed 4-byte quantities. The first pair is special. The first item
of that pair is the default offset, and the second item of that
pair gives the number of pairs that follow. Each subsequent pair
consists of a match and an offset.
[1431] The key must be an integer. The integer key on the stack is
compared against each of the matches. If it is equal to one of
them, the offset is added to the address of this instruction. If
the key does not match any of the matches, the default offset is
added to the address of this instruction.
[1432] 3.14 Manipulating Object Fields
[1433] putfield
[1434] Set Field in Object
[1435] Syntax: 157
[1436] Stack: . . . , objectref, value=> . . .
[1437] OR
[1438] Stack: . . . , objectref, value-word1, value-word2=> . .
.
[1439] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The constant pool item
will be a field reference to a class name and a field name. The
item is resolved to a field block pointer which has both the field
width (in bytes) and the field offset (in bytes).
[1440] The field at that offset from the start of the object
referenced by object refwill be set to the value on the top of the
stack.
[1441] This instruction deals with both 32-bit and 64-bit wide
fields.
[1442] If object ref is null, aNullPointerException is
generated.
[1443] If the specified field is a static field,
anIncompatibleClassChange- Error is thrown.
[1444] getfield
[1445] Fetch Field from Object
[1446] Syntax: 158
[1447] Stack: . . . , objectref=> . . . , value
[1448] OR
[1449] Stack: . . . , objectref=> . . . , value-word1,
value-word2
[1450] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The constant pool item
will be a field reference to a class name and a field name. The
item is resolved to a field block pointer which has both the field
width (in bytes) and the field offset (in bytes).
[1451] objectref must be a reference to an object. The value at
offset into the object referenced by objectref replaces objectref
on the top of the stack.
[1452] This instruction deals with both 32-bit and 64-bit wide
fields.
[1453] If objectref is null, a NullPointerException is
generated.
[1454] If the specified field is a static field, an
IncompatibleClassChangeError is thrown.
[1455] putstatic
[1456] Set Static Field in Class
[1457] Syntax: 159
[1458] Stack: . . . , value=> . . .
[1459] OR
[1460] Stack: . . . , value-word1, value-word2=> . . .
[1461] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The constant pool item
will be a field reference to a static field of a class. That field
will be set to have the value on the top of the stack.
[1462] This instruction works for both 32-bit and 64-bit wide
fields.
[1463] If the specified field is a dynamic field, an
IncompatibleClassChangeError is thrown.
[1464] getstatic
[1465] Get Static Field from Class
[1466] Syntax: 160
[1467] Stack: . . . , => . . . , value
[1468] OR
[1469] Stack: . . . , => . . . , value-word1, value-word2
[1470] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The constant pool item
will be a field reference to a static field of a class.
[1471] This instruction deals with both 32-bit and 64-bit wide
fields.
[1472] If the specified field is a dynamic field, an
IncompatibleClassChangeError is generated.
[1473] 3.15 Method Invocation
[1474] There are four instructions that implement method
invocation.
27 invokevirtual Invoke an instance method of an object,
dispatching based on the runtime (virtual) type of the object. This
is the normal method dispatch in JAVA. invokenonvirtual Invoke an
instance method of an object, dispatching based on the compile-time
(non-virtual) type of the object. This is used, for example, when
the keywordsuper or the name of a superclass is used as a method
qualifier. invokestatic Invoke a class (static) method in a named
class. invokeinterface Invoke a method which is implemented by an
interface, searching the methods implemented by the particular
run-time object to find the appropriate method.
[1475] invokevirtual
[1476] Invoke Instance Method, Dispatch Based on Run-Time Type
[1477] Syntax: 161
[1478] Stack: . . . , objectref, [arg1, [arg2 . . . ]], . . . =>
. . .
[1479] The operand stack must contain a reference to an object and
some number of arguments.indexbyte1 and indexbyte2 are used to
construct an index into the constant pool of the current class. The
item at that index in the constant pool contains the complete
method signature. A pointer to the object's method table is
retrieved from the object reference. The method signature is looked
up in the method table. The method signature is guaranteed to
exactly match one of the method signatures in the table.
[1480] The result of the lookup is an index into the method table
of the named class, which is used with the object's dynamic type to
look in the method table of that type, where a pointer to the
method block for the matched method is found. The method block
indicates the type of method (native, synchronized, and so on) and
the number of arguments expected on the operand stack.
[1481] If the method is marked synchronized the monitor associated
with objectref is entered.
[1482] The objectref and arguments are popped off this method's
stack and become the initial values of the local variables of the
new method. Execution continues with the first instruction of the
new method.
[1483] If the object reference on the operand stack is null, a
NullPointerException is thrown. If during the method invocation a
stack overflow is detected, a StackOverflowError is thrown.
[1484] invokenonvirtual
[1485] Invoke Instance Method, Dispatching Based on Compile-Time
Type
[1486] Syntax: 162
[1487] Stack: . . . , objectref, [arg1, [arg2 . . . ]], . . . =>
. . .
[1488] The operand stack must contain a reference to an object and
some number of arguments.indexbyte1 and indexbyte2 are used to
construct an index into the constant pool of the current class. The
item at that index in the constant pool contains a complete method
signature and class. The method signature is looked up in the
method table of the class indicated. The method signature is
guaranteed to exactly match one of the method signatures in the
table.
[1489] The result of the lookup is a method block. The method block
indicates the type of method (native, synchronized, and so on) and
the number of arguments (nargs) expected on the operand stack.
[1490] If the method is marked synchronized the monitor associated
with objectref is entered.
[1491] The objectref and arguments are popped off this method's
stack and become the initial values of the local variables of the
new method. Execution continues with the first instruction of the
new method.
[1492] If the object reference on the operand stack is null, a
NullPointerException is thrown. If during the method invocation a
stack overflow is detected, a StackOverflowError is thrown.
[1493] invokestatic
[1494] Invoke a Class (Static) Method
[1495] Syntax: 163
[1496] Stack: . . . , [arg1, [arg2 . . . ]], . . . => . . .
[1497] The operand stack must contain some number of
arguments.indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The item at that index
in the constant pool contains the complete method signature and
class. The method signature is looked up in the method table of the
class indicated. The method signature is guaranteed to exactly
match one of the method signatures in the class's method table.
[1498] The result of the lookup is a method block. The method block
indicates the type of method (native, synchronized, and so on) and
the number of arguments (nargs) expected on the operand stack.
[1499] If the method is marked synchronized the monitor associated
with the class is entered.
[1500] The arguments are popped off this method's stack and become
the initial values of the local variables of the new method.
Execution continues with the first instruction of the new
method.
[1501] If during the method invocation a stack overflow is
detected, a StackOverflowError is thrown.
[1502] invokeinterface
[1503] Invoke Interface Method
[1504] Syntax: 164
[1505] Stack: . . . , objectref, [arg1, [arg2 . . . ]], . . . =>
. . .
[1506] The operand stack must contain a reference to an object and
nargs-1 arguments indexbyte1 and indexbyte2 are used to construct
an index into the constant pool of the current class. The item at
that index in the constant pool contains the complete method
signature. A pointer to the object's method table is retrieved from
the object reference. The method signature is looked up in the
method table. The method signature is guaranteed to exactly match
one of the method signatures in the table.
[1507] The result of the lookup is a method block. The method block
indicates the type of method (native, synchronized, and so on) but
unlike invokevirtual and invokenonvirtual, the number of available
arguments (nargs) is taken from the bytecode.
[1508] If the method is marked synchronized the monitor associated
with objectref is entered.
[1509] The objectref and arguments are popped off this method's
stack and become the initial values of the local variables of the
new method. Execution continues with the first instruction of the
new method.
[1510] If the objectref on the operand stack is null, a
NullPointerException is thrown. If during the method invocation a
stack overflow is detected, a StackOverflowError is thrown.
[1511] 3.16 Exception Handling
[1512] athrow
[1513] Throw Exception or Error
[1514] Syntax: 165
[1515] Stack: . . . , objectref=>[undefined]
[1516] objectref must be a reference to an object which is a
subclass of Throwable, which is thrown. The current JAVA stack
frame is searched for the most recent catch clause that catches
this class or a superclass of this class. If a matching catch list
entry is found, the pc is reset to the address indicated by the
catch-list entry, and execution continues there.
[1517] If no appropriate catch clause is found in the current stack
frame, that frame is popped and the object is rethrown. If one is
found, it contains the location of the code for this exception. The
pc is reset to that location and execution continues. If no
appropriate catch is found in the current stack frame, that frame
is popped and the objectref is rethrown.
[1518] If objectref is null, then a NullPointerException is thrown
instead.
[1519] 3.17 Miscellaneous Object Operations
[1520] new
[1521] Create New Object
[1522] Syntax: 166
[1523] Stack: . . . => . . . objectref
[1524] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The item at that index
must be a class name that can be resolved to a class pointer,
class. A new instance of that class is then created and a reference
to the object is pushed on the stack.
[1525] checkcast
[1526] Make Sure Object is of Given Type
[1527] Syntax: 167
[1528] Stack: . . . , objectref=> . . . , objectref
[1529] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The string at that
index of the constant pool is presumed to be a class name which can
be resolved to a class pointer, class. objectref must be a
reference to an object.
[1530] checkcast determines whether objectref can be cast to be a
reference to an object of class class. A null objectref can be cast
to any class. Otherwise the referenced object must be an instance
of class or one of its superclasses. If objectref can be cast to
class execution proceeds at the next instruction, and the objectref
remains on the stack.
[1531] If objectref cannot be cast to class, a ClassCastException
is thrown.
[1532] instanceof
[1533] Determine if an Object is of Given Type
[1534] Syntax: 168
[1535] Stack: . . . , objectref=> . . . , result
[1536] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The string at that
index of the constant pool is presumed to be a class name which can
be resolved to a class pointer, class. objectref must be a
reference to an object.
[1537] instanceof determines whether objectref can be cast to be a
reference to an object of the class class. This instruction will
overwrite objectref with 1 if objectref is an instance of class or
one of its superclasses. Otherwise, objectref is overwritten by 0.
If objectref is null, it's overwritten by 0.
[1538] 3.18 Monitors
[1539] monitorenter
[1540] Enter Monitored Region of Code
[1541] Syntax: 169
[1542] Stack: . . . , objectref=> . . .
[1543] objectref must be a reference to an object.
[1544] The interpreter attempts to obtain exclusive access via a
lock mechanism to objectref. If another thread already has
objectref locked, than the current thread waits until the object is
unlocked. If the current thread already has the object locked, then
continue execution. If the object is not locked, then obtain an
exclusive lock.
[1545] If objectref is null, then a NullPointerException is thrown
instead.
[1546] monitorexit
[1547] Exit Monitored Region of Code
[1548] Syntax: 170
[1549] Stack: . . . , objectref=> . . .
[1550] objectref must be a reference to an object. The lock on the
object released. If this is the last lock that this thread has on
that object (one thread is allowed to have multiple locks on a
single object), then other threads that are waiting for the object
to be available are allowed to proceed.
[1551] If objectref is null, then a NulilPointerException is thrown
instead.
[1552] Appendix A: An Optimization
[1553] The following set of pseudo-instructions suffixed by _quick
are variants of JAVA virtual machine instructions. They are used to
improve the speed of interpreting bytecodes. They are not part of
the virtual machine specification or instruction set, and are
invisible outside of an JAVA virtual machine implementation.
However, inside a virtual machine implementation they have proven
to be an effective optimization.
[1554] A compiler from JAVA source code to the JAVA virtual machine
instruction set emits only non-_quick instructions. If the _quick
pseudo-instructions are used, each instance of a non-_quick
instruction with a _quick variant is overwritten on execution by
its_quick variant. Subsequent execution of that instruction
instance will be of the_quick variant.
[1555] In all cases, if an instruction has an alternative version
with the suffix quick, the instruction references the constant
pool. If the_quick optimization is used, each non-_quick
instruction with a_quick variant performs the following:
[1556] Resolves the specified item in the constant pool;
[1557] Signals an error if the item in the constant pool could not
be resolved for some reason;
[1558] Turns itself into the _quick version of the instruction. The
instructions putstatic, getstatic, putfield, and getfield each have
two _quick versions; and
[1559] Performs its intended operation.
[1560] This is identical to the action of the instruction without
the _quick optimization, except for the additional step in which
the instruction, overwrites itself with its quick variant.
[1561] The _quick variant of an instruction assumes that the item
in the constant pool has already been resolved, and that this
resolution did not generate any errors. It simply performs the
intended operation on the resolved item.
[1562] Note: some of the invoke methods only support a single-byte
offset into the method table of the object; for objects with 256 or
more methods some invocations cannot be "quicked" with only these
bytecodes.
[1563] This Appendix doesn't give the opcode values of the
pseudo-instructions, since they are invisible and subject to
change.
[1564] A.1 Constant Pool Resolution
[1565] When the class is read in, an array constant_pool [ ] of
size n constants is created and assigned to a field in the
class.constant_pool [0] is set to point to a dynamically allocated
array which indicates which fields in the constant_pool have
already been resolved.constant_pool [1] through constant_pool
[nconstants-1] are set to point at the "type" field that
corresponds to this constant item.
[1566] When an instruction is executed that references the
constant_pool, an index is generated, and constant_pool[0] is
checked to see if the index has already been resolved. If so, the
value of constant_pool [index] is returned. If not, the value of
constant_pool [index] is resolved to be the actual pointer or data,
and overwrites whatever value was already in constant_pool
[index].
[1567] A.2 Pushing Constants onto the Stack (_quick variants)
[1568] ldcl_quick
[1569] Push Item from Constant Pool onto Stack
[1570] Syntax: 171
[1571] Stack: . . . => . . . , item
[1572] indexbyte1 is used as an unsigned 8-bit index into the
constant pool of the current class. The item at that index is
pushed onto the stack.
[1573] ldc2_quick
[1574] Push Item from Constant Pool onto Stack
[1575] Syntax: 172
[1576] Stack: . . . => . . . , item
[1577] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The constant at that
index is resolved and the item at that index is pushed onto the
stack.
[1578] ldc2w_quick
[1579] Push Long Integer or Double Float from Constant Pool onto
Stack
[1580] Syntax: 173
[1581] Stack: . . . => . . . , constant-word1,
constant-word2
[1582] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The constant at that
index is pushed onto the stack.
[1583] A.3 Managing Arrays (_quick variants)
[1584] anewarray_quick
[1585] Allocate New Array of References to Objects
[1586] Syntax: 174
[1587] Stack: . . . , size=>result
[1588] size must be an integer. It represents the number of
elements in the new array.
[1589] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The entry must be a
class.
[1590] A new array of the indicated class type and capable of
holding size elements is allocated, and result is a reference to
this new array. Allocation of an array large enough to contain size
items of the given class type is attempted. All elements of the
array are initialized to zero.
[1591] If size is less than zero, a NegativeArraySizeException is
thrown. If there is not enough memory to allocate the array, an
OutOfMemoryError is thrown.
[1592] multianewarray_quick
[1593] Allocate New Multi-Dimensional Array
[1594] Syntax: 175
[1595] Stack: . . . , size1, size2, . . . sizen=>result
[1596] Each size must be an integer. Each represents the number of
elements in a dimension of the array.
[1597] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The resulting entry
must be a class.
[1598] dimensions has the following aspects:
[1599] It must be an integer .gtoreq.1.
[1600] It represents the number of dimensions being created. It
must be .ltoreq. the number of dimensions of the array class.
[1601] It represents the number of elements that are popped off the
stack. All must be integers greater than or equal to zero. These
are used as the sizes of the dimension.
[1602] If any of the size arguments on the stack is less than zero,
a NegativeArraySizeException is thrown. If there is not enough
memory to allocate the array, an OutOfMemoryError is thrown.
[1603] The result is a reference to the new array object.
[1604] A.4 Manipulating Object Fields (_quick variants)
[1605] putfield_quick
[1606] Set Field in Object
[1607] Syntax: 176
[1608] Stack: . . . , objectref, value=> . . .
[1609] objectref must be a reference to an object. value must be a
value of a type appropriate for the specified field. offset is the
offset for the field in that object. value is written at offset
into the object. Both objectref and value are popped from the
stack.
[1610] If objectref is null, a NullPointerException is
generated.
[1611] putfield2_quick
[1612] Set Long Integer or Double Float Field in Object
[1613] Syntax: 177
[1614] Stack: . . . , objectref, value-word1, value-word2=> . .
.
[1615] objectref must be a reference to an object. value must be a
value of a type appropriate for the specified field. offset is the
offset for the field in that object. value is written at offset
into the object. Both objectref and value are popped from the
stack.
[1616] If objectref is null, a NullPointerException is
generated.
[1617] getfield_quick
[1618] Fetch Field from Object
[1619] Syntax: 178
[1620] Stack: . . . , objectref=> . . . , value
[1621] objectref must be a handle to an object. The value at offset
into the object referenced by objectref replaces objectref on the
top of the stack.
[1622] If objectref is null, a NullPointerException is
generated.
[1623] getfield2_quick
[1624] Fetch Field from Object
[1625] Syntax: 179
[1626] Stack: . . . , objectref=> . . . , value-word1,
value-word2
[1627] objectref must be a handle to an object. The value at offset
into the object referenced by objectref replaces objectref on the
top of the stack.
[1628] If objectref is null, a NullPointerException is
generated.
[1629] putstatic_quick
[1630] Set Static Field in Class
[1631] Syntax: 180
[1632] Stack: . . . , value=> . . .
[1633] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The constant pool item
will be a field reference to a static field of a class.value must
be the type appropriate to that field. That field will be set to
have the value value.
[1634] putstatic2_quick
[1635] Set Static Field in Class
[1636] Syntax: 181
[1637] Stack: . . . , value-word1, value-word2=> . . .
[1638] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The constant pool item
will be a field reference to a static field of a class. That field
must either be a long integer or a double precision floating point
number. value must be the type appropriate to that field. That
field will be set to have the value value.
[1639] getstatic_quick
[1640] Get Static Field from Class
[1641] Syntax: 182
[1642] Stack: . . . , => . . . , value
[1643] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The constant pool item
will be a field reference to a static field of a class. The value
of that field will replace handle on the stack.
[1644] getstatic2_quick
[1645] Get Static Field from Class
[1646] Syntax: 183
[1647] Stack: . . . , => . . . , value-word1, value-word2
[1648] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The constant pool item
will be a field reference to a static field of a class. The field
must be a long integer or a double precision floating point number.
The value of that field will replace handle on the stack
[1649] A.5 Method Invocation (_quick variants)
[1650] invokevirtual_quick
[1651] Invoke Instance Method, Dispatching Based on Run-Time
Type
[1652] Syntax: 184
[1653] Stack: . . . , objectref, [arg1, [arg2 . . . ]]=> . .
.
[1654] The operand stack must contain objectref, a reference to an
object and nargs-1 arguments. The method block at offset in the
object's method table, as determined by the object's dynamic type,
is retrieved. The method block indicates the type of method
(native, synchronized, etc.).
[1655] If the method is marked synchronized the monitor associated
with the object is entered.
[1656] The base of the local variables array for the new JAVA stack
frame is set to point to objectref on the stack, making objectref
and the supplied arguments (arg1, arg2, . . . ) the first nargs
local variables of the new frame. The total number of local
variables used by the method is determined, and the execution
environment of the new frame is pushed after leaving sufficient
room for the locals. The base of the operand stack for this method
invocation is set to the first word after the execution
environment. Finally, execution continues with the first
instruction of the matched method.
[1657] If objectref is null, a NullPointerException is thrown. If
during the method invocation a stack overflow is detected, a
StackoverflowError is thrown.
[1658] invokevirtualobject_quick
[1659] Invoke Instance Method of Class JAVA.lang.Object,
Specifically for Benefit of Arrays
[1660] Syntax: 185
[1661] Stack: . . . , objectref, [arg1, [arg2 . . . ]]=> . .
.
[1662] The operand stack must contain objectref, a reference to an
object or to an array and nargs-1 arguments. The method block at
offset in JAVA.lang.Object's method table is retrieved. The method
block indicates the type of method (native, synchronized,
etc.).
[1663] If the method is marked synchronized the monitor associated
with handle is entered.
[1664] The base of the local variables array for the new JAVA stack
frame is set to point to objectref on the stack, making objectref
and the supplied arguments (arg1, arg2, . . . ) the first nargs
local variables of the new frame. The total number of local
variables used by the method is determined, and the execution
environment of the new frame is pushed after leaving sufficient
room for the locals. The base of the operand stack for this method
invocation is set to the first word after the execution
environment. Finally, execution continues with the first
instruction of the matched method.
[1665] If objectref is null, a NullPointerException is thrown. If
during the method invocation a stack overflow is detected, a
StackOverflowError is thrown.
[1666] invokenonvirtual_quick
[1667] Invoke Instance Method, Dispatching Based on Compile-Time
Type
[1668] Syntax: 186
[1669] Stack: . . . , objectref, [arg1, [arg2 . . . ]]=> . .
.
[1670] The operand stack must contain objectref, a reference to an
object and some number of arguments. indexbyte1 and indexbyte2 are
used to construct an index into the constant pool of the current
class. The item at that index in the constant pool contains a
method slot index and a pointer to a class. The method block at the
method slot index in the indicated class is retrieved. The method
block indicates the type of method (native, synchronized, etc.) and
the number of arguments (nargs) expected on the operand stack.
[1671] If the method is marked synchronized the monitor associated
with the object is entered.
[1672] The base of the local variables array for the new JAVA stack
frame is set to point to objectref on the stack, making objectref
and the supplied arguments (arg1, arg2, . . . ) the first nargs
local variables of the new frame. The total number of local
variables used by the method is determined, and the execution
environment of the new frame is pushed after leaving sufficient
room for the locals. The base of the operand stack for this method
invocation is set to the first word after the execution
environment. Finally, execution continues with the first
instruction of the matched method.
[1673] If objectref is null, a NullPointerException is thrown. If
during the method invocation a stack overflow is detected, a
StackOverflowError is thrown.
[1674] invokestatic_quick
[1675] Invoke a Class (Static) Method
[1676] Syntax: 187
[1677] Stack: . . . , [arg1, [arg2 . . . ]]=> . . .
[1678] The operand stack must contain some number of arguments.
indexbyte1 and indexbyte2 are used to construct an index into the
constant pool of the current class. The item at that index in the
constant pool contains a method slot index and a pointer to a
class. The method block at the method slot index in the indicated
class is retrieved. The method block indicates the type of method
(native, synchronized, etc.) and the number of arguments (nargs)
expected on the operand stack.
[1679] If the method is marked synchronized the monitor associated
with the method's class is entered.
[1680] The base of the local variables array for the new JAVA stack
frame is set to point to the first argument on the stack, making
the supplied arguments (arg1, arg2, . . . ) the first nargs local
variables of the new frame. The total number of local variables
used by the method is determined, and the execution environment of
the new frame is pushed after leaving sufficient room for the
locals. The base of the operand stack for this method invocation is
set to the first word after the execution environment. Finally,
execution continues with the first instruction of the matched
method.
[1681] If the object handle on the operand stack is null, a
NullPointerException is thrown. If during the method invocation a
stack overflow is detected, a StackOverflowError is thrown.
[1682] invokeinterface_quick
[1683] Invoke Interface Method
[1684] Syntax: 188
[1685] Stack: . . . , objectref, [arg1, [arg2 . . . ]]=> . .
.
[1686] The operand stack must contain objectref, a reference to an
object, and nargs-1 arguments. idbyte1 and idbyte2 are used to
construct an index into the constant pool of the current class. The
item at that index in the constant pool contains the complete
method signature. A pointer to the object's method table is
retrieved from the object handle.
[1687] The method signature is searched for in the object's method
table. As a short-cut, the method signature at slot guess is
searched first. If that fails, a complete search of the method
table is performed. The method signature is guaranteed to exactly
match one of the method signatures in the table.
[1688] The result of the lookup is a method block. The method block
indicates the type of method (native, synchronized, etc.) but the
number of available arguments (nargs) is taken from the
bytecode.
[1689] If the method is marked synchronized the monitor associated
with handle is entered.
[1690] The base of the local variables array for the new JAVA stack
frame is set to point to handle on the stack, making handle and the
supplied arguments (arg1, arg2, . . . ) the first nargs local
variables of the new frame. The total number of local variables
used by the method is determined, and the execution environment of
the new frame is pushed after leaving sufficient room for the
locals. The base of the operand stack for this method invocation is
set to the first word after the execution environment. Finally,
execution continues with the first instruction of the matched
method.
[1691] If objectref is null, a NullPointerException is thrown. If
during the method invocation a stack overflow is detected, a
StackOverflowError is thrown.
[1692] guess is the last guess. Each time through, guess is set to
the method offset that was used.
[1693] A.6 Miscellaneous Object Operations (_quick variants)
[1694] new_quick
[1695] Create New Object
[1696] Syntax: 189
[1697] Stack: . . . => . . . , objectref
[1698] indexbyte1 and indexbyte2 are used to construct an index
into the constant pool of the current class. The item at that index
must be a class. A new instance of that class is then created and
objectref, a reference to that object is pushed on the stack.
[1699] checkcast_quick
[1700] Make Sure Object is of Given Type
[1701] Syntax: 190
[1702] Stack: . . . , objectref=> . . . , objectref
[1703] objectref must be a reference to an object. indexbyte1 and
indexbyte2 are used to construct an index into the constant pool of
the current class. The object at that index of the constant pool
must have already been resolved.
[1704] checkcast then determines whether objectref can be cast to a
reference to an object of class class. A null reference can be cast
to any class, and otherwise the superclasses of objectref's type
are searched for class. If class is determined to be a superclass
of objectref's type, or if objectref is null, it can be cast to
objectref cannot be cast to class, a ClassCastException is
thrown.
[1705] instanceof_quick
[1706] Determine if Object is of Given Type
[1707] Syntax: 191
[1708] Stack: . . . , objectref=> . . . , result
[1709] objectref must be a reference to an object. indexbyte1 and
indexbyte2 are used to construct an index into the constant pool of
the current class. The item of class class at that index of the
constant pool must have already been resolved.
[1710] Instance of determines whether objectref can be cast to an
object of the class class. A null objectref can be cast to any
class, and otherwise the superclasses of objectref's type are
searched for class. If class is determined to be a superclass of
objectref's type, result is 1 (true). Otherwise, result is 0
(false). If handle is null, result is 0 (false).
* * * * *