System and method for retiring approximately simultaneously a group of instructions in a superscalar microprocessor

Abstract
An system and method for retiring instructions in a superscalar microprocessor which executes a program comprising a set of instructions having a predetermined program order, the retirement system for simultaneously retiring groups of instructions executed in or out of order by the microprocessor. The retirement system comprises a done block for monitoring the status of the instructions to determine which instruction or group of instructions have been executed, a retirement control block for determining whether each executed instruction is retirable, a temporary buffer for storing results of instructions executed out of program order, and a register array for storing retirable-instruction results. In addition, the retirement control block further controls the retiring of a group of instructions determined to be retirable, by simultaneously transferring their results from the temporary buffer to the register array, and retires instructions executed in order by storing their results directly in the register array. The method comprises the steps of monitoring the status of the instructions to determine which group of instructions have been executed, determining whether each executed instruction is retirable, storing results of instructions executed out of program order in a temporary buffer, storing retirable-instruction results in a register array and retiring a group of retirable instructions by simultaneously transferring their results from the temporary buffer to the register array, and retiring instructions executed in order by storing their results directly in the register array.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


The present invention relates generally to the field of superscalar processors, and more particularly, to a system and method for retiring multiple instructions executed out-of-order in a superscalar processor.


2. Discussion of Related Art


One method of increasing performance of microprocessor-based systems is overlapping the steps of different instructions using a technique called pipelining. In pipelining operations, various steps of instruction execution (e.g. fetch, decode and execute) are performed by independent units called pipeline stages. The steps are performed in parallel in the various pipeline stages so that the processor can handle more than one instruction at a time.


As a result of pipelining, processor-based systems are typically able to execute more than one instruction per clock cycle. This practice allows the rate of instruction execution to exceed the clock rate. Processors that issue, or initiate execution of, multiple independent instructions per clock cycle are known as superscalar processors. A superscalar processor reduces the average number of cycles per instruction beyond what is possible in ordinary pipelining systems.


In a superscalar system, the hardware can execute a small number of independent instructions in a single clock cycle. Multiple instructions can be executed in a single cycle as long as there are no data dependencies, procedural dependencies, or resource conflicts. When such dependencies or conflicts exist, only the first instruction in a sequence can be executed. As a result, a plurality of functional units in a superscalar architecture cannot be fully utilized.


To better utilize a superscalar architecture, processor designers have enhanced processor look-ahead capabilities; that is the ability of the processor to examine instructions beyond the current point of execution in an attempt to find independent instructions for immediate execution. For example, if an instruction dependency or resource conflict inhibits instruction execution, a processor with look-ahead capabilities can look beyond the present instruction, locate an independent instruction, and execute it.


As a result, more efficient processors, when executing instructions, put less emphasis on the order in which instructions are fetched and more emphasis on the order in which they are executed. As a further result, instructions are executed out of order.


For a more in-depth discussion of superscalar processors, see Johnson, Superscalar Microprocessor Design, Prentice Hall, Inc. (1991).


Scenarios occur whereby the execution of the instructions is interrupted or altered, and the execution must be restarted in the correct order. Two such scenarios will be described.


In a first scenario, during look-ahead operations, many processor designs employ predictive techniques to predict a branch that the program is going to follow in that particular execution. In these systems, the instructions fetched and executed as a result of look-ahead operations are instructions from the branch of code that was predicted. High instructing throughput is achieved by fetching and issuing instructions under the assumption that branches chosen are predicted correctly and that exceptions do not occur. This technique, known as speculative execution, allows instruction execution to proceed without waiting for the completion of previous instructions. In other words, execution of the branch target instruction stream begins before it is determined whether the conditional branch will be taken.


Since the branch prediction occasionally fails, the processor must provide recovery mechanisms for canceling the effects of instructions that were speculatively executed. The processor must also provide restart mechanisms to reestablish the correct instruction sequence.


In a second scenario, out-of-order completion makes it difficult to deal with exceptions. Exceptions are created by instructions when the instruction cannot be properly executed by hardware alone. These exceptions are commonly handled by interrupts, permitting a software routine to correct the situation. Once the routine is completed, the execution of the interrupted program must be restarted so it can continue as before the exception.


Processors contains information that must be saved for a program to be suspended and then restored for execution to continue. This information is known as the “state” of the processor. The state information typically includes a program counter (PC), an interrupt address register (IAR), and a program status register (PSR); the PSR contains status flags such as interrupt enable, condition codes, and so forth.


As program instructions are executed, the state machine is updated based on the instructions. When execution is halted and must later be restarted (i.e., one of the two above scenarios occurs) the processor looks to the state machine for information on how to restart execution. In superscalar processors, recovery and restart occur frequently and must be accomplished rapidly.


In some conventional systems, when instructions are executed out of order, the state of the machine is updated out of order (i.e., in the same order as the instructions were executed). Consequently, when the processor goes back to restart the execution, the state of the machine has to be “undone” to put it back in a condition such that execution may begin again.


To understand conventional systems, it is helpful to understand some common terminology. An in-order state is made up of the most recent instruction result assignments resulting from a continuous sequence of executed instructions. Assignments made by instructions completed out-of-order where previous instruction(s) have not been completed, are not included in this state.


If an instruction is completed and all previous instructions have also been completed, the instruction's results can be stored in the in-order state. When instructions are stored in the in-order state, the machine never has to access results from previous instructions and the instruction is considered “retired.”


A look-ahead state is made up of all future assignments, completed and uncompleted, beginning with the first uncompleted instruction. Since there are completed and uncompleted instructions, the look-ahead state contains actual as well as pending register values.


Finally, an architectural state is made up of the most recently completed assignment of the continuous string of completed instructions and all pending assignments to each register. Subsequent instructions executed out of order must access the architectural state to determine what state the register would be in had the instruction been executed in order.


One method used in conventional systems to recover from misdirected branches and exceptions is known as checkpoint repair. In checkpoint repair, the processor provides a set of logical spaces, only one of which is used for current execution. The other logical spaces contain backup copies of the in-order state, each corresponding to a previous point in execution. During execution, a checkpoint is made by copying the current architectural state to a backup space. At this time, the oldest backup state is discarded. The checkpoint is updated as instructions are executed until an in-order state is reached. If an exception occurs, all previous instructions are allowed to execute, thus bringing the checkpoint to the in-order state.


To minimize the amount of required overhead, checkpoints are not made at every instruction. When an exception occurs, restarting is accomplished by loading the contents of the checkpointed state preceding the point of exception, and then executing the instructions in order up to the point of exception. For branch misprediction recovery, checkpoints are made at ever) branch and contain the precise state at which to restart execution immediately.


The disadvantage of checkpoint repair is that it requires a tremendous amount of storage for the logical spaces. This storage overhead requires additional chip real estate which is a valuable and limited resource in the microprocessor.


Other conventional systems use history buffers to store old states that have been superseded by new states. In this architecture, a register buffer contains the architectural state. The history buffer is a last-in first-out (LIFO) stack containing items in the in-order state superseded by look-ahead values (i.e., old values that have been replaced by new values), hence the term “history.”


The current value (prior to decode) of the instruction's destination register is pushed onto the stack. The value at the bottom of the stack is discarded if its associated instruction has been completed. When an exception occurs, the processor suspends decoding and waits until all other pending instructions are completed, and updates the register file accordingly. All values are then popped from the history buffer in LIFO order and written back into the register file. The register file is now at the in-order state at the point of exception.


The disadvantage associated with the history buffer technique is that several clock cycles are required to restore the in-order state.


Still other conventional systems use a reorder buffer managed as a first-in first-out (FIFO) queue to restart after exceptions and mispredictions. The reorder buffer contains the look-ahead state, and a register file contains the in-order state. These two can be combined to determine the architectural state. When an instruction is decoded, it is assigned an entry at the top of the reorder buffer. When the instruction completes, the result value is written to the allocated entry. When the value reaches the bottom of the buffer, it is written into the register file if there are no exceptions. If the instruction is not complete when it reaches the bottom, the reorder buffer does not advance until the instruction completes. When an exception occurs, the reorder buffer is discarded and the in-order state is accessed.


The disadvantage of this technique is that it requires associative lookup to combine the in-order and look-ahead states. Furthermore, associative lookup is not straightforward since it must determine the most recent assignments if there is more than one assignment to a given register. This requires that the reorder buffer be implemented as a true FIFO, rather than a more simple, circularly addressed register array.


What is needed then is a system and method for maintaining a current state of the machine and for efficiently updating system registers based on the results of instructions executed out of order. This system and method should use a minimum of chip real estate and power and should provide quick recovery of the state of the machine up to the point of an exception. Furthermore, the system should not require complex steps of associative lookup to obtain the most recent value of a register.


SUMMARY OF THE INVENTION

The present invention is a system and method for retiring instructions issued out of order in a superscalar microprocessor system. According to the technique of the present invention, results of instructions executed out of order are first stored in a temporary buffer until all previous instructions have been executed. Once all previous instructions have been executed and their results stored in order in a register array, the results of the instruction in question can be written to the register array and the instruction is considered retired.


The register array contains the current state of the machine. To maintain the integrity of register array data, only results of instructions are not written to the register array until the results of all previous instructions have been written. In this manner, the state of the machine is updated in order, and situations such as exceptions and branch mispredictions can be handled quickly and efficiently.


The present invention comprises means for assigning and writing instruction results to a temporary storage location, transferring results from temporary storage to the register array so that the register array is updated in an in-order fashion and accessing results in the register array and temporary storage for subsequent operations.


Further features and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, are described in detail below with reference to the accompanying drawings.





BRIEF DESCRIPTION OF THE DRAWINGS/FIGURES


FIG. 1 is a data path diagram of a superscalar instruction execution unit.



FIG. 2 is a block diagram illustrating the functions of the superscalar instruction execution unit.



FIG. 3 is a diagram further illustrating the instruction FIFO and the instruction window.



FIG. 4 is a diagram illustrating instruction retirement according to the present invention.



FIG. 5A shows the configuration of an instruction window.



FIG. 5B is a diagram illustrating the assignment of instruction results to storage locations in a temporary buffer according to the present invention.



FIG. 6A is a timing diagram illustrating data writing to a register array according to the present invention.



FIG. 6B is a timing diagram illustrating writing results to four register locations per clock cycle according to the present invention.





In the drawings, like reference numbers indicate identical or functionally similar elements. Additionally, the left-most digit of a reference number identifies the drawing in which the reference number first appears.


DETAILED DESCRIPTION OF THE INVENTION

1. Overview


The present invention provides a system and a method for retiring completed instructions such that to the program it appears that the instructions are executed sequentially in the original program order. The technique of the present invention is to store all out-of-order instruction results (results of instructions not executed in the program order) in a temporary buffer until all previous instructions are complete without any exceptions. The results are then transferred from the temporary buffer to a register array which represents the official state.


When an instruction is retired, all previous instructions have been completed and the retired instruction is officially completed. When instructions are retired according to the technique of the present invention, the state of the machine is updated in order. Therefore, when an exception occurs, out-of-order execution is suspended and all uncompleted instructions prior to the exception are executed and retired. Thus, the state of the machine is up to date as of the time of the exception. When the exception is complete, out-of-order execution resumes from the point of exception. When a branch misprediction is detected, all instructions prior to the branch are executed and retired, the state of the machine is now current, and the machine can restart at that point. All results residing in the temporary buffer from instructions on the improper branch are ignored. As new instructions from the correct branch are executed, their results are written into the temporary buffer, overwriting any results obtained from the speculatively executed instruction stream.


2. Environment



FIG. 1 illustrates a block diagram of a superscalar Instruction Execution Unit (IEU) capable of out-of-order instruction issuing. Referring to FIG. 1, there are two multi-ported register files 102A, 102B which hold general purpose registers. Each register file 102 provides five read ports and two write ports. Each write port allows two writes per cycle. In general, register file 102A holds only integer data while register file 102B can hold both floating point and integer data.


Functional units 104 are provided to perform processing functions. In this example, functional units 104 are three arithmetic logic units (ALUs) 104A, a shifter 104B, a floating-point ALU 104C, and a floating-point multiplier 104D. Floating-point ALU 104C and floating-point multiplier 104D can execute both integer and floating-point operations.


Bypass multiplexers 106 allow the output of any functional unit 104 to be used as an input to any functional unit 104. This technique is used when the results of an instruction executed in one clock cycle are needed for the execution of another instruction in the next clock cycle. Using bypass multiplexers 106, the result needed can be input directly to the appropriate functional unit 104. The instruction requiring those results can be issued on that same clock cycle. Without bypass multiplexers 106, the results of the executed instruction would have to be written to register file 102 on one clock cycle and then be output to the functional unit 104 on the next clock cycle. Thus, without bypass multiplexers 106 one full clock cycle is lost. This technique, also known as forwarding, is well known in the art and is more fully described in Hennessy et al., Computer Architecture a Quantitative Approach, Morgan Kaufmann Publishers (1990) on pages 260-262.


Selection multiplexers 108 provide a means for selecting the results from functional units 104 to be written to register files 102.



FIG. 2 illustrates a block diagram of IEU control logic 200 for the IEU shown in FIG. 1. IEU control logic 200 includes an instruction window 202. Instruction window 202 defines the instructions which IEU control logic 200 may issue during one clock cycle. Instruction window 202 represents the bottom two locations in an instruction buffer, which is a FIFO register containing instructions to be executed. This instruction buffer is also referred to as an instruction FIFO. As instructions are completed, there are flushed out at the bottom and new, instructions are dropped in at the top. The bottom location of instruction window 202 is referred to as bucket 0 and the top location of instruction window 202 is referred to as bucket 1.


When all four instructions in bucket 0 have been retired, they are flushed out of bucket 0, the instructions in bucket 1 drop into bucket 0 and a new group of four instructions drops into bucket 1. Instruction window 202 may be implemented using a variety of techniques. One such technique is fully described in U.S. Pat. No. 5,497,499, entitled “Superscalar RISC Instruction Scheduling” and issued Mar. 5, 1996, the disclosure of which is incorporated herein by reference.


In the current example, instruction window 202 contains eight instructions. Therefore, IEU control logic 200 tries to issue a maximum number of instructions from among these eight during each clock cycle. Instruction decoding occurs in decoders 203. Instruction decoding is an ongoing process performed in IEU control logic 200. Instructions must be decoded before dependency checking (discussed below), issuing and execution occur.


IEU control logic 200 also contains register renaming circuitry (RRC) 204 which performs two related functions. The first function performed is data dependency checking. Once data dependency checking is complete, RRC 204 assigns tags to each instruction which are used to track the location of instruction operands and results.


Data dependency checking logic, residing in RRC 204, is used for checking instructions for dependencies. In checking for dependencies, the data dependency checking logic looks at the various register file source and destination addresses to determine whether one or more previous instructions must be executed before a subsequent instruction may be executed. FIG. 3 further illustrates instruction window 202 and the instruction FIFO. Referring to FIG. 3, various register file source and destination addresses 302 of the instruction I0 must be checked against the source and destination addresses of all other instructions.


Referring back to FIG. 2, since instruction window 202 in this example can contain 8 instructions, the IEU can look at eight instructions for scheduling purposes. All source register addresses must be compared with all previous destination addresses. If one instruction is dependent upon completion of a previous instruction, these two instructions cannot be completed out of order. In other words, if instruction I2 requires the results of instruction I1, a dependency exists and I1 must be executed before I2. Some instructions may be long-word instructions, which require extra care when checking for dependencies. For long-word instructions, the instructions occupy two registers both of which must be checked when examining this instruction for dependencies.


An additional function performed in RRC 204 is tag assignment. Proper tag assignment is crucial to effective instruction retirement according to the present invention. Each instruction in instruction window 202 is assigned a tag based on its location in instruction window 202, and based on the results of data dependency checking discussed above. The tag assigned to each instruction indicates where in a temporary buffer that instruction's results are to be stored until that instruction is retired and whether all of the previous instructions on which that instruction is dependent have been completed. Tag assignment and the temporary buffer are discussed in more detail below.


A further function performed by IEU control logic 200 is determining which instructions are ready for issuing. An instruction issuer 208 issues instructions to the appropriate functional unit 104 for execution. Circuitry within RRC 204 determines which instructions in instruction window 202 are ready for issuing and sends a bit map to instruction issuer 208 indicating which instructions are ready for issuing. Instruction decode logic 203 indicates the resource requirement for each instruction. Issuer 208 also receives information from functional units 104 concerning resource availability. This information is scanned by issuer 208 and an instruction is selected for issuing.


Instruction issuer 208 sends a control signal 209 to multiplexers 210 telling them which instruction to send to functional units 104. Instruction issuer 208 also sends a control signal 211 to multiplexer 212 configuring it to send the appropriate register address to configure the register that is to receive the results of the instruction. Depending on the availability of functional units 104, issuer 208 may issue multiple instructions each clock cycle.


Referring again to FIGS. 1 and 2, once an instruction is issued to functional units 104 and executed by the same, register files 102A and 102B must be updated to reflect the current state of the machine. When the machine has to “go back” and restart an execution because of an exception or a branch misprediction, the state of the machine must reflect the up-to-date state at the time the exception or branch occurred. Even when instructions are issued and executed out of order, the state of the machine must still reflect, or be recoverable to, the current state at the time of exception or branching.


The Instruction Retirement Unit (IRU) of the present invention, retires the instructions as if they were executed in order. In this manner, the state of the machine is updated, in order, to the point of the most recent instruction in a sequence of completed instructions.


The present invention provides a unique system and method for retiring instructions and updating the state of the machine such that when a restart is required due to an exception or a branch misprediction, the current state up to that point is recoverable without needing to wait for the register file to be rebuilt or reconstructed to negate the effects of out-of-order executions.


3. Implementations



FIG. 4 illustrates a high-level diagram of an Instruction Retirement Unit 400 (referred to as “IRU 400”) of the present invention. IRU 400 and its functions are primarily contained within register file 102 and a retirement control block (RCB) 409. As shown in FIG. 4, the functions performed by the environment are also critical to proper instruction retirement.


Referring to FIG. 4, the operation of IRU 400 will now be described. As discussed in subsection 2 of this application, the instructions executed in the superscalar processor environment are executed out of order, and the out-of-order results cannot be written to the registers until all previous instructions' results are written in order. A register array 404 represents the in-order state of the machine. The results of all instructions completed without exceptions, who also have no previous uncompleted instructions, are stored in register array 404. Once the results are stored in register array 404, the instruction responsible for those results is considered “retired.”


If an instruction is completed out of order, and there are previous instructions that have not been completed, the results of that instruction are temporarily stored in a temporary buffer 403. Once all instructions previous to the instruction in question have been executed and their results transferred to register array 404, the instruction in question is retirable, and its results can be transferred from temporary buffer 403 to register array 404. Once this is done, the instruction is considered retired. A retirable instruction then, is an instruction for which two conditions have been met: (1) it is completed, and (2) there are no unexecuted instructions appearing earlier in the program order.


If the results of an executed instruction are required by a subsequent instruction, those results will be made available to the appropriate functional unit 104 regardless of whether they are in temporary buffer 403 or register array 404.


Referring to FIGS. 1, 2, and 4, IRU 400 will be more fully described. Register file 102 includes a temporary buffer 403, a register array 404 and selection logic 408. There are two input ports 110 used to transfer results to temporary buffer 403 and register array 404. Control signals (not shown) generated in IEU control logic 200 are used to select the results in selection multiplexer 108 when the results are ready to be stored in register file 102. Selection multiplexer 108 receives data from various functional units and multiplexes this data onto input ports 110.


Two input ports 110 for each register file 102 in the preferred embodiment permit two simultaneous register operations to occur. Thus, input ports 110 provide two full register width data values to be written to temporary buffer 403. This also permits multiple register locations to be written in one clock cycle. The technique of writing to multiple register address locations in one clock cycle is fully described below.



FIGS. 5A and B illustrate the allocation of temporary buffer 403. FIG. 5A shows a configuration of instruction window 202, and FIG. 5B shows an example ordering of data results in temporary buffer 403. As noted previously, there can be a maximum of eight pending instructions at any one time. Each instruction may require one or two of temporary buffer's 403 eight register locations 0 through 7, depending on whether it is a regular-length or a long-word instruction.


The eight pending instructions in instruction window 202 are grouped into four pairs. The first instructions from buckets 0 and 1 (i.e. I0 and I4) are a first pair. The other pairs, I1 and I5, etc., are similarly formed. A result of I0 (I0RD) is stored in register location 0, and a result of I4 (I4RD) is stored in register location 1. If I0 is a long-word entry, I0RD, the low-word result (result of the first half of a long-word instruction) is still stored in location 0, but now the high-word result (I0RD+1, from the second half of the instruction) is stored in location 1. This means that the low-word result of I4 does not have a space in temporary buffer 403, and therefore can not be issued at this time.


Tags are generated in RRC 204 and assigned to each instruction before the instruction's results are store in temporary buffer 403. This facilitates easy tracking of results, particularly when instructions are executed out of order. Each tag comprises three bits, for example, to indicate addresses for writing the instruction's results in temporary buffer 403. These three bits are assigned according to the instructions locations in instruction window 202. The tags are used by the RRC to locate results in temporary buffer 403 if they are operands for other instructions, for example. Table 1 illustrates a representative assignment for these three tag bits.









TABLE 1







Tag Assignment









INSTRUCTION
TAG
LOCATION





0
000
0


1
010
2


2
100
4


3
110
6


4
001
1


5
011
3


6
101
5


7
111
7









Each location in instruction window 202 has a corresponding location in temporary buffer 403. The least significant bit indicates the bucket in instruction window 202 where the instructions originated. This bit is interpreted differently when the bucket containing the instruction changes. For example, when all four instructions of bucket 0 are retired, the instructions in bucket 1 drop into bucket 0. When this occurs the LSB (least significant bit) of the tag that previously indicated bucket 1, now indicates bucket 0. For example, in Table 1, an LSB of 1 indicates the instructions in bucket 1. When these instructions are dropped into bucket 0, the LSB will not change and an LSB of 1 will indicate bucket 0. The tag contains information on how to handle each instruction.


When the instruction is executed and its results are output from a functional unit, the tag follows. Three bits of each instruction's tag uniquely identify the register location where the results of that instruction are to be stored. A temporary write block (not shown) looks at functional units 104, the instruction results and the tags. Each functional unit 104 has 1 bit that indicates if a result is going to be output from that functional unit 104 on the next clock cycle. The temporary write block gets the tag for each result that will be available on the next clock cycle. The temporary write block generates an address (based on the tag) where the upcoming results are to be stored in temporary buffer 403. The temporary write block addresses temporary buffer 403 via RRC 204 on the next clock cycle when the results are ready at functional unit 104.


As noted above, a function of the tags is to permit the results of a particular functional unit 104 can be routed directly to the operand input of a functional unit 104. This occurs when a register value represents an operand that is needed immediately by a functional unit 104. The results can also be stored in register array 404 or temporary buffer 403.


In addition, the tags indicate to the IEU when to return those results directly to bypass multiplexers 106 for immediate use by an instruction executing in the very next clock cycle. The instruction results may be sent to either the bypass multiplexers 106, register file 102, or both.


The results of all instructions executed out of order are stored first in a temporary buffer 403. As discussed above, temporary buffer 403 has eight storage locations. This number corresponds to the size of instruction window 202. In the example discussed above, instruction window 202 has eight locations and thus there are up to eight pending instructions. Consequently, up to eight instruction results may need to be stored in temporary buffer 403.


If an instruction is completed in order, that is all previous instructions are already completed and their results written to register array 404, the results of that instruction can be written directly to register array 404. RCB 409 knows if results can go directly to register array 404. In this situation, RCB 409 sets an external write bit enabling a write operation to register array 404. Note, in the preferred embodiment, the results in this situation are still written to temporary buffer 403. This is done for simplicity.


For each instruction result in temporary buffer 403, when all previous instructions are complete, without any exceptions or branch mispredictions, that result is transferred from temporary buffer 403 to a register array 404 via selection logic 408. If an instruction is completed out of order and previous instructions are not all completed, the results of that instruction remain in temporary buffer 403 until all previous instructions are completed. If one or more instructions have been completed, and they are all awaiting completion of an instruction earlier in the program order, they cannot be retired. However, once this earlier instruction is completed, the entire group is retirable and can be retired.


A done block 420 is an additional state machine of the processor. Done block 420 keeps track of what instructions are completed and marks these instructions ‘done’ using a done flag. The done block informs a retirement control block 409 which instructions are done. The retirement control block 409, containing retirement control circuitry checks the done flags to see if all previous instructions of each pending instruction are completed. When retirement control block 409 is informed that all instructions previous (in the program order) to the pending instruction are completed, the retirement control block 409 determines that the pending instruction is retirable.



FIG. 6A is a timing diagram illustrating writing to register array 404, and FIG. 6B is a timing diagram illustrating the transfer of data from temporary buffer 403 to register array 404. Referring to FIGS. 4, 6A, and 6B, the technique of writing to register array 404 will be described.


Temporary buffer 403 has four output ports F, G, H, and I that are used to transfer data to register array 404. Register array 404 has two input ports, A′ and B′, for accepting instruction results from either temporary buffer 403 or functional units 104. Write enable signals 602 and 604 enable writes to temporary buffer 403 and register array 404, respectively, as shown at 603. Although not illustrated, there are actually 2 write enable signals 604 for register array 404. One of these enable signals 604 is for enabling writes to input port A′, and the other is for enabling writes to input port B′. Since there are two input ports A′, and B′, two writes to register array 404 can occur simultaneously.


Data to be written to register array 404 can come from either temporary buffer 403 or functional units 104 (via selection multiplexer 108 and bus 411). Control signal 606 is used to select the data in selection logic 408. When control signal 606 is a logic high, for example, data is selected from temporary buffer 403. Signal 410 is the write address, dictating the location where data is to be written in either temporary buffer 403 or register array 404. Data signal 608 represents the data being transferred from temporary buffer 403 to register array 404. Alternatively, data signal 608 represents data 110 from functional units 104 via selection multiplexer 108.


Register array 404 can write 4 locations in one clock cycle. Address 410 and write enable 604 signals are asserted first, then data 608 and control signal 606 are asserted. Control signal 606 is asserted as shown at 605. During the first half of the cycle, registers corresponding to instructions I0 and I1 will be updated. During the second half of the cycle, registers corresponding to I2 and I3 will be updated. If any of the results are long words, the upper half of the word will be updated during the second cycle. Thus, two results can be simultaneously transferred and two instructions can be simultaneously retired in a half a clock cycle. A total of four instructions can therefore be retired per clock cycle.


Referring to FIG. 6B, read addresses 612F, 612G, 612H, and 612I are available for temporary buffer 403 output ports F through I. Data 614F, 614G, 614H, and 614I is available from temporary buffer 403 at the beginning of the clock cycle, as shown at 615. Addresses 410A are generated for input port A′ and 410B are generated for input port B′. Similarly, a write enable signal 604A for input port A′ and a write enable signal 604B for input port B′ are generated for each half of the clock cycle. Address 410 appearing in the first half of the clock cycle, as shown at 611A and 611B, is the location to which data is written during enable signal 604 appearing in the first half, as shown as 605A and 605B. Similarly, data is written during the second half of the clock cycle to the address 410 appearing at that time, as shown at 613A and 613B. Since data is written to A′ and B′ simultaneously, up to four instruction results may be written to register array 404 during one clock cycle. Therefore, up to four instructions may be retired during one clock cycle.


Latches in selection logic 408 hold the data constant until the appropriate address 410 is present and write enable signals 604 allow the data to be written.


The process of transferring a result from temporary buffer 403 to register array 404, as described above, is called retiring. When an instruction is retired, it can be considered as officially completed. All instructions previous to that instruction have been completed without branch mispredictions or exceptions and the state of the machine will never have to be redetermined prior to that point. As a result, to the program running in the processor, it appears that the instructions are updated and executed sequentially.


Since instructions are being issued and executed out of order, subsequent instructions may require operands corresponding to results (values) in temporary buffer 403 or register array 404. Therefore, access to register values in temporary buffer 403, as well as values stored in register array 404 is provided by the present invention.


Read access to temporary buffer 403 and register file 404 is controlled by RRC 204. Such read access is required by instructions executing that need results of previously executed instructions. Recall from the discussion in subsection 2 above that RRC 204 performs data dependency checking. RRC 204 knows which instructions are dependent on which instructions and which instructions have been completed. RRC 204 determines if the results required by a particular instruction must be generated by a previous instruction, i.e. whether a dependency exists. If a dependency exists, the previous instruction must be executed first. An additional step is required, however, when a dependency exists. This step is determining where to look for the results of the instruction. Since RRC 204 knows what instructions have been completed, it also knows whether to look for the results of those instructions in temporary buffer 403 or register array 404.


RRC 204 sends a port read address 410 to register array 404 and temporary buffer 403 to read the data from the correct location onto output lines 412. One bit of read address 410 indicates whether the location is in temporary buffer 403 or register array 404. Again, see U.S. Pat. No. 5,497,499, entitled “Superscalar RISC Instruction Scheduling” and issued Mar. 5, 1996 for additional disclosure pertaining to the RRC.


In the preferred embodiment of the present invention, each output port A through E of temporary buffer 403 and register array 404 has its own dedicated address line. That is, each memory location can be output to any port.


4. Additional Features of the Invention


IRU 200 also informs other units when instructions are retired. IRU 200 informs an Instruction Fetch Unit (IFU) when it (the IRU) has changed the state of the processor. In this manner, the IFU can maintain coherency with IEU 100. The state information sent to the IFU is the information required to update the current Program Counter and to request more instructions from the IFU. In the example above, when four instructions are retired, the IFU can increment the PC by four and fetch another bucket of four instructions.


An example of the IFU is disclosed in a commonly owned, copending application Ser. No. 07/817,810 titled “High Performance RISC Microprocessor Architecture.”


In addition, according to a preferred embodiment of the present invention, status bits and condition codes are retired in order as well. Each of the eight instructions in instruction window 202 has its own copy of the status bits and condition codes. If an instruction does not affect any of the status bits, then it propagates the status bits from the previous instruction.


When an instruction is retired, all its status bits have to be officially updated. If more than one instruction is retired in one cycle, the status bits of the most recent (in order) instruction are used for the update.


5. Conclusion


While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

Claims
  • 1. A superscalar microprocessor for executing instructions having a program order, the microprocessor comprising: a temporary buffer comprising a plurality of temporary buffer locations configured to store result data for executed instructions, wherein the temporary buffer locations are arranged in a plurality of groups of temporary buffer locations, each group of temporary buffer locations including a number (N) of the temporary buffer locations, the number N being greater than 1;tag assignment logic configured to assign tags to instructions, wherein each tag identifies one of the temporary buffer locations, wherein each tag has a first portion that identifies one of the groups of temporary buffer locations and a second portion that identifies one of the temporary buffer locations within the group of temporary buffer locations identified by the first portion of the tag, andwherein the tag assignment logic is further configured to concurrently assign a tag to each instruction in a first set of instructions, wherein the number of instructions in the first set of instructions is at least 1 and not more than the number N, and wherein the tags are assigned such that the respective tag assigned to each of the instructions in the first set of instructions identifies a different one of the temporary buffer locations in a first one of the groups of temporary buffer locations;a plurality of functional units configured to execute instructions from at least the first set of instructions out of the program order, thereby generating result data for each of the instructions in the first set of instructions;a plurality of data paths configured to transfer result data from the functional units to the temporary buffer, wherein the result data for each instruction in the first set of instructions is transferred to the temporary buffer location identified by the tag assigned to that instruction;a register array including a plurality of array locations for storing result data for instructions that have been retired;a retirement control block configured to determine whether execution of all of the instructions in the first set of instructions is complete; anda superscalar instruction retirement unit configured to concurrently retire all of the instructions in the first set of instructions after execution of all of the instructions in the first set of instructions is complete, wherein retiring at least one of the instructions in the first set of instructions includes transferring the result data for the at least one instruction from the temporary buffer location identified by the tag assigned to the at least one instruction to a selected one of the array locations in the register array.
  • 2. The superscalar microprocessor of claim 1 wherein the respective first portions of the respective tags assigned to the instructions in the first set of instructions are identical to each other and the respective second portions of the respective tags assigned to the instructions in the first set of instructions are different from each other.
  • 3. The superscalar microprocessor of claim 1 wherein: each of the instructions in the first set of instructions specifies one of the array locations in the register array; andthe instruction retirement unit is further configured to transfer the result data for each of the instructions in the first set of instructions from the temporary buffer location identified by the tag assigned to that instruction to the array location specified by that instruction.
  • 4. The superscalar microprocessor of claim 1 wherein the temporary buffer is configured as a FIFO and wherein each of the groups of temporary buffer locations corresponds to an entry in the FIFO.
  • 5. The superscalar microprocessor of claim 4 wherein the instruction retirement unit is further configured to advance the FIFO by one entry upon retirement of the first set of instructions.
  • 6. The superscalar microprocessor of claim 1 wherein the number N is greater than 2.
  • 7. The superscalar microprocessor of claim 1 wherein the number N is equal to 4.
  • 8. The superscalar microprocessor of claim 1 wherein each of the instructions in the first set of instructions specifies one of the array locations in the register array; and wherein the respective tags are assigned to each of the instructions in the first set of instructions without regard to the specified array locations.
  • 9. The superscalar microprocessor of claim 1 wherein: the first set of instructions includes a first instruction and a second instruction, the first instruction preceding the second instruction in the program order;the second instruction is executed before the first instruction; andthe result data for the second instruction is stored in the temporary buffer location identified by the tag assigned to the second instruction before the result data for the first instruction is stored in the temporary buffer location identified by the tag assigned to the first instruction.
  • 10. The superscalar microprocessor of claim 1 wherein the tag assignment logic is further configured such that after the first set of instructions is retired, the tags assigned to the instructions in the first set of instructions are reassigned to instructions in a second set of instructions, the second set of instructions being subsequent to the first set of instructions in the program order.
  • 11. The superscalar microprocessor of claim 1 wherein the tag assignment logic is configured to concurrently assign a tag to each instruction in a second set of instructions before the instructions in the first set of instructions are retired, wherein the respective tag assigned to each of the instructions in the second set identifies a different one of the temporary buffer locations in a second one of the groups of temporary buffer locations.
  • 12. The superscalar microprocessor of claim 11 wherein each tag has a first portion that identifies one of the groups of temporary buffer locations and a second portion that identifies one of the temporary buffer locations within the group of temporary buffer locations identified by the first portion of the tag.
  • 13. The superscalar microprocessor of claim 12 wherein: the respective first portions of the respective tags assigned to the instructions in the first set of instructions are identical to each other, andthe respective first portions of the respective tags assigned to the instructions in the second set of instructions are identical to each other and different from the respective first portions of the respective tags assigned to the instructions in the first set of instructions.
  • 14. The superscalar microprocessor of claim 13 wherein: the respective second portions of the respective tags assigned to the instructions in the first set of instructions are different from each other,the respective second portions of the respective tags assigned to the instructions in the second set of instructions are different from each other, andthe respective second portion of each of the respective tags assigned to the instructions in the first set of instructions is identical to the respective second portion of exactly one of the respective tags assigned to the instructions in the second set of instructions.
  • 15. A superscalar microprocessor for executing instructions having a program order, the microprocessor comprising: a temporary buffer comprising a plurality of temporary buffer locations configured to store result data for executed instructions, wherein the temporary buffer locations are arranged in a plurality of groups of temporary buffer locations, each group of temporary buffer locations including a number (N) of the temporary buffer locations, the number N being greater than 1, wherein the temporary buffer includes exactly two groups of temporary buffer locations;tag assignment logic configured to assign tags to instructions, wherein each tag identifies one of the temporary buffer locations,wherein the tag assignment logic is further configured to concurrently assign a tag to each instruction in a first set of instructions, wherein the number of instructions in the first set of instructions is at least 1 and not more than the number N, and wherein the tags are assigned such that the respective tag assigned to each of the instructions in the first set of instructions identifies a different one of the temporary buffer locations in a first one of the groups of temporary buffer locations;a plurality of functional units configured to execute instructions from at least the first set of instructions out of the program order, thereby generating result data for each of the instructions in the first set of instructions;a plurality of data paths configured to transfer result data from the functional units to the temporary buffer, wherein the result data for each instruction in the first set of instructions is transferred to the temporary buffer location identified by the tag assigned to that instruction;a register array including a plurality of array locations for storing result data for instructions that have been retired;a retirement control block configured to determine whether execution of all of the instructions in the first set of instructions is complete; anda superscalar instruction retirement unit configured to concurrently retire all of the instructions in the first set of instructions after execution of all of the instructions in the first set of instructions is complete, wherein retiring at least one of the instructions in the first set of instructions includes transferring the result data for the at least one instruction from the temporary buffer location identified by the tag assigned to the at least one instruction to a selected one of the array locations in the register array.
  • 16. In a superscalar microprocessor, a method of executing instructions having a program order, the method comprising: receiving a first set of instructions, the first set of instructions including at least one instruction and not more than a number (N) of instructions, the number N being greater than 1;concurrently assigning a tag to each instruction in the first set of instructions, wherein the tag assigned to each of the instructions in the first set of instructions identifies one of a plurality of temporary buffer locations in a temporary buffer, the temporary buffer locations being configured to store result data for executed instructions, wherein the temporary buffer locations are arranged in a plurality of groups of temporary buffer locations, each group of temporary buffer locations including the number N of the temporary buffer locations,wherein each tag has a first portion that identifies one of the groups of temporary buffer locations and a second portion that identifies one of the temporary buffer locations within the group of temporary buffer locations identified by the first portion of the tag, andwherein the tags are assigned to the instructions in the first set of instructions such that the first portions of the respective tags assigned to the instructions in the first set of instructions are identical to each other and the second portions of the respective tags assigned to the instructions in the first set of instructions are different from each other, andwherein the tags are assigned such that the respective tag assigned to each of the instructions in the first set of instructions identifies a different one of the temporary buffer locations in a first one of the groups of temporary buffer locations;executing the instructions of the first set of instructions, thereby generating result data for each of the instructions in the first set of instructions, wherein at least one of the instructions in the first set of instructions is executed out of the program order;storing the result data in the temporary buffer, wherein the result data for each instruction in the first set of instructions is transferred to the temporary buffer location identified by the tag assigned to that instruction;determining whether execution of all of the instructions in the first set of instructions is complete; andin response to determining that execution of all of the instructions in the first set of instructions is complete, concurrently retiring all of the instructions in the first set of instructions, wherein retiring at least one of the instructions in the first set of instructions includes transferring the result data for the at least one instruction from the temporary buffer locations identified by the tag assigned to the at least one instruction to a selected one array location in a register array.
  • 17. The method of claim 16 wherein: each of the instructions in the first set of instructions specifies one of the array locations in the register array; andconcurrently retiring all of the instructions in the first set of instructions includes transferring the result data for each of the instructions in the first set of instructions from the temporary buffer location identified by the tag assigned to that instruction to the array location specified by that instruction.
  • 18. The method of claim 16 wherein the temporary buffer is configured as a FIFO and wherein each of the groups of temporary buffer locations corresponds to an entry in the FIFO, the method further comprising: upon retiring all of the instructions in the first set of instructions, advancing the FIFO by one entry.
  • 19. The method of claim 16 wherein the number N is greater than 2.
  • 20. The method of claim 16 wherein the number N is equal to 4.
  • 21. The method of claim 16 wherein each of the instructions in the first set of instructions specifies one of the array locations in the register array; and wherein the respective tags are assigned to each of the instructions in the first set of instructions without regard to the specified array locations.
  • 22. The method of claim 16 wherein: the first set of instructions includes a first instruction and a second instruction, the first instruction preceding the second instruction in the program order;executing the instructions in the first set of instructions includes executing the second instruction before executing the first instruction; andstoring the result data in the temporary buffer includes storing the result data for the second instruction in the temporary buffer location identified by the tag assigned to the second instruction prior to storing the result data for the first instruction in the temporary buffer location identified by the tag assigned to the first instruction.
  • 23. The method of claim 16 further comprising: after retiring the instructions in the first set of instructions, concurrently reassigning the tags that were assigned to the instructions in the first set of instructions to instructions in a second set of instructions, the second set of instructions being subsequent to the first set of instructions in the program order.
  • 24. The method of claim 16 further comprising: prior to retiring the instructions in the first set of instructions, concurrently assigning a tag to each instruction in a second set of instructions, wherein the respective tag assigned to each of the instructions in the second set identifies one of the temporary buffer locations in a second one of the groups of temporary buffer locations.
  • 25. The method of claim 24 wherein each tag has a first portion that identifies one of the groups of temporary buffer locations and a second portion that identifies one of the temporary buffer locations within the group of temporary buffer locations identified by the first portion of the tag.
  • 26. The method of claim 25 wherein: the respective first portions of the respective tags assigned to the instructions in the first set of instructions are identical to each other, andthe respective second portions of the respective tags assigned to the instructions in the second set of instructions are identical to each other and different from the respective first portions of the respective tags assigned to the instructions in the first set of instructions.
  • 27. The method of claim 26 wherein: the respective second portions of the respective tags assigned to the instructions in the first set of instructions are different from each other,the respective second portions of the respective tags assigned to the instructions in the second set of instructions are different from each other, andthe respective second portion of each of the respective tags assigned to the instructions in the first set of instructions is identical to the respective second portion of exactly one of the respective tags assigned to the instructions in the second set of instructions.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 11/149,227, filed Jun. 10, 2005, still pending, which is a continuation of application Ser. No. 10/815,742, filed Apr. 2, 2004, now U.S. Pat. No. 6,920,548, which is a continuation of application Ser. No. 10/151,932, filed May 22, 2002, now U.S. Pat. No. 6,775,761, which is a continuation of application Ser. No. 09/631,640, filed Aug. 2, 2000, now U.S. Pat. No. 6,412,064, which is a continuation of application Ser. No. 09/009,412, filed Jan. 20, 1998, now U.S. Pat. No. 6,131,157, which is a continuation of application Ser. No. 08/481,146 filed Jun. 7, 1995, now U.S. Pat. No. 5,826,055, which is a continuation of application Ser. No. 07/877,451, filed May 1, 1992, now abandoned. The following patents are related to the subject matter of the present application and are incorporate by reference in their entirety herein: “Superscalar RISC Instruction Scheduling,” U.S. Pat. No. 5,497,499, issued Mar. 5, 1996; and “High Performance, Superscalar-Based Computer System with Out-of-Order Instruction Execution,” U.S. Pat. No. 5,539,911, issued Jul. 23, 1996.

US Referenced Citations (314)
Number Name Date Kind
3346851 Thornton et al. Oct 1967 A
3718912 Hasbrouck et al. Feb 1973 A
3771138 Celtruda et al. Nov 1973 A
3789365 Jen et al. Jan 1974 A
3913074 Homberg et al. Oct 1975 A
4034349 Monaco et al. Jul 1977 A
4128880 Cray, Jr. Dec 1978 A
4200927 Hughes et al. Apr 1980 A
4212076 Conners Jul 1980 A
4228495 Bernhard et al. Oct 1980 A
4296470 Fairchild et al. Oct 1981 A
4315308 Jackson Feb 1982 A
4315314 Russo Feb 1982 A
4410939 Kawakami Oct 1983 A
4434461 Puhl Feb 1984 A
4459657 Murao Jul 1984 A
4476525 Ishii Oct 1984 A
4482950 Dshkhunian et al. Nov 1984 A
4498134 Hansen et al. Feb 1985 A
4500963 Smith et al. Feb 1985 A
4532598 Shibyama et al. Jul 1985 A
4561051 Rodman Dec 1985 A
4574349 Rechtschaffen Mar 1986 A
4594655 Hao et al. Jun 1986 A
4597054 Lockwood et al. Jun 1986 A
4613941 Smith et al. Sep 1986 A
4626989 Torii Dec 1986 A
4644466 Saito Feb 1987 A
4648045 Demetrescu Mar 1987 A
4675806 Uchida Jun 1987 A
4714994 Oklobdzija et al. Dec 1987 A
4719569 Ludemann et al. Jan 1988 A
4722049 Lahti Jan 1988 A
4752873 Shonai et al. Jun 1988 A
4758948 May et al. Jul 1988 A
4766566 Chuang Aug 1988 A
4775927 Hester et al. Oct 1988 A
4791607 Igarashi et al. Dec 1988 A
4807115 Torng Feb 1989 A
4811208 Myers et al. Mar 1989 A
4814978 Dennis Mar 1989 A
4823201 Simon et al. Apr 1989 A
4829467 Ogata May 1989 A
4833599 Colwell et al. May 1989 A
4841453 Finlay et al. Jun 1989 A
4858105 Kuriyama et al. Aug 1989 A
4858116 Gillett, Jr. et al. Aug 1989 A
4881167 Sasaki et al. Nov 1989 A
4897810 Nix Jan 1990 A
4901228 Kodama Feb 1990 A
4901233 Liptay Feb 1990 A
4903196 Pomerene et al. Feb 1990 A
4916604 Yamamoto et al. Apr 1990 A
4924376 Ooi May 1990 A
4926323 Baror et al. May 1990 A
4928226 Kamada et al. May 1990 A
4942525 Shintani et al. Jul 1990 A
4945479 Rusterholz et al. Jul 1990 A
4964057 Yabe Oct 1990 A
4974154 Matsuo Nov 1990 A
4974155 Dulong et al. Nov 1990 A
4980817 Fossum et al. Dec 1990 A
4985825 Webb, Jr. et al. Jan 1991 A
4991078 Wilhelm et al. Feb 1991 A
4991081 Bosshart Feb 1991 A
4992938 Cocke et al. Feb 1991 A
5003462 Blaner et al. Mar 1991 A
5032985 Curran Jul 1991 A
5051925 Kadono et al. Sep 1991 A
5067069 Fite et al. Nov 1991 A
5072364 Jardine et al. Dec 1991 A
5089951 Iijima Feb 1992 A
5093783 Kitada Mar 1992 A
5097409 Schwartz et al. Mar 1992 A
5101341 Circello et al. Mar 1992 A
5109495 Fite et al. Apr 1992 A
5119485 Ledbetter, Jr. et al. Jun 1992 A
5120083 Stine Jun 1992 A
5125083 Fite et al. Jun 1992 A
5125092 Prener Jun 1992 A
5129067 Johnson Jul 1992 A
5133074 Chou Jul 1992 A
5133077 Karne et al. Jul 1992 A
5134561 Liptay Jul 1992 A
5136697 Johnson Aug 1992 A
5140682 Okura et al. Aug 1992 A
5142633 Murray et al. Aug 1992 A
5142634 Fite et al. Aug 1992 A
5148533 Joyce et al. Sep 1992 A
5148536 Witek et al. Sep 1992 A
5150309 Shaw et al. Sep 1992 A
5155843 Stamm et al. Oct 1992 A
5167026 Murray et al. Nov 1992 A
5167035 Mann et al. Nov 1992 A
5179530 Genusov et al. Jan 1993 A
5179673 Steely, Jr. et al. Jan 1993 A
5179689 Leach et al. Jan 1993 A
5185872 Arnold et al. Feb 1993 A
5185878 Baror et al. Feb 1993 A
5187796 Wang et al. Feb 1993 A
5193157 Barbour et al. Mar 1993 A
5197132 Steely, Jr. et al. Mar 1993 A
5197136 Kimura et al. Mar 1993 A
5201056 Daniel et al. Apr 1993 A
5214763 Blaner et al. May 1993 A
5214786 Watanabe et al. May 1993 A
5222223 Webb, Jr. et al. Jun 1993 A
5222240 Patel Jun 1993 A
5222244 Carbine et al. Jun 1993 A
5226125 Balmer et al. Jul 1993 A
5226126 McFarland et al. Jul 1993 A
5226166 Ishida et al. Jul 1993 A
5226170 Rubinfeld Jul 1993 A
5228136 Shimizu et al. Jul 1993 A
5230068 Van Dyke et al. Jul 1993 A
5233694 Hotta et al. Aug 1993 A
5237666 Suzuki et al. Aug 1993 A
5241636 Kohn Aug 1993 A
5249286 Alpert et al. Sep 1993 A
5251306 Tran Oct 1993 A
5255384 Sachs et al. Oct 1993 A
5261057 Coyle et al. Nov 1993 A
5261071 Lyon Nov 1993 A
5276899 Neches Jan 1994 A
5278963 Hattersley et al. Jan 1994 A
H1291 Hinton et al. Feb 1994 H
5283903 Uehara Feb 1994 A
5285527 Crick et al. Feb 1994 A
5287465 Kurosawa et al. Feb 1994 A
5287467 Blaner et al. Feb 1994 A
5291615 Okamoto Mar 1994 A
5293500 Ishida et al. Mar 1994 A
5301278 Bowater et al. Apr 1994 A
5303362 Butts, Jr. et al. Apr 1994 A
5303382 Buch et al. Apr 1994 A
5317720 Stamm et al. May 1994 A
5345569 Tran Sep 1994 A
5355457 Shebanow et al. Oct 1994 A
5355460 Eickemeyer et al. Oct 1994 A
5367660 Gat et al. Nov 1994 A
5371684 Iadonato et al. Dec 1994 A
5377339 Saito et al. Dec 1994 A
5127091 Horst Feb 1995 A
5388215 Baker et al. Feb 1995 A
5390355 Horst Feb 1995 A
5394351 Widigen et al. Feb 1995 A
5394515 Lentz et al. Feb 1995 A
5394529 Brown, III et al. Feb 1995 A
5398330 Johnson Mar 1995 A
5404470 Miyake Apr 1995 A
5404472 Kurosawa et al. Apr 1995 A
5430884 Beard et al. Jul 1995 A
5430888 Witek et al. Jul 1995 A
5436869 Yoshida Jul 1995 A
5440752 Lentz et al. Aug 1995 A
5442757 McFarland et al. Aug 1995 A
5446912 Colwell et al. Aug 1995 A
5448705 Nguyen et al. Sep 1995 A
5452426 Papworth et al. Sep 1995 A
5461715 Matsuo et al. Oct 1995 A
5471592 Gove et al. Nov 1995 A
5473764 Chi Dec 1995 A
5481685 Nguyen et al. Jan 1996 A
5481734 Yoshida Jan 1996 A
5487156 Popescu et al. Jan 1996 A
5488729 Vegesna et al. Jan 1996 A
5490280 Gupta et al. Feb 1996 A
5493687 Garg et al. Feb 1996 A
5497499 Garg et al. Mar 1996 A
5524225 Kranich Jun 1996 A
5539911 Nguyen et al. Jul 1996 A
5559951 Lentz et al. Sep 1996 A
5560032 Nguyen et al. Sep 1996 A
5560035 Garg et al. Sep 1996 A
5561775 Kurosawa et al. Oct 1996 A
5561776 Popescu et al. Oct 1996 A
5564056 Fetterman et al. Oct 1996 A
5564117 Lentz et al. Oct 1996 A
5566385 Iadonato et al. Oct 1996 A
5568624 Sites et al. Oct 1996 A
5574927 Scantlin Nov 1996 A
5574935 Vidwans et al. Nov 1996 A
5574941 Horst Nov 1996 A
5577200 Abramson et al. Nov 1996 A
5577217 Hoyt et al. Nov 1996 A
5584001 Hoyt et al. Dec 1996 A
5586278 Papworth et al. Dec 1996 A
5590295 Deosaran et al. Dec 1996 A
5592636 Popescu et al. Jan 1997 A
5604865 Lentz et al. Feb 1997 A
5604877 Hoyt et al. Feb 1997 A
5604912 Iadonato et al. Feb 1997 A
5606676 Grochowski et al. Feb 1997 A
5608885 Gupta et al. Mar 1997 A
5613132 Clift et al. Mar 1997 A
5615126 Deeley et al. Mar 1997 A
5615385 Fetterman et al. Mar 1997 A
5617554 Alpert et al. Apr 1997 A
5619664 Glew Apr 1997 A
5619668 Zaidi Apr 1997 A
5623628 Brayton et al. Apr 1997 A
5625788 Boggs et al. Apr 1997 A
5625837 Popescu et al. Apr 1997 A
5627983 Popescu et al. May 1997 A
5627984 Gupta et al. May 1997 A
5627985 Fetterman et al. May 1997 A
5628021 Iadonato et al. May 1997 A
5630075 Joshi et al. May 1997 A
5630083 Carbine et al. May 1997 A
5630149 Bluhm May 1997 A
5630157 Dwyer, III May 1997 A
5640588 Vegesna et al. Jun 1997 A
5651125 Witt et al. Jul 1997 A
5655098 Witt et al. Aug 1997 A
5664136 Witt et al. Sep 1997 A
5666494 Mote, Jr. Sep 1997 A
5682546 Garg et al. Oct 1997 A
5689672 Witt et al. Nov 1997 A
5689720 Nguyen et al. Nov 1997 A
5708841 Popescu et al. Jan 1998 A
5734584 Iadonato et al. Mar 1998 A
5737624 Garg et al. Apr 1998 A
5745375 Reinhardt et al. Apr 1998 A
5754800 Lentz et al. May 1998 A
5768575 McFarland et al. Jun 1998 A
5778210 Henstrom et al. Jul 1998 A
5797025 Popescu et al. Aug 1998 A
5802605 Alpert et al. Sep 1998 A
5809276 Deosaran et al. Sep 1998 A
5819101 Peleg et al. Oct 1998 A
5826055 Wang et al. Oct 1998 A
5831871 Iadonato et al. Nov 1998 A
5832205 Kelly et al. Nov 1998 A
5832292 Nguyen et al. Nov 1998 A
5832293 Popescu et al. Nov 1998 A
5838986 Garg et al. Nov 1998 A
5881275 Peleg et al. Mar 1999 A
5892963 Iadonato et al. Apr 1999 A
5896542 Iadonato et al. Apr 1999 A
5941979 Lentz et al. Aug 1999 A
5961629 Nguyen et al. Oct 1999 A
5974526 Garg et al. Oct 1999 A
6038653 Nguyen et al. Mar 2000 A
6038654 Nguyen et al. Mar 2000 A
6044449 Garg et al. Mar 2000 A
6047348 Lentz et al. Apr 2000 A
6083274 Iadonato et al. Jul 2000 A
6092176 Iadonato et al. Jul 2000 A
6092181 Nguyen et al. Jul 2000 A
6101594 Nguyen et al. Aug 2000 A
6128723 Nguyen et al. Oct 2000 A
6131157 Wang et al. Oct 2000 A
6138231 Deosaran et al. Oct 2000 A
6219763 Lentz et al. Apr 2001 B1
6249856 Garg et al. Jun 2001 B1
6256720 Nguyen et al. Jul 2001 B1
6272579 Lentz et al. Aug 2001 B1
6272617 Deosaran et al. Aug 2001 B1
6272619 Nguyen et al. Aug 2001 B1
6282630 Nguyen et al. Aug 2001 B1
6289433 Garg et al. Sep 2001 B1
6360309 Iadonato et al. Mar 2002 B1
6385634 Peleg et al. May 2002 B1
6401232 Iadonato et al. Jun 2002 B1
6408375 Deosaran et al. Jun 2002 B2
6412064 Wang et al. Jun 2002 B1
6418529 Roussel Jul 2002 B1
6611908 Lentz et al. Aug 2003 B2
6647485 Nguyen et al. Nov 2003 B2
6735685 Senter et al. May 2004 B1
6757808 Iadonato et al. Jun 2004 B2
6775761 Wang et al. Aug 2004 B2
6782521 Iadonato et al. Aug 2004 B2
6915412 Nguyen et al. Jul 2005 B2
6920548 Wang et al. Jul 2005 B2
6922772 Deosaran et al. Jul 2005 B2
6934829 Nguyen et al. Aug 2005 B2
6941447 Nguyen et al. Sep 2005 B2
6948052 Nguyen et al. Sep 2005 B2
6954844 Lentz et al. Oct 2005 B2
6959375 Nguyen et al. Oct 2005 B2
6970995 Deosaran et al. Nov 2005 B2
6986024 Nguyen et al. Jan 2006 B2
7028161 Nguyen et al. Apr 2006 B2
7043624 Iadonato et al. May 2006 B2
7051187 Garg et al. May 2006 B2
7162610 Nguyen et al. Jan 2007 B2
7174525 Iadonato et al. Feb 2007 B2
20010034823 Garg et al. Oct 2001 A1
20020059508 Lentz et al. May 2002 A1
20020083300 Deosaran et al. Jun 2002 A1
20020129324 Iadonato et al. Sep 2002 A1
20020194456 Deosaran et al. Dec 2002 A1
20030056086 Nguyen et al. Mar 2003 A1
20030056087 Nguyen et al. Mar 2003 A1
20030070060 Nguyen et al. Apr 2003 A1
20030079113 Nguyen et al. Apr 2003 A1
20030115440 Garg et al. Jun 2003 A1
20040024987 Lentz et al. Feb 2004 A1
20040054872 Nguyen et al. Mar 2004 A1
20040093482 Nguyen et al. May 2004 A1
20040093483 Nguyen et al. May 2004 A1
20040093485 Nguyen et al. May 2004 A1
20050228973 Wang et al. Oct 2005 A1
20060020773 Deosaran et al. Jan 2006 A1
20060041736 Garg et al. Feb 2006 A1
20060064569 Lentz et al. Mar 2006 A1
20060123218 Iadonato et al. Jun 2006 A1
20060149925 Nguyen et al. Jul 2006 A1
20070101103 Nguyen et al. May 2007 A1
20070106878 Nguyen et al. May 2007 A1
20070113047 Garg et al. May 2007 A1
20070113214 Iadonato et al. May 2007 A1
20080059770 Garg et al. Mar 2008 A1
Foreign Referenced Citations (32)
Number Date Country
0 170 284 Feb 1986 EP
0 213 843 Mar 1987 EP
0 241 909 Oct 1987 EP
0354585 Feb 1990 EP
0 378 195 Jul 1990 EP
0 454 636 Oct 1991 EP
0 515 166 Nov 1992 EP
0 533 337 Mar 1993 EP
2 190 521 Nov 1987 GB
57-57345 Apr 1982 JP
60-144830 Jul 1985 JP
61-40650 Feb 1986 JP
61107434 May 1986 JP
62-242243 Oct 1987 JP
63-192135 Aug 1988 JP
1-142831 Jun 1989 JP
1-199233 Aug 1989 JP
02-042534 Feb 1990 JP
H2-48732 Feb 1990 JP
2-118757 May 1990 JP
2-211534 Aug 1990 JP
2-224025 Sep 1990 JP
2-226342 Sep 1990 JP
3-35324 Feb 1991 JP
3218524 Sep 1991 JP
4054638 Feb 1992 JP
H4-96132 Mar 1992 JP
04-503582 Jun 1992 JP
5-197544 Aug 1993 JP
H6-19707 Jan 1994 JP
WO 8809035 Nov 1988 WO
WO 9120031 Dec 1991 WO
Related Publications (1)
Number Date Country
20070106880 A1 May 2007 US
Continuations (7)
Number Date Country
Parent 11149227 Jun 2005 US
Child 11642625 US
Parent 10815742 Apr 2004 US
Child 11149227 US
Parent 10151932 May 2002 US
Child 10815742 US
Parent 09631640 Aug 2000 US
Child 10151932 US
Parent 09009412 Jan 1998 US
Child 09631640 US
Parent 08481146 Jun 1995 US
Child 09009412 US
Parent 07877451 May 1992 US
Child 08481146 US