Patent Grant
9952869
Embodiments of the invention relate to methods and systems for predicting outcomes of branch instructions. In particular, embodiments of present invention relate to storing instructions from branch mis-predictions for use during subsequent branch mis-predictions.
A program may include a branch instruction at which, based on a branch condition, a process may proceed in one of multiple possible ways. For example, in a sequence of instructions, 1, 2, 3, 4, 5, where 5 is a branch instruction, instruction 5 may command the process to proceed sequentially to instructions 6, 7, 8, . . . or to jump ahead to instructions 100, 101, 102, . . . .
To avoid time delays, instructions are typically fetched from program memory ahead of time so that they are ready for use when they are needed in the processor pipeline. However, at a branch, the next instruction may be unknown until the branch instruction is executed. Therefore, subsequent instructions can not be fetched beforehand, thereby causing a time delay in the process pipeline.
To reduce such time delays, a branch predictor may be used to predict the outcome of a conditional branch. The predicted instructions at the branch are preemptively retrieved from program memory and temporarily stored in a program cache for easy access. A branch predictor may be static, using only the branch instructions themselves to determine the branch outcome or dynamic, also using historical statistics of the branch to determine the branch outcome.
However, branch predictors may perform poorly for some algorithms, e.g., predicting correctly at approximately 50% of branches and predicting incorrectly at approximately 50% of branches. Furthermore, some algorithms cannot benefit from dynamic branch prediction, e.g., when there is no correlation between a current branch decision and preceding branch decisions.
When a branch prediction is correct, the predicted instructions are immediately retrieved from the program cache. When the branch prediction is incorrect, the retrieved instructions are discarded and the processor must again retrieve the correct instructions from program memory using additional computational cycles. The additional computational cycles used to retrieve the correct instructions from program memory after a branch mis-prediction may be referred to as a branch mis-prediction penalty.
The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings. Specific embodiments of the present invention will be described with reference to the following drawings, wherein:
It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.
In the following description, various aspects of the present invention will be described. For purposes of explanation, specific configurations and details are set forth in order to provide a thorough understanding of the present invention. However, it will also be apparent to one skilled in the art that the present invention may be practiced without the specific details presented herein. Furthermore, well known features may be omitted or simplified in order not to obscure the present invention.
Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions utilizing terms such as “processing,” “computing,” “calculating,” “determining,” or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulates and/or transforms data represented as physical, such as electronic, quantities within the computing system's registers and/or memories into other data similarly represented as physical quantities within the computing system's memories, registers or other such information storage, transmission or display devices.
A branch instruction may refer to an instruction at which a process may proceed in one of multiple possible ways. Branch instructions may be conditional or unconditional. An unconditional branch instruction may be one in which the outcome is predetermined and subsequent instructions are known prior to processing the branch instruction. For example, an unconditional branch instruction may be to repeat an instruction loop a predetermined number of times and then jump to a latter instruction. A conditional branch instructions may be one in which the outcome is dependent on a condition. The condition is typically unknown before subsequent instructions are to be fetched. For example, in one scenario, the condition may only be known when the branch instruction is decoded.
When a branch instruction is encountered in a program, a processor may retrieve one or more instructions from a program memory that are predicted to follow the branch instruction. To retrieve instructions from the program memory, the processor may fetch the instructions, store them in a program cache, queue and dispatch the instructions. Then, to read the instructions, the processor may access a tag array, perform a tag compare, and access the program cache. This series of operations is typically extensive and power consuming. In conventional systems, when the branch prediction is incorrect and the wrong predicted instructions have been retrieved from the program memory, these instructions are discarded and the processor accesses the program memory again, repeating the extensive process to retrieve the correct instructions. Each time the branch prediction is incorrect, the processor may suffer a significant time delay and computational penalty, i.e., a mis-prediction penalty, in order to fetch the correct instruction from program memory.
In an embodiment of the invention, a system and method are provided for executing a conditional branch instruction. A branch predictor may predict one or more instructions. The predicted instructions may depend on the conditional branch instruction. A branch mis-prediction buffer may store correct instructions that were not predicted by the branch predictor during a branch mis-prediction.
In an embodiment of the invention, a system and method are provided for executing a conditional branch instruction. One or more correct instructions may be retrieved from a branch mis-prediction buffer during a branch mis-prediction. The branch mis-prediction buffer may store previously used instructions that were not predicted during a previous branch mis-prediction.
In an embodiment of the invention, a system and method are provided for storing instructions in a branch mis-prediction buffer. One or more predicted instructions that depend on a conditional branch instruction may be retrieved from program memory. A processor may determine that the one or more predicted instructions are incorrect. One or more correct instructions may be retrieved from program memory. The one or more correct instructions may be stored in the branch mis-prediction buffer.
Embodiments of the invention may include a local cache, e.g., a branch mis-prediction buffer (BMB), to store mis-predicted instructions. A mis-predicted instruction may refer to an instruction that, once the branch condition is known, is determined to be the correct instruction(s) succeeding the branch instruction, but which was not predicted by the branch predictor. During a mis-prediction, if the correct instruction is stored in the BMB, the instruction may be quickly retrieved from the BMB and not from program memory, resulting in a zero mis-prediction penalty. However, if the correct instruction is not stored in the BMB, the correct instruction may be retrieved from program memory and a mis-predict penalty may be incurred. However, according to embodiments of the invention, instead of discarding the mis-predicted instructions and wasting the computational effort used to fetch them, the mis-predicted instructions may be stored in the BMB for use during subsequent branches that may result in mis-predictions.
Reference is made to
Device 100 may include a computer device, cellular device, or any other digital device such as a cellular telephone, personal digital assistant (PDA), video game console, etc. Device 100 may include any device capable of executing a series of instructions to run a computer program.
Processor 1 may include a central processing unit (CPU), a digital signal processor (DSP), a microprocessor, a controller, a chip, a microchip, a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC) or any other integrated circuit (IC), or any other suitable multi-purpose or specific processor or controller.
Processor 1 may be coupled to data memory unit 2 via a data bus 4 and to program memory unit 3 via a program memory bus 5.
Program memory unit 3 typically stores a set of instructions and rules for running a computer program while data memory unit 2 typically stores data generated while operating the program instructions such as pre-generated (i.e. static) data and/or scratch pad (i.e. dynamic) data; however, other arrangements for storing instructions and data in a memory or memories may be used.
Program cache 10 may provide temporary storage for program instructions retrieved from program memory unit 3 so that the instructions are more accessible for use by program control unit 8. Program memory unit 3 may be a long term memory unit, while program cache 10 may be a short term memory unit. Data memory unit 2, program memory unit 3 and program cache 10 may include, for example, random access memory (RAM), dynamic RAM (DRAM), flash memory, cache memory, volatile memory, non-volatile memory or other suitable memory units or storage units. Data memory unit 2, program memory unit 3, and program cache 10 may be implemented as separate or integrated memory units. Data memory unit 2, program cache 10 and/or program memory unit 3 may be integrated (“on-chip”) or may be separate (i.e., “off-chip”). In one embodiment in which there is a multi-level memory or a memory hierarchy, program memory unit 3 may be off-chip and the program cache 10 and/or Data memory unit 2 may be on-chip, e.g., an L-1 cache (e.g., which may run at a different rate than the processor clock rate) or an L-2 cache (e.g., which is relatively more integrated than the L-1 cache and typically runs at the processor clock rate). Other or additional memory architectures may be used.
Processor 1 may include a program control unit 8. Program control unit 8 may request, retrieve, and dispatch instructions from program memory unit 3 and may be responsible, in general, for the program pipeline flow. Program control unit 8 may include a data memory controller (not shown) coupled to data memory bus 4, and a program memory controller (not shown) coupled to program memory bus 5 to retrieve data from data memory unit 2 and program memory unit 3, respectively.
Program control unit 8 may include a fetch unit 12, an interrupt unit 13, and a branch mechanism 14. Fetch unit 12 may retrieve or fetch program instructions from program memory unit 3 and save the instructions to program cache 10 until they are requested for use by program control unit 8. Fetch unit 12 may be used to fetch instructions to a local queue prior to dispatching the instructions. Branch mechanism 14 may detect branch instructions, predict the outcome of branch instructions, and based on the predicted outcome of branch instructions request subsequent instructions from program memory unit 3 via fetch unit 12. Interrupt unit 13 may interrupt a current process, e.g., to initiate another higher priority process.
Processor 1 may include a decode unit 6, a load/store unit 7, one or more register files 9, and an execution unit 11. Once instructions are dispatched by program control unit 8, decode unit 6 may decode the instructions. Processor 1 may use register files 9 to implement tags to efficiently access decoded instruction, e.g., in the same computational cycle as they are requested. Execution unit 11 may execute the instructions. Load/store unit 7 may perform load and store operations from/to data memory unit 2.
Processor 1 may execute, for example, the following sequential pipeline stages for each instruction:
Other or additional pipeline stages and operating device components may be used.
In a process comprising sequential instructions, instructions to be processed in future are known beforehand and fetch unit 12 may preemptively retrieve instructions so that each instruction is fetched before the processor is ready to dispatch the instruction. The fetched instructions are temporarily stored in program cache memory 10, and/or a local queue which is significantly faster to access than program memory 3.
However, instructions succeeding a conditional branch instruction may depend on a branch condition that is not yet known at the time the instructions are to be fetched. For example, the branch instruction may proceed to any of multiple different instructions or process paths depending on the outcome of the branch condition.
Branch mechanism 14 may identify whether or not an instruction is a branch instruction, for example, at the decode stage (D2) of processing the instruction. When an instruction is a branch instruction, if the correct one of multiple possible subsequent instructions is not known at the time when the instruction is to be retrieved, branch mechanism 14 may predict which instruction most likely succeeds the branch instruction. A branch target buffer (BTB) 16 may store data used to make the predictions. BTB 16 may be a buffer or temporary memory unit, which may be separate from, integrated with or part of program cache 10.
If the predicted branch instruction matches the actual branch instruction, the predicted instruction may be used and the branch mis-prediction penalty is zero.
However, if the predicted branch instruction does not match the actual branch instruction, the actual branch instruction may be fetched from program memory 3. Accordingly, each time branch mechanism 14 mis-predicts a branch outcome, the process may suffer a time delay and computational penalty of fetching the correct instruction from program memory 3, for example, 3 cycles (IF1 to D1). This time delay or number of cycles may vary for different processor 1 pipelines.
According to embodiments of the invention, once the correct instructions are retrieved from program memory 3 and used, instead of discarding the instructions and wasting the computational effort used to fetch them, the correct, though mis-predicted, branch instructions may be written, saved, and/or stored for later use in a branch mis-prediction buffer (BMB) 17. BMB 17 may accumulate correct branch instructions that were not predicted. Although the program incurs a one-time mis-prediction penalty to initially retrieve these instructions from program memory 3, by saving them for use during subsequent mis-predictions, the mis-prediction penalty for retrieving the same instructions may be avoided thereafter.
During the operation of the series of program instructions, in a first scenario, branch mechanism 14 predicts the correct instruction succeeding a branch instruction and the correct subsequent instructions has already been retrieved from program memory 3. The correct subsequent instruction may then be used. In this case, there is no mis-prediction and the mis-predict penalty is zero.
In a second scenario, branch mechanism 14 makes a mis-prediction and predicts the wrong instruction succeeding a branch instruction. Once the instruction succeeding a branch instruction is known, processor 1 may attempt to retrieve the instruction from BMB 17. Processor 1 may check if BMB 17 contains the mis-predicted instruction simultaneous to program control unit 8 fetching a new instruction from the program memory sub-system. Only later when the branch instruction is known does processor 1 select between the predicted and mis-predicted instruction. If the correct instruction was a mis-predicted instruction in a previous program branch, the instruction should already be stored in BMB 17. Accordingly, instead of retrieving the correct instructions from program memory 3, processor 1 may retrieve the correct instruction from BMB 17. Therefore, even for a branch mis-prediction, if the correct branch instruction was previously a correct mis-predicted instruction, the mis-predict penalty for retrieving instructions from program memory 3 may be zero. In contrast with the other methods, in which the mis-predict penalty is zero for correct predictions and non-zero (e.g., 3 computational cycles) for mis-predictions, according to embodiments of the invention, the mis-predict penalty is zero for both correct as well as incorrect branch predictions.
BMB 17 may store instructions that have been dispatched (at the D1 pipeline stage). Alternatively, instructions in BMB 17 may be stored in other stages of a pipeline process (e.g., IF2 or D2). BMB 17 may be relatively more accessible than program cache 10 because BMB 17 is typically smaller than program cache 10. BMB 17 may be physically integrated with branch mechanism 14.
Reference is made to
In
In
The upper-right cell (row 1, column 1) in the table shows an instruction labeled “Branch A,B.” The instruction Branch A,B may be an instruction in a sequence of instructions of a program. Instruction Branch A,B may be stored at a first address, e.g., denoted arbitrarily to be 101. Instruction Branch A,B may be a branch instruction, for example, providing instructions to proceed next to either instruction A or instruction B, but this is not known until the instruction is decoded (in operation D2). The next instruction following Branch A,B (e.g., after the three delay slots) may be determined by comparing the predicted and mis-predicted instructions and is typically only known after Branch A,B has completed pipeline stage E1. The example in the figure does not depend on a static prediction. As such, either of address A or B may be the next sequential address. Instruction A may be stored at a second address, e.g., denoted arbitrarily to be 201, and instruction B may be stored at a third address, e.g., denoted arbitrarily to be 301.
During the program process, instruction Branch A,B may enter the processor pipeline, e.g., in pipeline stage IF1 (row 1, column 4). In pipeline stage IF1, a processor may access a program memory address to locate instruction Branch A,B stored at address 101 in a program memory.
Instruction Branch A,B may proceed to the next sequential stages IF2 (row 1, column 5), D1 (row 1, column 6), and then D2 (row 1, column 7). In pipeline stage D2, a processor may decode instruction Branch A,B to detect that Branch A,B is a branch instruction. To detect a branch instruction in operation D2, e.g., 3 computational cycles may be used (IF1-D1). Delay slots (e.g., three slots, ds1, ds2, and ds3) may be used to delay the pipeline cycle until instruction Branch A,B is decoded.
A branch mechanism may determine that instruction Branch A,B is a branch instruction in operation D2 (row 1, column 7). A branch predictor predicts the branch to proceed to instruction A at address 201. Accordingly, instruction A may enter the processor pipeline, e.g., in pipeline stage IF1 (row 5, column 8) and may be fetched from program memory in the next pipeline stage IF2 (row 5, column 9).
While instruction A is accessed from program memory (row 5, column 8), the BMB may be simultaneously searched for non-predicted instruction B at address 301, e.g., by checking for a BMB cache tag matching the instruction B cache tag (row 15, column 8). In this scenario, address 301 (where instruction B resides) is found in the cache tag, and the tag compare asserts the hit flag (row 16, column 8). In one embodiment, the cache tag may be implemented in registers (e.g., not RAM) causing the hit flag to be available in the same computational cycle (corresponding to column 8). Since there is a hit in the cache (row 16, column 8), the BMB may proceed to extract instruction B data.
In the following computational cycle (corresponding to column 9), the cache address, corresponding to the tag where instruction B found a match, may be applied to the BMB. In the next cycle, instruction B may be retrieved from the BMB (row 19, column 10). Instructions may be stored in the BMB after they have been dispatched (in D1 pipeline stage for a previous branch instruction). Accordingly, after instruction B is read from the BMB (row 19, column 10), it may proceed to the decode stage D2 of the pipeline (row 14, column 11).
While instruction B is being retrieved from the BMB, the processor may continue to process instruction A and the instructions succeeding A, i.e., A+1, A+2, . . . under the assumption that the branch prediction is correct. If the branch prediction is correct then instruction B retrieved from the BMB is not used. Predicted instructions A, A+1, A+2, are typically processed at least until the branch condition is known.
While instruction Branch A,B completes the E1 pipeline stage (row 1, column 10), the branch condition may be known and therefore, the actual branch direction is known. The condition result, in this case, indicates that the predicted branch instruction A is wrong and therefore the process should proceed with instruction B instead. As a result, in the decode stage D2 of the next cycle (row 5, column 11), the processor replaces the input of instruction A with the correct branch instruction B from the BMB (row 14, column 11).
In the following two cycles, instructions B+1 and B+2 are read from the BMB (row 19, columns 11 and 12) and are used to replace instructions A+1 and A+2, respectively, in the decoding stage (row 14, columns 12 and 13). Instructions A, A+1, A+2 are replaced by B, B+1, B+2, respectively, in each sequential decode stage D2 (row 5, column 11), (row 6, column 12), and (row 7, column 13), indicated by D2→D2. Since the predicted instruction A (from program memory) and the non-predicted instruction B (from BMB) are both available and dispatched in the same computational cycle (corresponding to column 10), replacing predicted instruction A with non-predicted instruction B in a branch mis-prediction occurs without any computational penalty or time delay for the mis-prediction.
In
Branch mechanism may determine that instruction Branch A,B is a branch instruction in operation D2 (row 1, column 7). A branch predictor predicts the branch to proceed to instruction A at address 201. Accordingly, instruction A may enter the processor pipeline, e.g., in pipeline stage IF1 (row 5, column 8) and may be fetched from program memory in the next pipeline stage IF2 (row 5, column 9).
While instruction A is fetched from program memory (row 5, column 8), the BMB may be simultaneously searched for non-predicted instruction B at address 301, e.g., by checking for a BMB cache tag matching the instruction B cache tag (row 17, column 8). In this scenario, in contrast with
The processor may continue to fetch and dispatch instruction A and the instructions succeeding A, i.e., A+1, A+2, . . . under the assumption that the branch prediction is correct. If the branch prediction is correct, then the BMB cache miss (row 16, column 8) is inconsequential and there is no computational penalty for the cache miss.
When instruction Branch A,B completes the E1 pipeline stage (row 1, column 10), the branch condition may be known and therefore, the actual branch direction may be known. The condition result, in this case, may indicate that the predicted branch instruction A is wrong and therefore the process may “kill” instruction A and the instructions succeeding A, i.e., A+1, A+2, . . . (column 10, rows 5, 6, and 7, respectively) before they are decoded in the D2 decoding stage.
As a result, the input of the decode stage D2 should be the correct branch instruction B from the BMB. However, since instruction B was not found in the BMB, there is no input for the decode stage D2 until instruction B is obtained, e.g., for 3 computational cycles (row 16, columns 8, 9, and 10).
The processor may fetch the instruction B from program memory (row 8, column 11). Address 301 of instruction B may be written as a tag in the BMB (row 17, column 13) in preparation for instructions B, B+1, B+2 to be stored in the BMB (row 19, columns 13, 14, 15, respectively).
Each of instructions B, B+1, B+2 may be fetched (rows 8, 9, 10, respectively, columns 12, 13, 14, respectively) and dispatched. The dispatched instruction packets B, B+1, B+2 may be written to the BMB at a BMB address (row 20, columns 13, 14, 15, respectively), e.g., placed in the BMB based on, for example, a least recently used (LRU) replacement policy. The same dispatched instruction packets B, B+1, B+2 may simultaneously enter the dispatch pipeline stage D1 (rows 8, 9, 10, respectively, columns 13, 14, 15, respectively). In the following computational cycle, the processor may decode the dispatched instruction packets B, B+1, B+2 in the D2 stage (rows 8, 9, 10, respectively, columns 14, 15, 16, respectively).
Accordingly, during a branch mis-prediction, the branch instructions that were not predicted may be stored in the BMB, e.g., if they have not already been stored. In this way, the processor may fill the BMB with correct branch instructions, which were erroneously not predicted. Once stored in the BMB, these branch instructions may be used during future branch mis-predictions, as described in reference to
Since the correct branch instruction B was not retrieved from program memory (i.e., only the incorrect predicted instruction A was retrieved) nor was the instruction available in the BMB (it was never the branch in a previous mis-prediction), the processor may retrieve instruction B from program memory sub-system (row 8, columns 11, 12, and 13). Retrieving instruction B from program memory sub-system may use additional, e.g., three, computational cycles and thus, the program process may incur a mis-prediction penalty.
In embodiments described above, the dispatched instructions A and B may be available in the same cycle, e.g., in
Although in the embodiments described above, processor 1 stores instructions in the BMB after they have been dispatched (in D1 pipeline stage), in an alternate embodiment, processor 1 may store instructions at any other or additional stage of a pipeline process.
In the embodiments above, during a branch mis-prediction, the BMB stores the correct un-predicted branch instruction. Alternatively, or additionally, during a correct branch prediction, the BMB or a separate memory unit may store the correct predicted branch instruction.
Furthermore, the BMB or a separate memory unit may store statistical data corresponding to each instruction entry in the BMB. The statistical data may include, for example, usage history data such as the computational cycle in which the instruction is used (e.g., for ordering the instructions based on which instruction was least or most recently used), the rate or number of times the instruction was mis-predicted (e.g., for determining whether or not to store the instruction in the BMB or for ordering the instructions in the BMB based on a total or average usage of the instruction), the size of the instruction (e.g., for ordering the instructions based on the size of the instruction), etc.
In one embodiment of the invention, BMB 17 may store mis-predictions for branches that have a mis-prediction rate that is greater than a predetermined threshold. The threshold may be automatically predetermined to satisfy computational efficiency parameters of a computing platform, e.g., based on the success or usage history of instructions stored in BMB 17 for each branch or process versus the memory and computational costs of storing instructions in BMB 17. Alternatively, the predetermined threshold may be manually or semi-automatically set by a programmer e.g., to be greater than 30-50%. If the mis-prediction rate is sufficiently small or less than a predetermined threshold for a specific branch or process, the processor may not store mis-predicted instructions for that branch or process. For example, if an average reduction in the branch mis-prediction penalty for the branch or process is, e.g., less than a specified number of cycles, mis-predicted instructions may not be stored in BMB 17.
In one embodiment of the invention, branch mechanism 14 may predict instructions partially or completely based on which instructions supplement the instructions already stored in BMB 17 instead of instructions that are statistically most likely to occur. For example, branch mechanism 14 may search BMB 17, look for any of the potential unknown branch instructions stored and if any is already stored in BMB 17, the branch prediction unit may predict, or be statistically more likely to predict, the instruction not stored in BMB 17. In this way, processor 1 will retrieve instructions from program memory 3 such that the instructions are new or not redundant to those already stored in BMB 17.
When a program is initiated and there have been no mis-predictions, BMB 17 may be empty. As a program is run, for each (or alternatively, for only some) branch mis-predictions, the mis-predicted instruction may be added to fill BMB 17. BMB 17 may have a fixed or maximum size, e.g., determined by a programmer, or a variable size, e.g., determined automatically based on BMB 17 usage history. The smaller the size of BMB 17, the more efficient its usage. However, the larger the size of BMB 17, the greater the number of instructions that may be stored.
During a mis-prediction, conventional processors fetch the correct mis-predicted instructions from a program memory. The processors then store the instructions in a program cache where they are queued and dispatched. In order to access the instructions, the processor accesses a tag array, performs a tag compare, and accesses the program cache to read the instructions. This process consumes a relatively large amount of processor power. In particular, for example, when large data packets are used, such as “very long instruction word” (VLIW) packets, a VLIW processor retrieves and stored the VLIW packets in a queue or buffers the packets so that they may be issued. After being issued, the VLIW packet are dispatched to the execution units, and only after being dispatched may they be decoded and executed. In conventional systems, this extensive series of operations is executed each and every time there is a branch mis-prediction. According to embodiments of the inventions, even when there is a branch mis-prediction, if the correct instruction was previously mis-predicted, the correct instruction is already stored in BMB 17. Therefore, the correct instruction may be quickly retrieved from BMB 17 and the aforementioned extensive series of operations may be eliminated, e.g., wholly or at least partially.
Embodiments of the invention include a system and method for using BMB 17 as a loop buffer. BMB 17 may be dedicated to storing loop instructions so that they may be accessed locally rather than from program memory 3. Since loop instructions may be used more often than other non-repeating instructions that are not part of a loop sequence, storing the loop instructions locally in BMB 17 rather than in program memory 3 may reduce power consumption used to access program memory 3 and queue and align/dispatch the instructions more so than for other non-repeating instructions.
The branch loop instruction, “brloop_write,” (row 1, column 1) indicates the number, n, of instruction packets (e.g., n=6) in an instruction loop. The instruction “nop” indicates no-operation due to latency in the processor pipeline. Processor 1 may use instructions (e.g., chip_select and write_enable instructions) to write the first, n−1, instruction packets of the instruction loop to BMB 17. BMB 17 may include a dedicated register (e.g., brloop_last_ir_r) to which the last, nth, instruction packet in the loop is written. While the last instruction packet in the loop is being written to the dedicated register, it is know that there are no more instructions in the loop, and the first instruction packet in the loop may be automatically and simultaneously retrieved from BMB 17.
To write instructions to BMB 17, when the number-of-packets is decoded (row 1, column 6), processor 1 may update one or more registers in BMB 17 to allow that number (e.g., n=6) of instruction packets to be written to respective entries of BMB 17 (row 30, columns 7-12). Using the tag address instruction (row 27), the BMB 17 tag array may be updated, while the BMB 17 cache array may be updated using the cache index instruction (row 30). Each BMB 17 entry may hold one or more (e.g., four) instruction packets. For example, the first BMB 17 entry may be filled with the first four instruction packets in the loop A1-A4 (row 30, columns 7-10). A corresponding tag address may be written to BMB 17 (row 27, column 7) for each BMB 17 entry. If the instruction loop includes more than four instructions, then processor 1 may update BMB 17 registers to find the next BMB 17 entry to be filled with the next (up to) four instruction packets A5 (row 30, column 11), and accordingly write the corresponding tag address (row 28, column 11). Processor 1 continues this process until all but the last instruction A6 is written to BMB 17 (row 30, column 11). Processor 1 may perform a tag compare for every fourth instruction to find the address of the next BMB 17 entry (row 28, column 12) to retrieve instructions from BMB 17 (row 31, columns 13, 14, . . . ).
In some embodiments of the invention, instructions are written to BMB 17 in an order based on a least recently used (LRU) algorithm. BMB 17 may include registers and corresponding entries that are ordered based on a LRU algorithm.
The branch loop (brloop) instruction A4 (row 6, column 1) (with two delay slots A5 and A6—rows 7 and 8, column 1) may be predicted taken or not-taken The predicted-taken address 102 may be written to a “not predicted branch target address” or “PTADDR_R” register (row 43, column 12) and used to search the tag array of BMB 17 (row 26, column 12). When the branch loop instruction A4 is taken, loop instructions may be accessed from BMB 17 instead of from program memory 3 to reduce power consumption. The not-taken address 108 is typically only used at the end of the last loop iteration or on an exit condition where the branch is predicted incorrectly. The last loop of the iteration (row 25, column 26) may be where there is an exit condition or where branch is predicted incorrectly.
Interrupt unit 13 may interrupt a current process (not shown), e.g., to initiate another process, often damaging partially processed branch instruction data. Interrupt unit 13 may be disabled while processor 1 writes loop instructions to BMB 17. Interrupt unit 13 may also be disabled while processor 1 reads instructions from BMB 17. In one exception, interrupts may be allowed while reading the last instruction packet, e.g., in each iteration of an instruction loop. If such an interruption is accepted then, if a branch instruction is taken then the return register may be written with the program address in the PTADDR_R register (row 43, columns 12, 18, 24), and if the branch is not-taken then the return register may be written with the program address from the program counter or “pseq_pc”. BMB 17 may be locked, to allow a programmer to control replacement of BMB 17 entries.
The status of the loop buffer may be tracked by indicators, flags, or other markers. A “buf_valid” flag may be set when all of the instructions in the loop are written and/or available in BMB 17. The buf_valid flag may be cleared when any of the loop instructions are replaced in BMB 17. A “buf_active” flag may be set when processor 1 accesses instructions from BMB 17. The buf_active flag may be set after encountering a brloop_write instruction and loop instructions are written to BMB 17. The buf_active flag may be cleared when a branch is taken or when a call or interruption is encountered.
The status of the loop buffer may be indicated by different flag combinations. For example, buf_valid and buf_active may indicate each of the following four different states:
During the first iteration of the loop, the instructions are executed and simultaneously written to BMB 17. During subsequent iterations the instructions are accessed from BMB 17, while program memory 3, queue, and dispatcher are idle. At the end of the last iteration, program memory 3, queue, and dispatcher begin operating on the next sequentially instruction packet that comes after the loop, e.g., address 108, 109, 110, . . . .
BMB 17 may include a buffer, cache or other memory structure that stores mis-predicted or loop instructions in a separate cache for access during subsequent mis-predictions or iterations of the loop. BMB 17 typically does not rely on the history of branch outcomes to make future predictions, thereby overcoming the limitations of both static and dynamic branch prediction techniques. In alternate embodiments, BMB 17 may wholly or partially take into account branch prediction histories to make future predictions.
BMB 17 typically does not rely on software directives. However, in some embodiments, software directives may be used to pre-load instructions into BMB 17. BMB 17 may be fully or partially transparent to a programmer. BMB 17 may use a fully or partially associative cache to store instructions at the branch target address. These instructions may be automatically retrieved during an instruction loop or when a branch predictor predicts incorrectly (e.g., achieving zero overhead during branch mis-predictions).
Reference is made to
In operation 500, a processor may decode a conditional branch instruction.
In operation 510, a branch prediction unit may predict the subsequent instruction(s) following the branch.
In operation 520, a fetching unit may retrieve the predicted instruction(s) from program memory.
In operation 525, the processor may retrieve a non-predicted instruction from the branch mis-prediction buffer (BMB), e.g., by checking for a BMB cache tag matching the instruction cache tag. Operations 520 and 525 may be run substantially simultaneously, e.g., in the same clock cycle.
In operation 530, the processor may execute the branch instructions and determine the actual subsequent instruction(s) following the branch.
In operation 540, the processor may compare the actual subsequent instruction(s) following the branch with the predicted instruction(s) retrieved from program memory. If the actual instruction(s) match the predicted instruction(s), a process may proceed to operation 550. If the actual instruction(s) do not match the predicted instruction(s), a process may proceed to operation 560.
In operation 550, the processor may decode the predicted instruction(s) retrieved from program memory.
In operation 560, the processor may decode the non-predicted instruction(s) retrieved from the BMB.
If the non-predicted instruction was not found in the BMB and therefore, not retrieved in the BMB in operation 525, and the actual instruction(s) determined in operation 530 do not match the predicted instruction(s) retrieved from program memory in operation 520, a process may proceed to operation 570.
In operation 570, the processor may retrieve the non-predicted instructions from program memory, decode the instructions and write the instruction to the BMB.
Other operations or series of operations may be used.
Embodiments of the invention may include an article such as a computer or processor readable medium, or a computer or processor storage medium, such as for example a memory, a disk drive, or a USB flash memory, encoding, including or storing instructions which when executed by a processor or controller, carry out methods disclosed herein.
Although the particular embodiments shown and described above will prove to be useful for the many distribution systems to which the present invention pertains, further modifications of the present invention will occur to persons skilled in the art. All such modifications are deemed to be within the scope and spirit of the present invention as defined by the appended claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3940741 | Horikoshi et al. | Feb 1976 | A |
| 4725947 | Shoni et al. | Feb 1988 | A |
| 5734881 | White et al. | Mar 1998 | A |
| 5850542 | Schroter et al. | Dec 1998 | A |
| 5961637 | Sturges et al. | Oct 1999 | A |
| 7197630 | Alsup et al. | Mar 2007 | B1 |
| 7620804 | Kuo | Nov 2009 | B2 |
| 7836287 | Doing et al. | Nov 2010 | B2 |
| 20020087852 | Jourdan et al. | Jul 2002 | A1 |
| 20030023838 | Karim et al. | Jan 2003 | A1 |
| 20030135722 | Johnson | Jul 2003 | A1 |
| 20080086621 | Ogura | Apr 2008 | A1 |
| Number | Date | Country |
|---|---|---|
| 01-106141 | Apr 1989 | JP |
| WO 9904335 | Jan 1999 | WO |
| Entry |
|---|
| European Search Report for Application No. EP 10 18 9135 Date of completion Jan. 12, 2011. |
| Number | Date | Country | |
|---|---|---|---|
| 20110107071 A1 | May 2011 | US |
