MICROPROCESSOR INCLUDING MULTIPLE REGISTER FILES OCCUPYING THE SAME LOGICAL SPACE

Abstract: A microprocessor (10) includes a first register file (44) including a plurality of multimedia registers defined to store operands for multimedia instructions and a second register file (42) including a plurality of floating point registers defined to store operands for floating point instructions. The multimedia registers and floating point registers are mapped to the same logical storage according to the instruction set employed by the microprocessor. In order to maintain predefined behavior when a floating point instruction reads a register most recently updated by a multimedia instruction or vice versa, the microprocessor provides for synchronization of the first and second register files between executing a set of one or more multimedia instructions and a set of one or more floating point instructions. The microprocessor supports an empty state instruction. If the empty state instruction is included between the set of one or more multimedia instructions and the set of one or more floating point instructions in a code sequence, the microprocessor inhibits the register file synchronization.

Description: TITLE: MICROPROCESSOR INCLUDING MULTIPLE REGISTER FILES OCCUPYING THE SAME LOGICAL SPACE . BACKGROUND OF THE INVENTION 1. Technical Field This invention is related to the field of microprocessors and, more particularly, to microprocessors having multiple register files which map to the same logical storage. 2. Background Art Microprocessors are often configured to operate upon a variety of data types in order to provide computational solutions to a wide range of problems. For example, integer and floating point data types are common. The integer data type may be used in the case where the values to be operated upon are of approximately the same magnitude (as well as any intermediate results calculated in order to produce the results of interest). On the other hand, if the magnitudes of the values to be operated upon (or the intermediate results) are expected to vary widely, then the floating point data type may be more appropriate. The data type used by each instruction within the instruction set is typically predefined as part of the instruction definition. For example, integer instructions are instructions which are defined to operate upon the integer data type. Similarly, floating point instructions are defined to operate upon the floating point data type. Generally, an instruction is the most basic operation which the programmer can specify in order to direct the microprocessor to perform a desired function. By arranging instructions in a particular order, the programmer may accomplish a specific objective. Instructions may be grouped with other instructions to form different instruction types according to the data type upon which they are defined to operate. Typically, an instruction is defined to receive one or more operands upon which to perform an operation (the "source operands") and is defined to store the result (the "destination operand"). The term "instruction set", as used herein, refers to a group of instructions defined via a particular processor architecture. Each instruction is assigned a unique encoding which identifies that instruction unambiguously from other instructions within the instruction set. As advances in semiconductor fabrication processes have been developed, it has become possible to increase the number of transistors which can be included upon a single chip and to increase the operating frequencies of the chips. Accordingly, microprocessors have been able to increase performance through increased operating frequencies (i.e. shorter clock cycles) as well as through advanced microarchitectures made possible by the increase in available transistors. One way to take advantage of the increase in available transistors is to add new data types to the microprocessor. The new data types may be specifically designed with a particular task in mind. The data type, and the instructions defined to operate upon the data type, may be optimized for the particular task. For example, the x86 instruction set has recently been expanded in this fashion. While previous microprocessors which implement the x86 instruction set (e.g. the 80486 from Intel Corporation and the 5 K 86 from Advanced Micro Devices, Inc.) generally execute instructions specifying the floating point and integer data types, the most recent microprocessors implementations also execute instructions specifying the MMX data type. The MMX data type is a 64 bit operand treated as a set of packed integers. The packed integers may be eight 8 bit integers, four 16 bit integers, or two 32 bit integers. The MMX data type and instructions which use the data type are optimized for video and audio data manipulations. Audio and/or video manipulation is referred to herein as "multimedia manipulation". These types of operations have become more important as computer systems have employed more advanced graphical user interfaces via the operating systems and application programs installed thereon. Additionally, the audio capabilities of computer systems have been enhanced. More particularly, the MMX data type allows for the same operation to be performed upon each of the integer values within the packed integer. Fewer instructions may be employed to perform the desired manipulations then would have otherwise been required, since one instruction may operate upon multiple values. For many video and/or audio computing tasks, the same operation is applied to a large number of data elements arranged for display or playback, and therefore instructions which perform the same operation upon multiple data elements may be advantageous. In order to minimize the impact upon operating systems designed for the x86 architecture prior to the addition of the MMX data type and instructions, the registers defined to store the MMX operands are defined to be shared with the floating point registers. In other words, the MMX registers are architecturally defmed to use the same logical storage locations as the floating point registers. In this manner, no new state is added to the microprocessor. Operating systems which do not recognize MMX instructions may still operate properly, as the data being used by the MMX instructions is stored in the same set of registers as the floating point data. Since these operating systems were already handling the floating point registers, the MMX registers are automatically handled. The sharing of registers between data types may be advantageous for operating system compatibility, but creates additional hardware problems for microprocessors supporting the new data type and instructions. While it is generally illogical to store a value of one data type in a shared register and then use the shared register as a source operand for an instruction operating upon a different data type, it is desirable to provide defined behavior in such situations. In order to maintain compatibility with software written using the new data types, it is desirable to maintain this defined behavior when designing microprocessors which implement the architecture. It is also desirable to maintain this behavior with a minimal impact upon the performance of the microprocessors. DISCLOSURE OF INVENTION The problems outlined above are in large part solved by a microprocessor in accordance with the present invention. The microprocessor includes a first register file including a plurality of multimedia registers defined to store operands for multimedia instructions and a second register file including a plurality of floating point registers defined to store operands for floating point instructions. The multimedia registers and floating point registers are mapped to the same logical storage according to the instruction set employed by the microprocessor. In order to maintain predefined behavior when a floating point instruction reads a register most recently updated by a multimedia instruction or vice versa, the microprocessor provides for synchronization of the first and second register files between executing a set of one or more multimedia instructions and a set of one or more floating point instructions (where either set may be prior to the other in program order and the order affects which direction copying of the contents is performed, i.e. first register file to second register file or vice versa). Advantageously, synchronization of the register files is automatically performed. The predefined behavior in the above mentioned circumstances is thereby maintained. In order to support higher performance in cases for which the predefined behavior is not needed, the microprocessor supports an empty state instruction. If the empty state instruction is included between the set of one or more multimedia instructions and the set of one or more floating point instructions in a code sequence, the microprocessor inhibits the register file synchronization. Since the register file synchronization is not performed, the delay associated with the synchronization is circumvented. Advantageously, more efficient code execution may be realized. In one embodiment including the x86 instruction set, the empty state instruction performs the same set of actions as the EMMS instruction in addition to the above mentioned features. By providing register file synchronization and the empty state instruction, compatibility with software expecting the predefined behavior is maintained while allowing software not needing the predefined behavior the flexibility not to have the register file synchronization. Broadly speaking, the present invention contemplates a microprocessor comprising a decode unit, a first register file, a second register file, a first execution unit, and a second execution unit. The decode unit is configured to decode instructions defined within an instruction set including a first type of instructions, a second type of instructions, and an empty state instruction. Additionally, the instruction set defines that a first plurality of registers accessible via the first type of instructions and a second plurality of registers accessible via the second type of instructions are mapped onto a logical storage in which each of the first plurality of registers is assigned to a logical storage location to which a corresponding one of the second plurality of registers is assigned. The first register file includes physical storage locations corresponding to the first plurality of registers. Similarly, the second register file includes physical storage locations corresponding to the second plurality of registers. Coupled to the first register file, the first execution unit is configured to execute instructions of the first type. Additionally, the first execution unit is configured to read operands for the instructions of the first type from the first register file. Similarly, the second execution unit is coupled to the second register file and is configured to execute instructions of the second type. The second execution unit is configured to read operands for the instructions of the second type from the second register file. The decode unit is configured to inhibit a synchronization of the first register file and the second register file between an execution of the first instruction and an execution of the second instruction upon decoding a first instruction sequence including a first instruction of the first type, the empty state instruction, and the second instruction of the second type. The present invention ftirther contemplates a method for executing instructions defined within an instruction set including a first type of instructions, a second type of instructions, and an empty state instruction. The instruction set further defines that a first plurality of registers accessible via the first type of instructions and a second plurality of registers accessible via the second type of instructions are mapped onto a logical storage in which each of the first plurality of registers is assigned to a logical storage location to which a corresponding one of the second plurality of registers is assigned. A first operand for a first instruction of the first type is read from a first register file including physical storage locations for each of the first plurality of registers. A second operand for a second instruction of the second type is read from a second register file including physical storage locations for each of the second plurality of registers. The first register file and the second register file are synchronized between reading the first operand and reading the second operand if the empty state instruction is not included between the first instruction and the second instruction in an instruction sequence. A synchronization of the first register file and the second register file is inhibited if the empty state instruction is included between the first instruction and the second instruction in the instruction sequence. Moreover, the present invention contemplates a microprocessor comprising a first register file and a second register. The first register file includes physical storage locations corresponding to a first plurality of registers. Similarly, the second register file includes physical storage locations corresponding to a second plurality of registers. The microprocessor is configured to execute instructions defined within an instruction set including a first type of instructions, a second type of instructions, and an empty state instruction, wherein the instruction set further defines that a first plurality of registers accessible via the first type of instructions and a second plurality of registers accessible via the second type of instructions are mapped onto a logical storage in which each of the first plurality of registers is assigned to a logical storage location to which a corresponding one of the second plurality of registers is assigned. Additionally, the microprocessor is configured to inhibit a synchronization of the first register file and the second register file subsequent to executing a first instruction of the first type and prior to executing a second instruction of the second type responsive to a first instruction sequence including the first instruction and the second instruction also including the empty state instruction. The present invention still further contemplates a computer system, comprising a microprocessor, a memory, and an I/O device. The microprocessor includes a first register file including physical storage locations corresponding to a first plurality of registers and a second register file including physical storage locations corresponding to a second plurality of registers. The microprocessor is configured to execute instructions defined within an instruction set including a first type of instructions, a second type of instructions, and an empty state instruction, wherein the instruction set further defines that a first plurality of registers accessible via the first type of instructions and a second plurality of registers accessible via the second type of instructions are mapped onto a logical storage in which each of the first plurality of registers is assigned to a logical storage location to which a corresponding one of the second plurality of registers is assigned. Furthermore, the microprocessor is configured to inhibit a synchronization of the first register file and the second register file subsequent to executing a first instruction of the first type and prior to executing a second instruction of the second type responsive to an instruction sequence including the first instruction and the second instruction also including the empty state instruction. Coupled to the microprocessor, the main memory is configured to store the instruction sequence and to provide the instruction sequence to the microprocessor upon request therefrom for the instruction sequence. Coupled to the main memory, the I/O device is configured to transfer data between the main memory and a second computer system coupled to the I/O device. BRIEF DESCRIPTION OF DRAWINGS Other objects and advantages of the invention will become apparent upon reading the following detailed description and upon reference to the accompanying drawings in which: Fig. 1 is a block diagram of one embodiment of a microprocessor. Fig. 2 is a block diagram of one embodiment of a decode unit shown in Fig. 1. Fig. 3 is a state machine diagram illustrating operation of one embodiment of a decode unit shown in Fig. 2. Fig. 4 is a flow chart illustrating steps performed in a microcode sequence implementing a portion of the state machine shown in Fig. 3 according to one embodiment of the decode unit shown in Fig. 2. Fig. 5 is a diagram illustrating a subroutine hierarchy and exemplary use of the fast empty state instruction. Fig. 6 is a block diagram of one embodiment of a computer system including the microprocessor shown in Fig. 1. While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the present invention as defined by the appended claims. MODE(S) FOR CARRYING OUT THE INVENTION Turning now to Fig. 1, a block diagram of one embodiment of a microprocessor 10 is shown. Other embodiments are possible and contemplated. In the embodiment of Fig. 1, microprocessor 10 includes a predecode logic block 12 coupled to an instruction cache 14 and a predecode cache 15. Caches 14 and 15 also include an instruction TLB 16. A cache controller 18 is coupled to predecode logic block 12, instruction cache 14, and predecode cache 15. Controller 18 is additionally coupled to a bus interface unit 24, a level-one data cache 26 (which includes a data TLB 28), and an L2 cache 40. Microprocessor 10 further includes a decode unit 20, which receives instructions from instruction cache 14 and predecode data from predecode cache 15. This information is forwarded to execution engine 30 in accordance with input received from a branch logic unit 22. Execution engine 30 includes a scheduler buffer 32 coupled to receive input from decode unit 20. Scheduler buffer 32 is coupled to convey decoded instructions to a plurality of execution units 36A-36E in accordance with input received from instruction control unit 34. Execution units 36A-36E include a load unit 36A, a store unit 36B, and register X unit 36C, and register Y unit 36D, and a floating point unit 36E. Load unit 36A receives input from data cache 26, while store unit 36B interfaces the data cache 26 via a store queue 38. Elements referred to herein with a reference number followed by a letter will be collectively referred to by the reference number alone. For example, execution units 36A-36E will be collectively referred to as execution units 36. As shown in Fig. 1, register units 36C-36D are coupled to a register file 44, from which register units 36C-36D are configured to read source operands and to which register units 36C-36D are configured to store destination result values. Floating point unit 36E is also shown as including a register file 42. Register file 42 includes physical storage locations assigned to each of the architected floating point registers. Register file 44 also includes physical storage locations assigned to each of the architected floating point registers. Floating point instructions are executed by floating point unit 36E, which reads source operands from register file 42 and updates destinations within register file 42 as well. Register units 36C-36D execute integer instructions, reading source operands from register file 44 and updating destinations within register file 44. However, the integer registers are logically separate (i.e. architecturally defined to be separate storage locations) from the floating point registers. Additionally, register units 36C-36D are configured to execute multimedia instructions, which in the present embodiment are defined to read source operands from multimedia registers which are logically the same storage locations as the floating point registers. Therefore, the physical storage locations corresponding to multimedia registers within register file 44 are logically the same as the physical storage locations within register file 42. As used herein, the term multimedia instruction refers to the above described packed integer operations (e.g. operations such as those defined by the MMX instructions within the x86 instruction set). Furthermore, the term multimedia instructions may refer to floating point instructions optimized for three dimensional graphics calculations. These instructions may be defined to operate, for example, on two 32-bit floating point numbers packed into a given floating point register. Because separate sets of physical storage locations within register files 42 and 44 are mapped to one set of logical storage locations (i.e. the architected floating point registers), microprocessor 10 supports synchronization of register files 42 and 44 in order to allow predictable behavior when: (i) a floating point instruction uses a register as a source operand, and the most recent update to the register was performed in response to a multimedia instruction; and (ii) a multimedia instruction uses a register as a source operand, and the most recent update to the register was performed in response to a floating point instruction. However, the register file synchronization is a relatively slow process. Generally, synchronizing register files 42 and 44 involves copying the contents of each physical storage location within one of the register files which represents a register logically shared between multimedia instructions and floating point instructions into the other register file. The direction of the copy (i.e. from register file 42 to register file 44 or from register file 44 to register file 42) depends upon which type of instructions (floating point or multimedia) have recently been executed. As used herein, the term "logical storage location" refers to a storage location (e.g. a register) which is architecturally defined to exist. In other words, the instruction set definition defines the storage location, and instructions can specify the storage location as an operand via various encodings of the instruction. On the other hand, a "physical storage location" refers to a storage location actually implemented by microprocessor 10. A logical storage location is "mapped" to a particular physical storage location if an instruction coded to access the logical storage location results in an access to the particular physical storage location. As mentioned above, synchronizing register files 42 and 44 is a relatively slow process. Accordingly, synchronizing register files 42 and 44 may unduly limit the performance of microprocessor 10. As noted previously, it is generally illogical for a floating point instruction to use multimedia results as a source operand, and vice versa. Microprocessor 10 defines an empty state instruction which can be used to indicate that a particular instruction sequence is not relying on synchronization between multimedia register updates and floating point register updates. If the empty state instruction is used in an instruction sequence, microprocessor 10 inhibits the synchronization of register files 42 and 44. In this fashion, code sequences which do not require synchronization may be executed more rapidly by microprocessor 10, and therefore may achieve a higher performance level than would otherwise be possible. In one embodiment, microprocessor 10 employs the x86 instruction set and the empty state instruction performs the operations defined for the EMMS instruction in addition to inhibiting register file synchronization. More particularly, the tag word register in the floating point unit 36E is updated upon execution of the empty state instruction to indicate that each of the floating point registers is not valid. The empty state instruction is encoded differently than the EMMS instruction, and microprocessor 10 is configured to execute the EMMS instruction as well. The EMMS instruction, however, as no effect on whether or not register files 42 and 44 are synchronized. In other words, if the EMMS instruction is executed and the empty state instruction is not executed, register files 42 and 44 are synchronized. In one particular embodiment, an encoding of OF 0E (hexadecimal) is assigned to the empty state instruction (as opposed to the encoding OF 77 for the EMMS instruction) and the instruction mnemonic is FEMMS. It is noted that microprocessor 10 may employ register renaming with respect to register files 42 and 44, such that a particular physical location within register file 42 is not permanently assigned to a given logical floating point register (and similarly a particular physical location within register file 44 is not permanently assigned to a given logical multimedia register). However, prior to the execution of any particular instruction, a set of physical locations within each register file does correspond to the logical registers. Accordingly, register file synchronization is still performed even in the presence of register renaming. It is further noted that, while the above discussion refers to floating point and multimedia instructions as having register source operands and destinations, these instructions are not precluded from having memory operands (i.e. operands read from and stored to memory locations directly as opposed to using registers). Still further, while multimedia and floating point instruction types are described herein as having shared register sets, it is contemplated that other types of instructions may be similarly configured, and that the empty state instruction may be used in such embodiments. In one embodiment, instruction cache 14 is organized as sectors, with each sector including two 32 byte cache lines. The two cache lines of a sector share a common tag and have separate state bits that track the status of the line. Accordingly, two forms of cache misses (and associated cache fills) may take place: sector replacement and cache line replacement. In the case of sector replacement, the miss is due to a tag mismatch in instruction cache 14, with the required cache line being supplied by external memory via bus interface 24. The cache line within the sector that is not needed is then marked invalid. The required cache line is supplied by external memory, but, unlike the sector replacement case, the cache line within the sector that was not requested remains in the same state. In alternate embodiments, other organizations for instruction cache 14 may be utilized, as well as various replacement policies. Microprocessor 10 performs prefetching only in the case of sector replacements, in one embodiment. During sector replacement, the required cache line is filled. If this required cache line is in the first half of the sector, the other cache line in the sector is prefetched. If this required cache line is in the second half of the sector, no prefetching is performed. It is noted that other prefetching methodologies may be employed in different embodiments of microprocessor 10. When cache lines of instruction data are retrieved from external memory by bus interface unit 24, the data is conveyed to predecode logic block 12. In one embodiment, the instructions processed by microprocessor 10 and stored in cache 14 are variable length (e.g. the x86 instruction set). Because decode of variable length instructions is particularly complex, predecode logic block 12 is configured to provide additional information to be stored in predecode cache 15 to aid during decode. In one embodiment, predecode logic block 12 generates predecode bits for each byte stored in instruction cache 14. The predecode bits indicate the number of bytes to the start of the next variable length instruction. These predecode bits are stored in predecode cache 15 are passed to decode unit 20 when instruction bytes are requested from cache 14. Instruction cache 14 may be implemented as a 32 Kbyte, two way set associative cache. The cache line size may be 32 bytes, for example. Cache 14 also includes a TLB 16 used to translate linear addresses to physical addresses. TLB 16 may comprise, for example, 64 entries. Instruction fetch addresses are supplied by cache controller 18 to instruction cache 14. In one embodiment, up to 16 bytes per clock cycle may be fetched from cache 14. The corresponding predecode information is fetched from predecode cache 15 in parallel. The fetched information is placed into an instruction buffer within decode unit 20. In one embodiment of microprocessor 10, fetching may occur long a single execution stream with up to seven outstanding branches taken. Decode unit 20 is configured to decode multiple instructions per processor clock cycle. In one embodiment, decode unit 20 accepts instruction bytes and predecode bits from the instruction buffer (in x86 format), locates instruction boundaries, and generates corresponding "RISC ops". RISC ops are fixed format internal instructions, most of which are executable by microprocessor 10 in a single clock cycle. RISC ops are combined to form every function of the x86 instruction set. Instruction control unit 34 contains the logic necessary to manage out of order execution of instructions stored in scheduler buffer 32. Instruction control unit 34 also manages data forwarding, register renaming, simultaneous issue and retirement of RISC ops, and speculative execution. In one embodiment, scheduler buffer 32 holds up to 24 RISC ops at one time, equating to a maximum of 12 x86 instructions. When possible, instruction control unit 34 may simultaneously issue (from buffer 32) a RISC op to any available one of execution units 36. In one embodiment, instruction control unit 34 may issue up to 6, and retire up to four, RISC ops per clock cycle. As shown in Fig. 1, microprocessor 10 includes five execution units 36. Store unit 36B and load unit 36A are two staged pipeline designs. Store unit 36A performs data memory writes which are available for loading after one clock cycle. Load unit 36A performs memory reads. The data from these reads is available after two clock cycles. Load and store units are possible in other embodiments with varying latencies. Execution unit 36C is a fixed point (or integer) execution unit which is configured to operate on ALU operations, multiplication, division (both signed and unsigned), shifts, and rotates. In contrast, execution unit 36D is a fixed point execution unit which is configured to operate on basic word and double word ALU operations (e.g. add, and, compare, etc.). Execution units 36C-36D are also configured to accelerate performance of software written using multimedia instructions. Applications that can take advantage of multimedia instructions include graphics, video and audio compression and decompression, speech recognition, and telephony. Execution unit 36E contains an IEEE 754 compliant floating point unit designed to accelerate the performance of software which utilizes the x86 floating point instructions. Execution unit 36E may include an adder unit, a multiplier unit, and a divide/square root unit. Execution unit 36E may operate in a coprocessor style fashion, in which decode unit 20 directly dispatches the floating point instructions to execute unit 36E. The floating point instructions are still allocated in scheduler buffer 32 to allow for in order retirement of instructions. Execution unit 36E and scheduler buffer 32 communicate to determine when a floating point instruction is ready for retirement. Branch resolution unit 35 is separate from the branch prediction logic 22 in that it resolves conditional branches after the branch conditions been evaluated. Branch resolution unit 35 allows efficient speculative execution, enabling microprocessor 10 to execute instructions beyond conditional branches before knowing whether the branch prediction was correct. As described above, microprocessor 10 is configured to handle up to seven outstanding branches in one embodiment. Branch prediction logic 22, coupled to decode unit 20, is configured to increase the accuracy with which conditional branches are predicted in microprocessor 10. Branch prediction logic 22 is configured to handle branch behavior and its negative effects on instruction execution, such as stalls due to delayed instruction fetching. In one embodiment, branch prediction logic 22 includes an 8192 entry branch history table, a 16 entry by 16 byte branch target cache, and a 16 entry return address stack. Branch prediction logic 22 implements a two level adaptive history algorithm using the branch history table. This table stores executed branch information, predicts individual branches, and predicts behavior of groups of branches. In one embodiment, the branch history table does not store predicted target addresses in order to save space. These addresses are instead calculated on the fly during the decode stage. To avoid a clock cycle penalty for a cache fetch when a branch is predicted taken, a branch target cache within branch logic 22 supplies the first 16 bytes at the target address directly to the instruction buffer (if a hit occurs in the branch target cache). Branch logic 22 also includes circuitry designed to optimize the call and return instructions. This circuitry allows the address of the next instruction following the call instruction in memory to be pushed onto a return address stack. When microprocessor 10 encounters a return instruction, branch logic 22 pops the address from the return stack and begins fetching at that address. Like instruction cache 14, data cache 26 is also organized as a two way set associative, 32 Kbyte cache according to the present embodiment. Data TLB 28 is used to translate linear to physical addresses, and may include, for example, 128 entries. Data cache 26 may be sectored similar to instruction cache 14. Turning next to Fig. 2, a block diagram of one embodiment of decode unit 20 is shown. Other embodiments are possible and contemplated. In the embodiment shown in Fig. 2, decode unit 20 includes an instruction buffer 50, a set of short decoders 52, a long decoder 54, a vector decoder 56, a sequencer 58, a microcode ROM 60, and an output select multiplexor (mux) 62. Instruction buffer 50 is coupled to receive instruction bytes and corresponding predecode data from instruction cache 14 and predecode cache 15 or from branch logic unit 22 in the event that a branch is predicted taken. Instruction buffer 50 is also coupled to short decoders 52, long decoder 54, and vector decoder 56. Each of short decoders 52, long decoder 54, vector decoder 56, and sequencer 58 are coupled to provide inputs to output select mux 62. Vector decoder 56 is also coupled to sequencer 58 which is further coupled to microcode ROM 60. Output select mux 62 is coupled scheduler buffer 32. Vector decoder 56 includes a pair storage locations 64 and 66. Storage location 64 stores a multimedia enable indication, while storage location 66 stores a floating point enable indication. Sequencer 58 includes a scratch RAM 68 for use by microcode routines stored in microcode ROM 60. Scratch RAM 68 includes storage for a floating point/multimedia state. Instruction buffer 50 is configured to store the instruction bytes and corresponding predecode data until the bytes are decoded and dispatched by one of decoders 52, 54 and 56. Each clock cycle, instruction buffer 50 discards the instruction bytes which have been decoded and merges the remaining instruction bytes with instruction bytes received from instruction cache 14/predecode cache 15 or branch logic unit 22. In one embodiment, instruction buffer 50 stores up to 16 instruction bytes and corresponding predecode data. Short decoders 52 translate the most commonly used x86 instructions (e.g. moves, shifts, branches, etc.) into zero, one or two RISC ops each. Short decoders 52 are configured to operate upon "short" x86 instructions. In other words, short decoders 52 are configured to decode instructions having a number of bytes up to a predefined maximum length. In one embodiment, the predefined maximum length is seven bytes. In one embodiment, short decoders 52 comprises two parallel decoders. Long decoder 54 decodes one instruction per clock cycle and generates up to four RISC ops in response to the instruction. The decoder 54 is configured to decode an instruction which is longer than the predefined maximum length supported by short decoders 52, but can still be decomposed into no more than four RISC ops. In one embodiment, long decoder 54 is configured to decode instructions up to 11 bytes in length. Vector decoder 56 decodes the remaining instructions not handled by short decoders 52 or long decoder 54. Vector decoder 56 is configured to generate the first four RISC ops of a microcode routine corresponding to the instruction being decoded. In parallel, vector decoder 56 is configured generate an entry point (i.e. an address within microcode ROM 60) at which the remainder of the routine is stored. Sequencer 58 fetches the remainder of the routine from microcode ROM 60 during subsequent clock cycles, and transmits the routine, up to four RISC ops at a time, to output select mux 62. In addition to handling those instructions for which short decoders 52 and long decoder 54 are not designed, vector decoder 56 detects certain exception conditions and generates the initial RISC ops of the corresponding to microcode routine and entry point in response to the exception condition. One of these exception conditions is the detection of either: (i) a multimedia instruction subsequent to decoding floating point instructions but prior to decoding any other multimedia instructions; and (ii) a floating point instruction subsequent to decoding multimedia instructions but prior to decoding any other floating point instructions. In each these cases, a synchronization of register files 42 and 44 may be needed. Vector decoder 56 detects the above mentioned cases using the multimedia enable and floating point enable indications stored in storage locations 64 and 66. Each indication may comprise a bit indicative, when set, 10 that decode of the corresponding instruction type is enabled and indicative, when clear, that decode of the corresponding instruction type is disabled. Alternatively, each indication may comprise a bit indicative when set, that decode of the corresponding instruction type is disabled and indicative, when clear, that decode of the corresponding instruction type is enabled. Only one of the instruction types represented by the multimedia enable and the fioatmg point enable indications may be enabled at any given time. Upon decode of an instruction type which is disabled, vector decoder 56 generates the exception condition. Sequencer 58 fetches the microcode routine which determines if a register file synchronization between register files 42 and 44 is to be performed and which selectively performs that synchronization. The microcode routine also performs certain other synchronizations between execution units 36C-36D and execution unit 36E. For example, in embodiments of microprocessor 10 which employ x86 architecture including the multimedia instructions described above, the tag word used by floating point execution unit 36E to indicate the validity of the floating point registers and the top of stack portion of the status word are modified in response to execution of mukimedia instructions. Accordingly, if a floating point instruction is being decoded upon generation of the exception, the top of stack and tag word within floating point execution in a 36E are modified accordingly. Sequencer 58 stores a floating point/multimedia state within scratch RAM 68. The floating point/multimedia state indicates whether or not floating point instruction decode or multimedia instruction decode are enabled, similar to the multimedia enable and floating point enable indications maintained by vector decoder 56. Additionally, however, the floating point/multimedia state also indicates if the most recently decoded multimedia instruction was an empty state instruction. The floating point/multimedia state is set to indicate that the most recently decoded multimedia instruction was an empty state instruction upon decode of the empty state instruction by vector decoder 56. The floating point/multimedia state indicates that the most recently decoded mukimedia instruction was an empty state instruction until either a floating point or a multimedia instruction is subsequently decoded. If a subsequently decoded multimedia or floating point instruction is enabled (as indicated by the multimedia enable and floating point enable indications), the floating point/multimedia state is updated to indicate that instruction type and that the last instruction decoded was not the empty state instruction. In one embodiment, the empty state instruction is considered to be a multimedia instruction by vector decoder 56. Accordingly, subsequent to decoding an empty state instruction, a floating point instruction causes an exception and the multimedia instruction does not cause an exception but does cause the floating point/multimedia state to be set not to indicate that the most recently decoded instruction was an empty state instruction. In this manner, the microcode routine fetched from microcode ROM 60 can determine whether or not a synchronization of register files 42 and 44 is desired. Alternatively, sequencer 58 may fetch different microcode routines depending on the state of the floating point/multimedia state and whether or not, in the case of decode of a multimedia instruction by vector decoder 56, the multimedia instruction is the empty state instruction. The microcode routine also disables the instruction type that was previously enabled and enables the instruction type was previously disabled in storage locations 64 and 66. Subsequently, the instruction for which vector decoder 56 generated the exception is fetched again. Since the corresponding instruction type has now been enabled, an exception should not be generated. Additionally, if instruction of the opposite instruction type is subsequently decoded, another exception is generated (and an opportunity to synchronize or not synchronize register files 42 and 44 occurs). 11 In the above described fashion, decode unit 20 is configured to either inhibit synchronization of register files 42 and 44 or perform the synchronization upon decoding an instruction type which is not currently enabled. The enable indications allow decode unit 20 to detect boundaries between a set of one or more floating point instructions and a set of one or more multimedia instructions, even if a variety of the other instruction types are decoded therebetween (e.g. integer instructions). It is noted that, in some cases, decode of neither instruction type may be enabled. For example, floating point instruction execution may be disabled via various control bits in control registers defined by the architecture employed by microprocessor 10. In such a case, floating point instruction decode is disabled even if multimedia instruction decode is disabled. Output select mux 62 is configured to select instructions from one of the sources providing instructions thereto and to transmit those instructions to scheduler buffer 32. Each of the sources of instructions provides RISC ops to output select mux 62, and hence scheduler buffer 32 only receives RISC ops. Output select mux 62 is controlled by control signals (not shown in the drawing for clarity) from each of the decoders and sequencer 58. It is noted that instructions from instruction buffer 50 are provided to each of decoders 52, 54, and 56 in parallel. Each of the decoders attempts to decode the instruction bytes provided, and a decoder which is actually able to decode the instruction(s) causes output select mux 62 to select its output. It is further noted that microcode ROM 60, in addition to storing the routines described above for register file synchronization (or the lack thereof), stores routines for various other purposes, as desired. A microcode routine comprises a sequence of instructions (e.g. RISC ops) which are arranged to accomplish a particular objective. Turning next to Fig. 3, an exemplary state machine 70 illustrating the states of one embodiment of the floating point/multimedia state maintained by sequencer 58 is shown. Other embodiments are possible in contemplated. In the embodiment of Fig. 3, state machine 70 includes an FP active state 72, a multimedia active state 74, and an FEMMS state 76. FP active state 72 is the state in which floating point instructions may be decoded and dispatched without causing an exception to determine if a register file synchronization is to be performed. In either of mukimedia active state 74 or FEMMS state 76, multimedia instructions may be decoded and dispatched without causing an exception to determine if a register file synchronization is to be performed. The various arcs illustrated upon state machine 70 indicate the events which cause state changes to occur. A dashed arc indicates an exception signalled by vector decoder 56 in order determine if a register file synchronization is to be performed. A solid arc indications a state change (or lack thereof) performed without an exception. When state machine 70 is in FP active state 72, a decode of either floating point or "regular" instructions cause state machine 70 to remain in FP active state 72. For purposes of this discussion, "regular" instructions refer to instructions which are not floating point, multimedia, or empty state instructions. For example, integer instructions are regular instructions in this discussion. On the other hand, the decode of a multimedia instruction or an empty state instruction (an "FEMMS instruction" as shown in Fig. 3) causes a state transition from FP active state 72 to one of multimedia active state 74 or FEMMS state 76, respectively. Each of these transitions occurs via an exception signalled by vector decoder 56 to sequencer 58. A transition from FP active state 72 to multimedia active state 74 incurs a register file synchronization, while a transition from FP active state 72 to 12 FEMMS state 76 does not incur a register file synchronization. In this manner, a transition from executing floating point instructions to executing multimedia instructions can be initiated with an empty state instruction, and the register file synchronization may be inhibited. Upon completion of the microcode routine, state machine 70 is in the destination state. When state machine 70 is in multimedia active state 74, a decode of either multimedia or regular instructions causes state machine 70 to remain in multimedia state 74. On the other hand, a decode of an empty state instruction causes state machine 72 transition to FEMMS state 76 and a decode of the floating point instruction causes a transition to FP active state 72. The transition to FEMMS state 76 occurs without causing an exception (because the empty state instruction is considered to be a multimedia instruction with respect to state machine 70 and with respect to synchronization of register files 42 and 44). Conversely, the transition to FP active state 72 occurs via an exception. When state machine 70 is in FEMMS state 76, a decode of regular instructions causes state machine 70 to remain in FEMMS state 76. In this manner, one or more regular instructions can be inserted in a code sequence between the empty state instruction and a subsequent multimedia instruction or floating point instruction and the effects upon register file synchronization due to the existence of the empty state instruction within the code sequence are the same as if the regular instructions were not in the code sequence. Accordingly, the programming model for use of the empty state instruction may be more flexible. On the other hand, a decode of a mukimedia instruction causes state machine 70 transition to multimedia active state 74 (again without a register file synchronization since the empty state instruction is considered to be a multimedia instruction). A decode of a floating point instruction causes a transition to FP active state 72 and an exception to determine if register file synchronization is desired. The transition from FEMMS state 76 to FP active state 72 is accomplished without a register file synchronization, because state machine 70 being in FEMMS state 76 indicates that the most recently executed multimedia or floating point instruction was the empty state instruction, and hence register file synchronization is not desired. It is noted that, while the above description indicates which of the exception-causing transitions incur a register file synchronization and which do not, those state machine transitions are managed via microcode routines. Accordingly, it is the microcode routines that determine, during execution of a state transition, whether or not a register file synchronization is performed. It is further noted that the transitions between multimedia active state 74 and FEMMS state 76 may be performed without causing an exception because the empty state instruction is considered to be a multimedia instruction. Accordingly, register file synchronization is not needed. The floating point/multimedia state maintained by sequencer 58 is simply updated to the new state. Furthermore, the state machine described above is implemented partially in microcode routines and partially in hardware. However it is contemplated that the state machine could be implemented completely in hardware, including the appropriate register file synchronizations. Still further, other embodiments are contemplated in which the functionality represented by state machine 70 and decode unit 20 may be employed a different stages in the pipeline than the decode stage. Any suitable configuration may be used. It is noted that, according to one embodiment, the state of state machine 70 may be dispatched along with each branch instruction predicted by microprocessor 10. If a branch misprediction occurs, the state 13 dispatched with that branch instruction may be restored to state machine 70. Alternatively, a combination of dispatching the state with branch instructions and stalling instruction execution prior to executing certain instructions may be employed as desired. Any suitable method for restoring the state of state machine 70 when speculative instruction execution is redirected (e.g. branch misprediction and exception) may be used. Turning next to Fig. 4, a flowchart shown illustrating an exemplary set of actions performed by one or more microcode routines used to selectively perform a register file synchronization in accordance with the above description. Other embodiments are possible and contemplated. While the steps shown in Fig. 4 are in some cases illustrated in serial order, any suitable order may be used. For the remainder of this discussion, the term microcode routine will be used. It is understood, however, that one or more microcode routines may be used to perform the steps shown in Fig. 4. The microcode routine examines the state of the floating point enable and multimedia enable indications stored in storage locations 64 and 66 to determine the appropriate actions to perform (decision blocks 80 and 82). If neither floating point instructions nor multimedia instructions are enabled, the microcode routine transfers control to a software interrupt handler (step 84). The software interrupt handler may determine whether or not floating point and/or mukimedia execution should be enabled. If the floating point enable indication is enabled (i.e. state machine 70 is in FP active state 72), the microcode routine determines if the multimedia instruction to be decoded is the empty state instruction (decision block 86). If the multimedia instruction is the empty state instruction, then a transition between floating point instructions and multimedia instructions has been detected, and the multimedia instructions are initiated with the empty state instruction. Accordingly, a register file synchronization is not desired. The microcode routine sets the floating point/multimedia state to FEMMS state 76 (step 88) and further sets storage locations 64 and 66 to indicate multimedia enabled and floating point disabled. On the other hand, if the multimedia instruction to be decoded is not the empty state instruction, then a transition between floating point instructions and multimedia instructions has been detected and a register file synchronization is desired. Accordingly, each of the registers within register file 42 is copied to a corresponding register within register file 44 (step 90). Additionally, the microcode routine sets the floating point/multimedia state to mukimedia active state 74 and sets storage locations 64 and 66 to indicate multimedia enabled and floating point disabled. If, conversely, floating point is disabled and multimedia is enabled, the microcode routine determines if state machine 70 is in FEMMS state 76 (decision block 92). If state machine 70 is in FEMMS state 76, then a transition between multimedia instructions and floating point instructions has been detected and a register file synchronization is not desired. Accordingly, the microcode routine sets the tag word within floating point execution unit 36E to indicate that each register within register file 42 is invalid (because the most recently executed multimedia instruction was the empty state instruction). Additionally, the microcode routine sets the top of stack portion of the status word to zero (in accordance with multimedia instruction definitions). Still further, the microcode routine sets the floating point/multimedia state to FP active state 72, and sets storage locations 64 and 66 to indicate multimedia disabled and floating pomt enabled (step 94). If floating point is disabled, multimedia is enabled, and state machine 70 is in multimedia active state 74, a transition between multimedia instructions and floating point instructions has been detected and a register file 14 synchronization is desired. Therefore, the microcode routine sets the stack portion of the status word to zero (step 96). Additionally, the tag word is set for each register to either valid or invalid depending upon whether not the most recently executed multimedia instruction was the EMMS instruction or another multimedia instruction. Additionally, the microcode routine copies the registers within register file 44 to the corresponding registers within register file 42. Finally, the microcode routine sets the floating point/multimedia state to FP active state 72, and sets storage locations 64 and 66 to indicate multimedia disabled and floating point enabled. Turning now to Fig. 5, an exemplary software hierarchy is shown to indicate exemplary uses for the empty state instruction. A variety of routines are illustrated via boxes 100-108. Each box is divided into an upper portion and a lower portion. The upper portion identifies the type of routine, and the lower portion illustrates the set of instructions included in that type of routine. Arrows between the boxes illustrate which routines may communicate with each other (i.e. call or be called). Box 100 illustrates a regular routine (i.e. a routine which does not include floating point or multimedia instructions) which does not get called by a floating point routine and does not call a floating point routine. Accordingly, the regular routine includes one or more regular instructions. Optionally following the one or more regular instructions is the empty state instruction if a multimedia routine is called by the regular routine. A return instruction concludes the regular routine. Accordingly, a routine such as the routine represented by box 108 may omit the empty state instruction at the conclusion of the routine. Furthermore, the routine represented by box 108 may omit the empty state instruction at the beginning of the routine if the regular routine and any multimedia routines which call the routine represented by box 108 includes the empty state instruction prior to calling the routine represented by box 108. The routine illustrated by box 108 is a multimedia routine (i.e. a routine including one or more multimedia instructions and optionally one or more regular instructions) which is called only by multimedia routines or regular routines. Since the routine illustrated by box 108 is only called by multimedia routines or regular routines, the routine illustrated by box 108 may omit the empty state instruction and rely on the called routines to insert the empty state instruction prior to execution of any floating point instructions. The routine illustrated by box 108 concludes with a return instruction. The routine illustrated by box 102 is a regular routine which may be called by any routine, including floating point routines. Accordingly, the routine includes one or more regular instructions concluded with a return instruction. Box 104 illustrates a multimedia routine which is callable by non multimedia routines including, for example, floating point routines. Accordingly, the routine is initiated by an empty state instruction to inhibit a register file synchronization if the routine is called by a floating routine or is called subsequent to the execution of a floating point routine but prior to the execution of a different multimedia routine. The empty state instruction is followed by one or more mukimedia and/or regular instructions. The routine concludes with another empty state instruction and a return instruction. The concluding empty state instruction inhibits a register file synchronization if a subsequent routine executes floating point instructions. A floating point routine is illustrated by box 106. Floating point routines may be called by any other routines, and include one or more floating point and/or regular instructions and conclude with a return instruction. 15 The routines illustrated in Fig. 5 are an exemplary attempt to minimize the number of empty state instructions which are included in the variety of routines which may be employed by a program. Additionally, it is noted that if register file synchronizations are desired, then the empty state instruction should not be used for those routines. Turning now to Fig. 6, a block diagram of one embodiment of a computer system 200 including microprocessor 10 coupled to a variety of system components through a bus bridge 202 is shown. Other embodiments are possible and contemplated. In the depicted system, a main memory 204 is coupled to bus bridge 202 through a memory bus 206, and a graphics controller 208 is coupled to bus bridge 202 through an AGP bus 210. Finally, a plurality of PCI devices 212A-212B are coupled to bus bridge 202 through a PCI bus 214. A secondary bus bridge 216 may further be provided to accommodate an electrical interface to one or more EISA or ISA devices 218 through an EISA/ISA bus 220. Microprocessor 10 is coupled to bus bridge 202 through a CPU bus 224. Bus bridge 202 provides an interface between microprocessor 10, main memory 204, graphics controller 208, and devices attached to PCI bus 214. When an operation is received from one of the devices connected to bus bridge 202, bus bridge 202 identifies the target of the operation (e.g. a particular device or, in the case of PCI bus 214, that the target is on PCI bus 214). Bus bridge 202 routes the operation to the targeted device. Bus bridge 202 generally translates an operation from the protocol used by the source device or bus to the protocol used by the target device or bus. In addition to providing an interface to an ISA/EISA bus for PCI bus 214, secondary bus bridge 216 may further incorporate additional functionality, as desired. For example, in one embodiment, secondary bus bridge 216 includes a master PCI arbiter (not shown) for arbitrating ownership of PCI bus 214. An input/output controller (not shown), either external from or integrated with secondary bus bridge 216, may also be included within computer system 200 to provide operational support for a keyboard and mouse 222 and for various serial and parallel ports, as desired. An external cache unit (not shown) may further be coupled to CPU bus 224 between microprocessor 10 and bus bridge 202 in other embodiments. Alternatively, the external cache may be coupled to bus bridge 202 and cache control logic for the external cache may be integrated into bus bridge 202. Main memory 204 is a memory in which application programs are stored and from which microprocessor 10 primarily executes. A suitable main memory 204 comprises DRAM (Dynamic Random Access Memory), and preferably a plurality of banks of SDRAM (Synchronous DRAM). PCI devices 212A-212B are illustrative of a variety of peripheral devices such as, for example, network interface cards, video accelerators, audio cards, hard or floppy disk drives or drive controllers, SCSI (Small Computer Systems Interface) adapters and telephony cards. Similarly, ISA device 218 is illustrative of various types of peripheral devices, such as a modem, a sound card, and a variety of data acquisition cards such as GPIB or field bus interface cards. Graphics controller 208 is provided to control the rendering of text and images on a display 226. Graphics controller 208 may embody a typical graphics accelerator generally known in the art to render three- dimensional data structures which can be effectively shifted into and from main memory 204. Graphics controller 208 may therefore be a master of AGP bus 210 in that it can request and receive access to a target 16 interface within bus bridge 202 to thereby obtain access to main memory 204. A dedicated graphics bus accommodates rapid retrieval of data from main memory 204. For certain operations, graphics controller 208 may further be configured to generate PCI protocol transactions on AGP bus 210. The AGP interface of bus bridge 202 may thus include functionality to support both AGP protocol transactions as well as PCI protocol target and initiator transactions. Display 226 is any electronic display upon which an image or text can be presented. A suitable display 226 includes a cathode ray tube ("CRT"), a liquid crystal display ("LCD"), etc. It is noted that, while the AGP, PCI, and ISA or EISA buses have been used as examples in the above description, any bus architectures may be substituted as desired. It is further noted that computer system 200 may be a multiprocessing computer system including additional microprocessors (e.g. microprocessor 10a shown as an optional component of computer system 200). Microprocessor 10a may be similar to microprocessor 10. More particularly, microprocessor 10a may be an identical copy of microprocessor 10. Microprocessor 10a may share CPU bus 224 with microprocessor 10 (as shown in Fig. 6) or may be connected to bus bridge 202 via an independent bus. In accordance with the above disclosure, a microprocessor has been shown which supports selective register file synchronization between two register files which are defined to map to the same logical storage. Advantageously, if synchronization between the register files is not desired, the microprocessor may inhibit the synchronization. Instruction sequences employing both types of instructions which access the same logical register file and which do not require register file synchronization may achieve higher performance due to the non-synchronization of the register files. On the other hand, code sequences which do require register file synchronization still receive the benefits of the synchronization (with possibly lower performance achieved). Industrial Applicability The present invention may be applicable to microprocessors and computer systems. Numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications. 17

Claims: WHAT IS CLAIMED: 1. A microprocessor (10) comprising: a first register file (42, 44) including physical storage locations corresponding to a first plurality of registers; and a second register file (42, 44) including physical storage locations correspondmg to a second plurality of registers; wherein said first plurality of registers and said second plurality of registers are mapped onto a logical storage in which each of said first plurality of registers is assigned to a logical storage location to which a corresponding one of said second plurality of registers is assigned, and wherein said microprocessor (10) is configured to inhibit a synchronization of said first register file and said second register file responsive to an empty state instruction. 2. The microprocessor as recited in claim 1 further configured to execute instructions defined within an instruction set including a first type of instructions, a second type of instructions, and said empty state instruction, and wherein said instruction set further defines that said first plurality of registers is accessible via said first type of instructions and said second plurality of registers is accessible via said second type of instructions 3. The microprocessor as recited in claim 2 further configured to inhibit said synchronization subsequent to executing a first instruction of said first type and prior to executing a second instruction of said second type responsive to a first instruction sequence including said first instruction and said second instruction also including said empty state instruction 4. The microprocessor as recited in claim 3 further comprising a decode unit (20) configured to decode instructions within said instruction set, wherein said decode unit is configured to inhibit said synchronization only responsive to a program order of said first instruction sequence being said first instruction, subsequently said empty state instruction, and further subsequently said second instruction. 5. The microprocessor as recited in claim 4 wherein said first instruction sequence further includes one or more instructions of a third type of instructions defined by said instruction set. 6. The microprocessor as recited in claim 5 wherein said decode unit (20) is configured to inhibit said synchronization even if some of said one or more instructions are between said first instruction and said empty state instruction in program order. 18 7. The microprocessor as recited in claim 5 wherein said decode unit (20) is configured to inhibit said synchronization even if some of said one or more instructions are between said second instruction and said empty state instruction in program order. 8. The microprocessor as recited in claim 5 wherein said third type of instructions comprises integer instructions. 9. The microprocessor as recited in claim 4 wherein said decode unit (20) is configured to initiate said synchronization of said first register file (42 ,44) and second register file (42, 44) upon decode of a second instruction sequence including said first and second instructions but excluding said empty state instruction. 10. The microprocessor as recited in claim 9 wherein said decode unit (20) comprises: one or more decoders (52, 54, 56) configured to decode instructions; and a microcode ROM (60) coupled to provide instructions upon decode of a microcoded instruction by one of said one or more decoders, said microcode ROM further storing a routine including instructions to inhibit said synchronization and instructions to perform said synchronization. 11. The microprocessor as recited in claim 2 wherein said first type of instructions comprises one of a group including multimedia instructions and floating point instructions. 12. The microprocessor as recited in claim 9 wherein said second type of instructions comprises another one of said group. 13. The microprocessor as recited in claim 2 further comprising: a first execution unit (36C, 36D, 36E) coupled to said first register file (42, 44), wherein said first execution unit (36C, 36D, 36E) is configured to execute instructions of said first type, and wherein said first execution unit (36C, 36D, 36E) is configured to read operands for said instructions of said first type from said first register file (42,44); and a second execution unit (36C, 36D, 36E) coupled to said second register file (42, 44), wherein said second execution unit (36C, 36D, 36E) is configured to execute instructions of said second type, and wherein said second execution unit (36C, 36D, 36E) is configured to read operands for said instructions of said second type from said second register file (42, 44). 14. A computer system (200), comprising: 19 a microprocessor (10) as recited in claim 1; a main memory (204) coupled to said microprocessor (10), wherein said main memory (204) is configured to store an instruction sequence and to provide said instruction sequence to said microprocessor (10) upon request therefrom for said instruction sequence; and an input/output (I/O) device (212, 218) coupled to said main memory (204), said I/O device (212, 218) configured to transfer data between said main memory (204) and a second computer system coupled to said I/O device. 15. The computer system (200) as recited in claim 14 further comprising a second microprocessor (10a) identical to said microprocessor (10). 16. A method for executing instructions defined within an instruction set including a first type of instructions, a second type of instructions, and an empty state instruction, wherein said instruction set further defines that a first plurality of registers accessible via said first type of instructions and a second plurality of registers accessible via said second type of instructions are mapped onto a logical storage in which each of said first plurality of registers is assigned to a logical storage location to which a corresponding one of said second plurality of registers is assigned, the method comprising: reading a first operand for a first instruction of said first type from a first register file (42,44) including physical storage locations for each of said first plurality of registers; reading a second operand for a second instruction of said second type from a second register file (42, 44) including physical storage locations for each of said second plurality of registers; and inhibiting a synchronization of said first register file (42, 44) and said second register file (42, 44) if said empty state instruction is included between said first instruction and said second instruction in said instruction sequence. 17. The method as recited in claim 16 further comprising: synchronizing said first register file (42, 44) and said second register file (42, 44) between said reading said first operand and said reading said second operand if said empty state instruction is not included between said first instruction and said second instruction in an instruction sequence. 18. The method as recited in claim 16 further comprising synchronizing said first register file (42, 44) and said second register file (42, 44) responsive to said instruction sequence including a third instruction of said first type 20 between said empty state instruction and said second instruction. 19. The method as recited in claim 16 wherein said inhibiting is performed even if one or more instructions of a third type of instructions defined within said instruction set are included within said instruction sequence between said first instruction and said empty state instruction or between said second instruction and said empty state instruction. 21

Inventors: FAVOR JOHN G, FAVOR, JOHN, G.
Applicants: ADVANCED MICRO DEVICES INC, ADVANCED MICRO DEVICES, INC.
Application year: 1999
Main classification: G06F9
IPC codes: G06F7, G06F9