INTERRUPT PROCESSING SYSTEM

Abstract: An interrupt processing system capable of asynchronous operation of basic CPU resources to be used with an interrupt handler. Interrupt handlers for use in the processing system are easy to prepare. In this system, a program, suspended by a resource-dependent interrupt, is resumed after the interrupt is completed. The system comprises queuing means for judging whether the instruction stored in an instruction buffer requires synchronous processing or asynchronous processing and queuing the instruction if it requires the asynchronous processing. When an interrupt occurs in a synchronous or asynchronous processing section or outside the CPU, queued asynchronous processes may end in incompletion or may cause exceptions. Therefore, the system further includes means for informing the program, at the occurrence of an interrupt, about the contents (unprocessed jobs, or types of exceptions) and method of termination of all the processing that has not been completed or caused exceptions. Thus, the interrupt program is resumed.

Description: The present invention relates to a method of terminating asynchronous CPU processes at the time of occurrence of an interruption and to a method of reporting CPU-resource-using process-dependent factors generated in the asynchronous CPU processes for use in a CPU which executes some CPU resource using processes with long processing times, asynchronously with instructions while guaranteeing data-dependent relationships of the processes. (Although a process is initiated by an instruction, the process is terminated after the instruction is terminated. After executing the instruction that initiated the process, the CPU initiates execution of a next instruction before termination of the initiated process). The present invention is especially effective in executing basic processes used in an OS interruption handler asynchronously with instruction execution. In a CPU which executes CPU-resource-using processes with a long processing time asynchronously with execution of an initiating instruction, partial prior execution of an instruction succeeding a preceding instruction which is long in processing time can be performed by partial prior execution of the succeeding instruction and canceling the effect of the preceding instruction when a program interruption is generated in the process initiated by the preceding instruction. In this case, however, the instruction pipeline of the CPU becomes complicated and the extent of prior execution of the succeeding instruction is limited. An effective method of improving the CPU's performance without stopping the execution of a simultaneously executable succeeding CPU instruction (bearing no data-dependent relationship with the previous process) when the previous process requires a long processing time in a CPU-resource, is to execute the CPU-resource-using process with a long processing time asynchronously with the execution of the succeeding instruction. Using this method, a plurality of CPU-resource-using processes containing more than one asynchronous CPU-resource-using process will be executed at the same time. In conventional computers, the following methods are used to terminate a CPU-resource-using process when an interruption occurs. There are two types of interruptions: CPU-resource-using process-dependent interruptions; and CPU-resource-using process-independent interruptions. (1) All CPU-resource-using processes are executed synchronously with instructions. When a CPU-resource-using process-dependent interruption factor is detected as a result of an execution of an instruction, a corresponding CPU-resource-using process -dependent interruption is generated prior to the execution of the next instruction after the termination of the execution of the instruction. Only when no CPU-resource-using process-dependent interruption is detected at the execution of the last instruction and a CPU-resource-using process-independent factor is present, a corresponding CPU-resource using-process-independent interruption is generated. In the situation where all the CPU-resource-using processes initiated prior to an interruption have been terminated at the time of the occurrence of the interruption, an interruption handler is easy to construct. In the case of an interruption for a necessary CPU-resource-using process-dependent factor, an original program can be resumed after proper processing by the interruption handler. In the case of the previously-described situation in a process (instruction) executing system, however, the execution of a succeeding CPU-resource-using process cannot be terminated during the execution of a CPU-resource using process with a long execution time, thus degrading the performance of the CPU. (2) A unit (for example, a floating-point arithmetic unit) performs input/output operations on some of the CPU resources and asynchronously executes processes (asynchronous CPU-resource-using processes) which are initiated by instructions and executed asynchronously with the execution of the instructions. Where a CPU-resource-using-process-dependent factor is detected in these asynchronous CPU-resource using processes, when a process using a CPU resource accessed by the unit or an instruction initiating a process that the unit executes is executed, a CPU resource-using process-dependent interruption held by the asynchronous operation unit is generated synchronously with the instruction without executing a process specified by the instruction. When an interruption corresponding to an interruption factor other than a CPU-resource-using-process-dependent interruption factor is detected by the asynchronous operation unit, termination of the operation of the asynchronous operation unit does not wait. The CPU-resource-using-process-dependent interruption factor held by the asynchronous operation unit at this point is not reported simultaneously. When the asynchronous operation unit holds a CPU-resource-using-process-independent interruption factor and a CPU-resource-using-process-dependent interruption factor at the same time, the latter takes no precedence over the former and the CPU-resource-using-process-dependent interruption factor remains held, so that a CPU-resource-using-process-independent interruption is generated. Where an asynchronous CPU-resource using process and its output resource are not used in an environment save area of the interruption handler, the method constitutes an effective interruption system. However, the interruption system will have the following problems in the case of non-synchronization of basic CPU-resource-using-processes used in the interruption handler. After the occurrence of an interruption (first interruption), an interruption (second interruption) for a CPU-resource-using-process-dependent interruption factor is generated which is detected in a process initiated by a program executed prior to the occurrence of the first interruption during the operation of the interruption handler which processes the first interruption. In the process for the second interruption, it becomes difficult or impossible to determine which programs initiated the process that generated the interruption factor. In this case, therefore, the processing of the CPU-resource-using-process-dependent interruption detected by a CPU-resource using process used by the interruption handler becomes impossible or the interruption processing by the interruption handler becomes very complicated. (3) An asynchronously operating unit executes an asynchronous CPU-resource-using process initiated by an instruction and executed asynchronously with the instruction. To use the output of the asynchronous unit in a succeeding process, there are two cases: the case in which a specified procedure is required; and the case in which the initiation of execution of an instruction for initiating the succeeding process is delayed. When some interruption factor is detected, the CPU performs the following interruption operations. 1 ○It does not initiate the execution of a new instruction. 2 ○It waits until all processes (asynchronous CPU-resource using processes) being executed by the asynchronously operating unit are terminated. The asynchronously operating unit executes all the processes whose execution have been initiated regardless of whether or not a CPU-resource-using-process-dependent interruption factor has been detected in a preceding process. A CPU-resource-using-process-dependent interruption factor is detected and an output whose value differs from an expected value is also used as it is in a succeeding process. In this case, the result of execution of the succeeding process will become different from an expected one and a CPU-resource-using-process-dependent interruption factor may be detected even in the succeeding process because an input does not have an expected value. When detecting more than one CPU-resource-using-process-dependent interruption factor as a result of operation 2 ○, the asynchronous operation unit holds the interruption factor detected first or all the interruption factors detected. In the case where all the detected interruption factors are held, when a certain CPU-resource-using-process-dependent interruption factor triggers off the generation of a CPU-resource-using-process-dependent interruption factor in a succeeding process, it becomes difficult to specify the triggering interruption factor. 3 ○ When, in operation 2 ○, none of the CPU-resource-using-process-dependent interruption factors are detected, the CPU-resource-using-process-dependent interruption that initiates the interruption operation is generated. When a CPU-resource-using-process-dependent interruption factor is detected, a CPU-resource-using-process-dependent interruption is generated without depending on the type of the interruption factor that initiated the interruption operation. With this interruption handling system, since a CPU-resource-using-process-dependent interruption factor is detected and the execution of a process using its output which has become an expected value as an input is not stopped, non-synchronization of a process results (for example, for storage into main memory, an unpredictable area is destroyed when an address used as an input is abnormal) that cannot specify a resource which is destroyed when an input is abnormal and makes debugging the program very difficult. In addition, with this interruption system, when a CPU-resource-using-process-dependent interruption factor is detected in the non-synchronised process, the original program cannot be resumed. According to a first aspect of the present invention there is provided an interruption handling system comprising: an instruction buffer to store an instruction; and queuing means for determining for the instruction stored in the instruction buffer which of a synchronous process or an asynchronous process is indicated and queuing the instruction when an asynchronous process is indicated; characterised by further comprising: means for indicating, when more than one queued asynchronous process is terminated under exceptional circumstances, contents and termination methods of all of the queued asynchronous processes terminated under exceptional circumstances, according to a data-dependent relationship and an interruption factor so as to enable resumption of each queued asynchronous process, the said exceptional circumstances including: without beginning processing; with an exception in a case where an interruption is generated as a synchronous process or as an asynchronous process by an external interruption; wherein a data-dependent relationship exists between two processes if the later process uses the result of the prior process or the later process overwrites the result of the prior process; and wherein an interruption factor indicates a satisfied condition causing the interruption. Accordingly, an interruption handling system embodying the present invention can permit such basic CPU-resource using processes as are used by an interruption handler to be executed asynchronously and the interruption handler to be executed asynchronously and the interruption handler to be constructed easily. An interruption handling system embodying the present can also permit an original program to be resumed after termination of an interruption handler process corresponding to a necessary CPU-resource-using-process-dependent interruption factor. According to a second aspect of the present invention there is provided a method of operating a command processor comprising the steps of: storing an instruction; determining for the stored instruction which of a synchronous process and an asynchronous process is indicated; and queuing the instruction when an asynchronous process is indicated in the determining step; characterised by further comprising the step of: indicating, when more than one queued asynchronous process is terminated under exceptional circumstances, contents and termination methods of all the queued asynchronous processes terminated under the exceptional circumstances, in accordance with a data-dependent relationship and an interruption factor so as to enable resumption of each queued asynchronous process, the said exceptional circumstances including: without beginning processing; with an exception in a case where an interruption is generated as a synchronous process or as an asynchronous process; by an external interruption; wherein a data-dependent relationship exists between two processes if the later process uses the result of the prior process or the later process overwrites the result of the prior process; and wherein an interruption factor indicates a satisfied condition causing the interruption. An embodiment of the present invention has the following features: (1) When a CPU-resource-using-process-dependent interruption factor or a CPU-resource-using-process-independent interruption factor is detected, an interruption operation is initiated. (2) During the interruption operation, all or part of asynchronous CPU resource using processes are terminated while their data-dependent relationship is guaranteed. A process using the output of a process in which a CPU-resource-using-process-dependent interruption factor has been detected as its input is terminated unexecuted. At the termination of the operation, the data-dependent relationship is erased. 3 ○ When a CPU-resource-using-process-dependent interruption factor is detected at the termination of process which included the interruption factor, a CPU-resource-using-process-dependent interruption is generated without depending on the type of the interruption factor which has initiated the interruption operation. Otherwise, a CPU-resource-using-process-independent interruption is generated. At the time of generation of a CPU-resource-using-process-dependent interruption, all the CPU-resource-using-process-dependent interruption factors and information about processes unexecuted are displayed. 4 ○ After proper processing of a CPU-resource-using-process-dependent interruption factor whose rerun is expected and a process terminated unexecuted by an interruption handler, hardware can rerun the process when return is made to the original program or the interruption handler displays information sufficient to simulate processing. According to the present invention, (1) processes for performing inputting from CPU resources such as registers, outputting from CPU resources or both inputting and outputting are classified into two types of synchronous CPU resource using processes and asynchronous CPU resource using processes and are executed as follows. 1 ○ a synchronous CPU-resource-using process is initiated by an instruction instructing the process, and executed synchronously with the execution of the instruction. The synchronous CPU resource using process initiated by the instruction is completed at the termination of the execution of the instruction. 2 ○ an asynchronous CPU-resource-using process is initiated by an instruction instructing the process, and is executed asynchronously with the execution of the instruction. The asynchronous CPU resource using process initiated by the instruction is completed after the termination of the execution of the instruction; (2) When an asynchronous CPU resource using process (preceding process) for performing an outputting operation to a CPU resource is initiated by an instruction and an output to the resource used by the preceding process is used as input in a CPU resource using process (succeeding process) initiated by an instruction issued after the instruction which has initiated the preceding process, the input from the resource in the succeeding process waits until the output to the resource is terminated in the preceding process. When the CPU resource using process (succeeding process) performs an output operation to a resource, the succeeding process performs an output operation to the resource after access to the resource by all of CPU resource using processes (preceding processes) initiated prior to the succeeding process. When the succeeding process is a synchronous CPU resource using process, the termination of an instruction designating the succeeding process is delayed until access to a related resource in the prior process, that is, a program counter remains pointing to the instruction initiating the succeeding instruction. When the succeeding instruction is an asynchronous CPU resource using process, the termination of the execution of the instruction initiating the succeeding instruction may be delayed until access to the resource by the preceding process is terminated and access to the resource by the succeeding process may be delayed though the execution of the instruction initiating the succeeding instruction is completed and the succeeding process is initiated. When the execution of the asynchronous CPU resource using process is initiated, the output to the resource used in the succeeding CPU resource using process waits until its input is completed. (3) Part of synchronous CPU resource using processes and part of asynchronous CPU resource using processes produce the generation of a CPU resource using process dependent interruption factor. The output of the process is an input in the succeeding process, for making the result of the execution of the succeeding process different from an expected execution result. The CPU resource using process dependent interruption factor is detected when a specific event is generated while a CPU resource using process is being executed and shows that the output of the process in which the CPU resource using process interruption factor is detected is not the expected result, and that the interruption factor indicating that the use of the process output as an input in the succeeding process is not the expected result. When the output of the process in which the CPU-resource-using process-dependent-interruption factor is used as an input in the succeeding process, the result of the execution of the succeeding process is also different from the expected execution result. (4) When said CPU resource using process dependent interruption factor is detected in a CPU resource using process being executed or when an interruption factor of an interruption which is generated without directly depending on the result of the CPU resource using process being executed such as external interruption (CPU resource using process independent interruption), hardware performs the following interruption operations: (A) though not initiating the execution of a new instruction, the hardware continues to execute the instruction being executed and the asynchronous CPU resource using process having its execution initiated, and waits for the executable CPU resource using process to terminate and for its state to vary no longer. (B) After the wait for the termination of the CPU resource using process in step (A) is executed, all the asynchronous CPU resource using processes which were being executed at the time of the initiation of the interruption operation are terminated by one of the following methods. Asynchronization1 ○ Asynchronous CPU resource using process terminating means completes without detecting a CPU resource using process dependent interruption factor and the output of the process is the expected output. Asynchronization2 ○ Asynchronous CPU resource using process terminating means detects the CPU resource using process dependent interruption factor and terminates the execution. Asynchronization3 ○ The asynchronous CPU resource using process terminating means is a process in which the asynchronous CPU resource using process uses the output to the resource of the preceding process, and the CPU resource using asynchronous process is terminated unprocessed when the preceding process detects a CPU resource using process dependent interruption factor and does not perform expected outputting, and the data-dependent relationship for the output of the process terminated unprocessed is erased. Asynchronization4 ○ The asynchronous CPU resource using process terminating means terminates an asynchronous CPU resource using process using the output of the process unexecuted in asynchronization 3 ○ or 4 ○ as an input as it is unexecuted and the data-dependent relationship for the output of the process terminated unexecuted is erased. Asynchronization 5 ○ When at least one asynchronous CPU resource using process dependent interruption factor is detected, the asynchronous CPU resource using process terminating process may terminate an asynchronous CPU resource using process which has already been initiated by an instruction and has no data-dependent relationship with the interruption factor as it is unexecuted. The synchronous CPU resources using process is completed at the time of terminating the execution of the instruction for starting the process by using one of the following methods. The synchronization CPU resource using process which is being executed is completed at the time of terminating the operation of (A) by using one of the following methods. Synchronization1 ○ The synchronous CPU terminating means completes without detecting a CPU resource using process dependent interruption factor. Synchronization2 ○ The synchronous CPU terminating means terminates the execution of a process by detecting a CPU resource using process dependent interruption factor. (C) When none of CPU resource using process dependent interruption factors are detected, an interruption factor which has initiated an interruption operation is a CPU resource using process independent interruption factor and interruption generating means which generates an interruption corresponding to an interruption factor has initiated an interruption operation. (D) When at least one CPU resource using process dependent interruption factor is detected, all information on CPU resource using asynchronous processes corresponding to the asynchronization 2 ○ to 4 ○ and (B) and CPU resource 'using synchronous processes corresponding to the synchronization 2 ○ are notified to the programs initiating the processes simultaneously by one CPU resource using process dependent interruption without depending on an interruption factor which has initiated the interruption operation, thereby performing a compound CPU resource using process dependent process, (5) A part of CPU resource using process dependent interruption factors are the kinds of CPU resource using process dependent interruption factors which are generated by programs that are sometimes expected to resume executing after an appropriate process by the corresponding interruption factor processing program, e.g., a factor for a page absence. Such a factor is called a resume-expected CPU resource using process dependent interruption factor. When a CPU resource using process dependent interruption is generated, if only a CPU resource using process dependent interruption factor expected to be resumed is dependent as an interruption factor, there is the possibility that the original program can be resumed after the proper processing of all generated CPU resource using process dependent interruptions which are expected to be resumed. One of the following methods is possible for each of processes which generated resume-expected CPU resource using process dependent interruptions and for CPU resource using processes terminated unexecuted at the time of generation of a CPU resource using process dependent factor. 1 ○ A process detecting a designated resume-expected CPU resource using process dependent interruption factor and a process terminated unexecuted are re-executed when a CPU resource using process returns to the interruption-originating program. 2 ○ An interruption factor processing program displays information enough to simulate a process on a program at the time of an interruption, when a certain kind of CPU resource using process dependent interruption factor in which a program of the factor generating source is expected to resume and it is necessasry to maintain the input data upon interruption, there is provided a resumption-expected CPU resource using process interruption process for terminating all the succeeding processes in which the input resource of the process generating the factor is determined as the output destination, when the interruption factor is generated, thereby enabling a program generating an interruption factor to be resumed when a resume-expected CPU resource using process dependent interruption factor is generated. Brief Description of Drawings Fig. 1 is a timing diagram of a conventional computer pipeline; Fig. 2 is a timing diagram of a pipeline of a computer in which asynchronous CPU-resource processes which are the subject of the present invention are present; Fig. 3 is a timing diagram indicating synchronization of an instruction execution controller and pipeline reading into main storage in Fig. 2; Fig. 4 is a table illustrating an example of a program; Fig. 5 is a timing diagram of the program of Fig. 4 in a conventional computer; Fig. 6 is a timing diagram of the program of Fig. 4 in a computer of the present invention; Fig. 7 is a block diagram illustrating a first embodiment of the present invention; Fig. 8 is a diagram illustrating an instruction format; Fig. 9 is a diagram illustrating a termination code of a synchronous process; Fig. 10 illustrates a form of an asynchronous queue copying register; Figs. 11A and 11B are a flowchart illustrating the operation of the instruction execution controller in the first embodiment; Fig. 12 is a flowchart illustrating the operation of the asynchronous process execution controller in the first embodiment; Fig. 13 is a flowchart of the processing of an RTN instruction in the first embodiment; Fig. 14 is a block diagram illustrating a hardware arrangement for detecting a data-dependent relationship; Fig. 15 is a block diagram illustrating a second embodiment of the present invention; Fig. 16 is a flowchart illustrating a part of an instruction execution controller in the second embodiment; and Fig. 17 is a flowchart illustrating the processing of an RTN instruction in the second embodiment. First, the throwing-away method for asynchronous processing of the present invention will be described in comparison with the case where it is not used. The basic timing in a pipeline system in which the throwing-away method is not used is shown in Fig. 1, while the timing of the case where the throwing-away method is used is shown in Fig. 2. Each time interval has a duration of 1τ and is synchronous timing. Symbols are used to explain operations allotted to the time intervals and the meaning of each symbol is indicated below. D: Decode: Decoding of an instruction and an execute initiation condition (a collision of a data-dependent relationship and a resource) E: Execute: Execution of an arithmetic operation, computation of an execute address in the case of a main storage access instruction W: Write: Writing of the result of execution P1: Priority of load: Enqueuing into asynchronous processing queue and detecting of an execute initiation condition (a collision of a data-dependent relationship and a resource) C: Cache: Address translation and reading of data from a cache W1: Write of load: Writing of data read from the cache (and the main storage) into a register Pf: Priority of floating point operation: Enqueuing into an asynchronous execution queue and detecting of an execute initiation condition (a collision of a data-dependent relationship and a resource) Ef1: Execute of floating point operation 1 Ef2: Execute of floating point operation 2 Ef3: Execute of floating point operation 3 Wf: Write cycle of the results of floating-point addition and floating-point multiplication. In a pipeline using no throwing-away method, pipeline processing is performed in the order of D, E and W in an inter-register arithmetic operation as shown in Fig. 1, row 1 ○. Bypassing is permitted at the end of the E cycle. When there is a need of loading from the cache, a C cycle for address translation and reading of data from the cache is needed. Bypassing is permitted at the end of this cycle. In the case of a floating-point arithmetic operation, the execute cycle is prolonged from 1τ to 3τ, which needs Ef1, Ef2 and Ef3. Bypassing is performed at the end of Ef3. Fig. 2 shows the case where the throwing-away method is used as in the present invention. 1 ○ is the same as the case where the throwing-away method is not used. In the case of loading from the cache, a P1 interval is present at the end of the D cycle as shown in 2 ○. That is, after enqueuing into an asynchronous queue and detecting of an execute initiation condition (a collision of a data-dependent relationship and a resource), the C cycle follows. These operations can be performed by the throwing-away method. In the case of floating point as well, enqueuing into the asynchronous queue and detecting of an execute initiation condition (a collision of a data-dependent relationship and a resource) are performed by the throwing-away method. Subsequently, a floating-point operation cycle follows. In the throwing-away method, parallel operations are performed such that asynchronization operation is thrown away from or independent from the synchronization operation. Detailed timing of synchronization and non-synchronization is indicated in Fig. 3. 1 ○: Pipeline of an instruction execute controller and a synchronous arithmetic operation executor D-Wait, E-wait and W-wait are present. 2 ○: Asynchronous processing: Pipeline of reading (loading) into main storage (at the time of hit of the cache), the presence of P-wait, synchronization with the E cycle of the instruction execute controller until the C cycle is initiated (for the purpose of entering an effective address as the output of the E cycle in the C cycle). A timing diagram for a program for obtaining the sum of arrays using basic timing in the cases where the throwing-away method is used and it is not used will be described using,as an example, the program illustrated in Fig. 4. The program of Fig. 4 is adapted to obtain the sum X of elements of an array A[0: 100] X = A[0] + A[1] + ··· + A[100] It is assumed that the array elements are double-precision floating-point numbers (length of 8 bytes) in the form of IEEEP 754 (Project 754). A description will be made of a timing chart when the program of Fig. 4 is executed in a synchronous computer which makes no use of the throwing-away of Fig. 5. The instruction numbers 1 to 10 of the program correspond to the numbers indicated on the left of the timing chart. Each of the instructions 1 to 4 is made possible by pipelining of synchronous processes D, E, W. At instruction number 5, the program enters looping and the cache is used at the first instruction within the loop, i.e., the fifth instruction. Thus, the basic cycle is formed of D, E, C, W. At the sixth instruction, addition using floating-point arithmetic is performed and its operand is the result of execution of the fourth instruction and the result of execution of the fifth instruction. If there is a data-dependent relationship and data is not gathered, the floating-point addition cannot be performed. Thus, the addition of GR 2 and GR3 is performed in the instruction 7, which follows D, D, Ef1, Ef2, Ef3, Wf after a delay of 1τ as shown in the number 6 of the timing chart of Fig. 5. This makes no use of the result of the floating point addition of instruction 6. In this example which has no data-dependent relationship with it and makes no use of the throwing-away method, the basic timing becomes D, D, D, E, W with the D cycle prolonged by 2τ as shown in the seventh instruction of Fig. 5. Subsequently, the eighth Compare instruction and the ninth Branch instruction are performed in pipeline by D, E, W and, when a jump is made to the instruction 5 at the instruction 9, a delay of 1τ is produced as branch penalty to start D, E, W. The timing chart of this operation using the throwing-away method of the computer of the present invention is shown in Fig. 6. Instructions numbers 1 to 4 are the same as those in Fig. 5. At that part of the instruction which uses the cache, the cache operation is performed asynchronously as shown, by 5-asynchronization and the P1, C, W1 cycles are performed such that they are asynchronous. The C cycle of 5-asynchronization overlaps W of 5 and they are performed simultaneously. The execution is faster than the case of Fig. 5. In the floating-point arithmetic of the instruction 6, the execution is performed using the instructions 6 and 6-asynchronization and after decoding advance can be made to the 6-asynchronization state using the throwing-away method. As shown, the output of C of 5-asynchronization is used as the input of Ef1 of 6-asynchronization. In subsequent asynchronous processing of the instruction 7, its D cycle can be performed like the E cycle of the instruction 6, that is, the Pf cycle of 6-asynchronization. Thus, in the case of Figs. 5 and 6, the throwing-away method is faster than the case making no use of the method by 3τ. The instructions 8, 9, 10 are the same as those in the previous case. The resuming operation for asynchronous processing interruption of the present invention and the invention relating to data-dependent accounting are used in a computer using such a throwing-away method. Next, a first embodiment of the present invention will be described with reference to Fig. 7. First, each constituent element of Fig. 7 will be described. As shown in Fig. 8, the instruction format is as follows. OPC: Instruction code. The position parts of other fields of an instruction may be ignored, depending on the value of the OPC. It is assumed that whether the instruction bits 17 to 31 indicate GR or FR is determined by the value of the OPC as follows. When the most significant bit of the OPC is a 0: the instruction bits 17 to 31 indicate GR. When the most significant bit of the OPC is a 1: the instruction bits 17 to 31 indicate FR. However, with an instruction for data transfer between main storage and FR, although the most significant bit of the OPC is a 0, it is assumed that the bits 17 to 26 indicate GRN1, GRN2 and the bits 27 to 31 indicate FR3. At this point, it is assumed that GR1 + GR2 + IMM indicate an effective address and FRN indicates transmission source or destination FR when the data is transmitted to or from the main storage. IMM: Immediate data (input) GRN1: GR Number 1, input GR register number 1 GRN2: GR Number 2, input GR register number 2 GRN3: GR Number 3, output GR register number 3 FRN1: FR Number 1, input FR register number 1 FRN2: FR Number 2, input FR register number 2 FRN3: FR Number 3, output FR register number The kinds of synchronous processing and asynchronous processing and the kinds of interruptions 2-1 synchronous processing 1 ○ Arithmetic processing of a short execution time 2 ○ Branching process, program calling process (process for modifying the instruction executing ) 3 ○SVC (supervisor call) process 4 ○CR (control register) accessing process (excluding a process for modifying only CC in PSR) 5 ○ Asynchronous processing queue copying register accessing process 2 - 2 Asynchronous processing 1 ○ Arithmetic process of a long execution time 2 ○ Transfer process between GR and main storage and transfer process between FR and main storage 2 - 3 Interruption 1 ○ Program interruption Outputs of a CPU-resource-using-process-dependent interruption and a CPU-resource using process indicate values different from expected values. 2 ○ SVC (supervisor call) process This is an interruption whose interruption factor is generated at the time of execution of an SVC instruction. The low order seven bits of the IMM part of an SVC instruction + 0 x 80 are used as a call number. 3 ○ External interruption This is an interruption whose interruption factor is an external interruption signal which is externally input to the CPU. The external interruptions have levels 0 to 15. Only external interruption signals with levels above EAL of PSR are accepted to initiate interruption. CPU resources accessed by asynchronous processing In the case of asynchronous processing, access is made to only CR, FR and CC among CPU resources. Processes of accessing the CR and the asynchronous processing queue copying register comprise only synchronous processes. Description of each hardware unit 4 - 1 CPU resources 1 ○ GR (General purpose register) This general purpose register is used as a base register or an index register for addressing destination of the input/output of an operation or a main storage. GR is 32 bits in length and 32 GRs are present. GR numbers 0 to 31 are uniquely allocated to the GRs. GR0 holds 0 at all times. The writing into the GR0 is ignored and a 0 is always read when the GR0 is read. 2 ○ FR (floating point register) This is a register which is used for inputting/outputting floating-point arithmetic. An FR is 64 bits in length and 32 FRs are present. Unique FR numbers 0 to 31 are allocated to the FRs. The FRO holds a 0 at all times. The writing into the FRO is ignored. A 0 is always read when the FRO is read. 3 ○ CR (control register) This is a register for holding parameters to control the operation of the CPU. 32 CRs each of 32 bits in length are present. The CR0 to CR4 are allocated the following parameters. CR0: PSR (Processor Status Register) This register holds parameters (supervisor mode/user mode, etc.) for defining the main operating environment of a program. The PSR contains a CC (Condition Code: Condition Code Area) of 2 bits in length and an EAL (External Interrupt Accept Level) of 4 bits in length. The CC becomes a candidate for outputting in specific processing and is used as an input for branch determination in conditional branch processing. The EAL defines the level of an accepted external interruption factor. Only external interruption signals having a value larger than the EAL are accepted to initiate interruption operation. CR1: OPSR (Old PSR) This is a register for holding the PSR value prior to the occurrence of an interruption at the time of the occurrence of the interruption. CR2: OIC (Old Instruction Counter) This is a register for holding the PC value (which points to the address of an instruction to be executed next) prior to the occurrence of an interruption at the time of the occurrence of the interruption. CR3: OLEP (Old Last Entry Pointer) This is a register for holding the last entry pointer value of a run queue of asynchronous processes after wait for the termination of the asynchronous processes. CR4: INTD (INTerrupt Designation) This is a register for holding a code (INTTYPE) indicating the type of an interruption at the occurrence of the interruption and a termination code (LSRETC) of an asynchronous process executed last at the occurrence of a program interruption in the form shown in Fig. 9. For example, the following values are allocated to the INTTYPE. 0 x 00 - 0 x OF: reserved 0 x 10 : program interruption 0 x 11 - 0 x 1F: reserved 0 x 20 - 0 x 2F: external interruptions of level 0 to level 15. (L + 32) indicates an external interruption of level L. 0 x 30 - 0 x 7F: reserved 0 x 80 - 0 x FF: supervisor calling interruptions with call numbers 0 x 80 - 0 x FF. The low-order 7 bits of the IMM value of a SVC instruction + 0 x 80 is a supervisor call number. CR5: INTB (INterrupt Base address) This is a register for holding the base address of an address newly set in an IC (Instruction Counter) at the time of the occurrence of an interruption. INTB + INTTYPE*16 is set as a new count of the IC at the time of the occurrence of an interruption. CR6: NPSR (New PSR) This is a register for holding a value newly set in the PSR at the time of the occurrence of an interruption. CR7 to CR31: These are used as registers for holding parameters defining other program operating environments. 4 ○ Asynchronous Process Copy Register This is a register onto which the contents of an asynchronous process queue after wait for the termination of an asynchronous operation is copied at the time of the occurrence of a program interruption. There are 32 asynchronous process copy registers each of which is 64 bits in length, but the APCR0 holds a 0 at all times. Each of the APCRs has the following form. When the OLEP is not 0 at the time of the execution of an RTN (ReTurN), the contents of the APCR1 to APCR(OLEP) are written into an asynchronous process queue. 4 -2 Instruction Buffer (IB) This is the same as a usual CPU instruction buffer. An instruction to be executed is fed into this instruction buffer temporarily. Reading an instruction from main storage into the instruction buffer is performed in the same manner as in usual computers. 4 - 3 Instruction Execution Controller This is a unit for controlling instruction execution and interruption. This performs the control of instruction fetch containing branches, decoding of instructions, processing execution control, control of interruption operations and interruption operations. For the operation of the instruction execution controller, refer to the description of the asynchronous process queue below. The instruction execution controller includes the following registers. 1 ○ IC: Instruction Counter This is a counter for indicating the address of an instruction to be executed next. 2 ○ SRETC: Synchronous process RETurn code This is a register for holding the termination code of a synchronous process. 3 ○ SVCC: SVC code This is a register for holding the SVC code of an SVC instruction executed immediately before. 4 - 4 Asynchronous process execution unit This is a unit prompted by the instruction execution controller to execute a synchronous process. The SRETC (Synchronous process RETurn code) in the instruction execution controller is set in accordance with the result of the execution of the process. 4 - 5 Asynchronous process queue This is a queue for holding an asynchronous process being executed and asynchronous processes initiated by instructions and waiting for execution. There are 31 entries APQE1 to APQE31. Each of the entries comprises an instruction code, a termination code (RETC: 8-bit length) and an execution ID (EXID). The entries ranging from APQE1 to APQE(SEP - 1) are being executed. APQE(SEP) is an entry to be executed next. APQE(SEP + 1) to APQE(LEP) are entries which are initiated by instructions but are placed in the execution wait state. APQE(LEP + 1) indicates an entry to be enqueued next. There are the following register interference detection facilities for the instruction buffer and an entry pointed to by a starting-point pointer. When, in the following register interference detection facility, the CR number in the instruction buffer is 0 or the GR number in the entry pointed to by the starting-point pointer is 0, it is determined that the area is not included in an area for comparison. 1 ○ Instruction Buffer (IB) The facility for determining whether or not IB.GRN1 is included in the GRN3 area of APQE1 to APQE(LEP) The facility for determining whether or not IB.GRN2 is included in the GRN3 area of APQE1 to APQE(LEP) The facility for determining whether or not IB.GRN3 is included in the GRN1, GRN2 or GRN3 area of APQE1 to APQE(LEP) In the case where the instruction in IB specifies FR, three similar facilities are provided. The facility for determining whether or not a process (OPC) for modifying CC is included in APQE1 to APQE(LEP) when IB.OPC is a process for modifying or referring to CC. When IB.OPC is not a process for accessing CC, it is determined that there is no interference by CC. When there is any one of these interferences, the data interference signal line to the instruction execution controller is a 1. 2 ○ Entry (Start Entry) pointed to by starting-point pointer The facility for determining whether or not SE.GRN1 is included in the GRN3 area of APQE1 to APQE(LEP) The facility for determining whether or not SE.GRN2 is included in the GRN3 area of APQE1 to APQE(LEP) The facility for determining whether or not SE.GRN3 is included in the GRN1, GRN2 or GRN3 area of APQE1 to APQE(LEP) In the case where the instruction in SE specifies FR, three similar facilities are provided. The facility for determining whether or not a process (OPC) for modifying CC is included in APQE1 to APQE(SEP-1) when SE.OPC is a process for modifying CC. When SE.OPC is not a process for modifying CC, it is determined that there is no interference by CC. Enqueuing into and dequeuing from the asynchronous process queue are performed by an enqueue and dequeue controller as follows. 1 ○ Enqueuing When detecting that an instruction in the instruction buffer indicates asynchronous processing, the instruction execute controller issues a request for enqueuing of an asynchronous process to the enqueue and dequeue controller. When the LEP is less than 31, the enqueue and dequeue controller adds 1 to the LEP and copies the contents of the instruction buffer into an entry pointed to by the new value of the LEP. The RETC and EXID of the entry is initialized to 0. When the LEP is 31, the asynchronous process queue is full and a new entry cannot be enqueued. In this case, the execution of an instruction is delayed until an entry has been dequeued from the queue. 2 ○ Dequeuing When a process having an entry number smaller than the starting point pointer (SEP) is terminated without a program interruption factor, the asynchronous process execute controller specifies EXID to prompt the enqueue dequeue controller to dequeue the entry. The enqueue dequeue controller shifts each of entries following the entry having the specified EXID to its previous entry and decrements each of the SEP and LEP by one. 4 - 6 Enqueue dequeue controller The enqueue dequeue controller is a unit which holds the starting entry pointer (SEP) and the last entry pointer (LEP) and performs the next operation. 1 ○ When prompted by the instruction execute controller, the enqueue dequeue controller enqueues the contents of the instruction buffer into the last location of the queue. 2 ○ After a wait for the termination of an asynchronous operation at the time of the occurrence of a program interruption factor, the controller is prompted by the instruction execute controller to copy the contents of APQE1 to APQE(LEP) into APCR1 to APCR(LEP) and the value of LEP into OLEP. Subsequently, a 0 is set in the LEP and a 1 is set in the SEP. 3 ○ The EXID specified by the asynchronous process execute controller is written into an entry pointed to by the SEP and the SEP is incremented by one. 4 ○ The entry having the EXID specified by the asynchronous process execute controller is dequeued. 5 ○ A specified value is set in the RETC of an entry having the EXID specified by the asynchronous process execute controller. 4 - 7 Asynchronous process execute controller The asynchronous process execute controller performs the determination of initiation of the entry pointed to by the SEP, the control of execute initiation of transmission of the instruction code and EXID to the process execute unit and processing thereof and the control at the time of termination of an asynchronous process. For the operation of the asynchronous process execute controller, refer to the description of the asynchronous process queue above. The asynchronous process execute controller includes the following two 31-bit length registers. 1 ○ EXIDB (EXID Busy flag) This is a register consisting of 31 flags EXIDB#1 to EXIDB#31 each of one bit. The EXIDB#(X) indicates whether or not an asynchronous process having the X value as the EXID is used in the following manner. 0: The EXID of the X value is not used. 1: The X value is used as the EXID. An asynchronous process having the X value as the EXID is either being executed or has been terminated as a result of detection of a program interruption factor. 2 ○ EXIDR(EXID interRupt flag) This is a register consisting of 31 flags EXIDR#1 to EXIDR#31 each of one bit. 0: A process having the EXID of the X value is not present or being executed. 1: A process having the X value as the EXID has been terminated as a result of detection of a program interruption factor. The asynchronous process execute controller is responsive to reception of the following signals from the instruction execute controller to perform a specific operation when it is a 1. 1 ○ Asynchronous process reset signal Upon receipt of this signal, the asynchronous process execute controller performs the following operation at a specific time. To set a 0 in the EXIDB. To set a 0 in the EXIDB. Also, the asynchronous process execute controller transmits the following two types of signals to the instruction execute controller. 2 ○ Asynchronous process program interruption signal This is a signal which assumes a value of the logical sum of all of bits of EXIDR#1 to EXIDR#31. Whether or not an asynchronous process is present which has been terminated as a result of the detection of a program interruption factor is indicated as follows. 0: There is no asynchronous process which has been terminated as a result of detection of a program interruption factor. 1: There is an asynchronous process which has been terminated as a result of detection of a program interruption factor. 3 ○ Asynchronous process termination signal This is a signal which becomes a 1 when there is no asynchronous process that is being executed and the asynchronous process execute controller is placed in the state in which a process in the asynchronous process queue is not initiated anew. This signal becomes a 1 in the following condition. The LEP is a 0, or all the EXIDBs are not 0s and the EXIDBs are equal to the EXIDRs. 4 - 8 Asynchronous process execute units These are units which are prompted by the asynchronous process execute controller to execute specific asynchronous processes. The units perform the following operations. 1 ○ To initiate a process in response to receipt of an instruction code and EID from the asynchronous process execute controller. 2 ○ To inform the asynchronous process execute controller of the EXID and RETC at the time of termination of the process. Next, the instruction executing operation according to the first embodiment will be described using Figs. 11A and 11B. First, starting with [A] in the figure, four bytes are read from the address designated by IC into the instruction buffer. Next, a determination is made as to whether or not a program interruption factor relating to instruction reading has been generated. If YES, the value corresponding to the generated program interruption factor is output as the SRETC. If NO, a shift is made to [B] when there is no interruption operation initiation factor. The interruption operation initiation factor is that 1 ○ the SRETC is not a 0, 2 ○ the asynchronous process program interruption signal is a 1, 3 ○ the SVCC is not a 0, 4 ○ there is an external interruption signal having a greater level than the EAL. When there is an interruption operation initiation factor, a determination is made as to whether or not the OPC in the instruction buffer specifies an asynchronous process. If YES, a process in which the OPC in the instruction buffer is not defined is specified. If this specification is NO, a determination is made as to whether there is a data-dependent relationship between previous entries on the basis of the instruction in the instruction buffer and the LEP in the asynchronous process queue. If NO, the synchronous execute unit is prompted to execute processing, the synchronous execute unit outputs the result of execution as the SRETC at the time of termination of processing, the SVCC is set in the SVC process, 4 is added to the IC when the executed process is not a process for modifying the IC and a determination is made as to whether or not the SRETC is a 0 (there is a program interruption factor in an asynchronous process). If YES, a return is made to the first. When the OPC in the instruction buffer specifies an undefined process, a code indicating abnormality of the OPC is set in the SRETC. When the OPC in the instruction buffer does not specify non-synchronization, the enqueue dequeue controller is prompted to enqueue a process in the instruction buffer and a determination is made as to whether or not the asynchronous process queue is one byte. If NO, 4 is added to the IC and then a return is made to the first step, in Fig. 11A. Next, as shown in Fig. 11B, in the [B] process, a determination is made as to whether or not the asynchronous process termination signal is a 0. If YES, a determination is made as to whether or not the SRETC is a 0 or whether or not the asynchronous process program interruption signal is a 1. If NO, a determination is made as to whether or not the SVCC is a 0. If NO, the SVCC is copied into the INTTYPE, a 0 is set in the SVCC and then OPSR ← PSR and PSR ← NPSR are performed (with the EAL value unchanged). When the SVCC is a 0, the external interruption signal of the highest level is selected and the selected level is supposed to be L. After OPSR ← PSR, INTTYPE ← L + 0 x 20, PSR ← NPSR (with L set in the EAL), OIC ← IC, IC ← INTB + INTTYPE*16, a return is made to [A]. When the SRETC is not a 0, or when the asynchronous process program interruption signal is a 1 and the SVCC is not a 0, the IC is decremented by 4 and the SVCC is set to a 0. The enqueue dequeue controller is prompted to copy the asynchronous process queue into the asynchronous process queue copy register and initialize it. The enqueue dequeue controller copies APQE#1 to APQE#(LEP) into APCR#1 to APCR#(LEP). After the OLEP has been copied into the LEP, a 0 is set in the LEP and a 1 is set in the SEP. A 1 is output to the asynchronous process reset signal for a fixed period of time, during which period the asynchronous process execute controller sets the EXIDB and the EXIDR to 0. The SRECTC is copied into the LSRETC and 0 x 10 is set in the INTTYPE. And, OPSR ← PSR and PSR ← NPSR are performed with the EAL value unchanged. Next, a description will be made of the operation of the asynchronous process execute controller with reference to Fig. 12. When SEP < =LEP and EXID = 0, a determination is made as to whether or not there is a data-dependent relationship between an instruction in the entry pointed to by the SEP and an asynchronous process queue entry prior to the SEP and the asynchronous processing unit for executing a corresponding process is placed in the state to initiate the process. If YES, of the EXIDB#1 to EXIDB#31 a flag which holds a 0 and is the lowest in number is recognized. The number X is allocated as the EXID of the entry pointed to by the SEP. A 1 is set to the EXIDB#X. X is added, as the EXID, to the contents of the entry pointed to by the SEP and transmitted to an asynchronous process execute unit which executes the process. The corresponding asynchronous process unit initiates the process. X is added to prompt the enqueue dequeue controller to modify the SEP. After setting X to the EXID of the entry pointed to by the SEP, the enqueue dequeue controller adds a 1 to the SEP. Next, the EXID and the RETC (termination code) of the execution terminate process that each asynchronous process execute unit transmits are accepted. The following processes are performed on accepted sets of EXID-X and RETC-Y. When Y is a 0 (a program interruption factor is absent and the process is terminated), the enqueue dequeue controller is prompted to dequeue the entry having EXID-X. The enqueue dequeue controller shifts each of entries following the entry having EXID-X to the entry one entry before, The SEP and the LEP are decremented by one. A 0 is set to the EXIDB#(X). When Y is not a 0, the enqueue dequeue controller is prompted to set RETC-Y to the RETC of the entry having EXID-X. The enqueue dequeue controller executes this process. A 1 is set to the EXIDR#(X). The process flow fqr the RTN instruction in [C] in the flow shown in Fig. 11A is shown in Fig. 13. If LEP is 0 (SEP is 1), PSR ← OPSR, IC ← OIC are set and the enqueue dequeue controller is prompted to transfer the contents of the asynchronous queue copy register to the asynchronous process queue. After copying the contents of APCR#1 to APCR#(OLEP) to APQE#1 to APQE#(OLEP), the enqueue dequeue controller sets LEP - OLEP. The end of [C] is reached and when LEP is not 0, it is handled as NOP. Next, a data-dependent relationship examining circuit used in the present invention will be described with reference to Fig. 14. In Fig. 14, by ORing QE#X conflicts IB N1 signals for all the asynchronous queue entries, the presence or absence of a data-dependent relationship for N1 areas in IB can be detected. The same is true of N2 area in IB. For N3 area in IB, a comparison is made with all N1, N2 and N3 areas of each queue entry. The data-dependent relationship between entries pointed to by SEP(start entry pointer) may be detected by the following two methods. (1) A method by which QE#X (queue entry #X) is placed in the position of IB of Fig. 14 and a circuit for detecting a data-dependent relationship between QE#X and each of QE#X1 to QE#(X-1) is provided for each QE. (2) An asynchronous process execute initiation buffer (APSB: Asynchronous process Start Buffer) is provided and the entry pointed to by SEP is copied into the APSB buffer. Such a data-dependent relationship detecting circuit is provided between the APSB buffer and each Q E. In Fig. 14, IB is replaced by APSB. Also, LEP and its decoder are replaced by SEP and its decoder, respectively. A dependent relationship between the instruction buffer of Fig. 7 and the #-th asynchronous queue entry of 32 asynchronous queue entries is examined. If a dependent relationship is present, QE# _ Conflicts_IB_ N1 is set to 1. An instruction that enters the instruction buffer is the newest one and its dependent relationship with instructions that entered in the past is examined. First, the OPC of the instruction buffer, that is, the type of instruction is examined by decoding. Instructions are classified into instructions specifying GR and instructions specifying FR. N1, N2, N3 indicated in the instruction buffer correspond to N1, N2, N3 of GR or N1, N2, N3 of FR. They are made clear by decoding OPC. GR or FR is seen by the most significant bit of the OPC. It is GR when the most significant bit is 0, and it is FR when the most significant bit is 1. A decoded output, for example, IB N1 GR by OPC, is a signal which becomes 1 when N1 is GR as a result of decoding of OPC. The same is true of N2, N3. Likewise, a determination can be made as to whether each field of N1, N2, N3 is Gr or FR by decoding the OPC of an instruction in an asynchronous queue entry. For example, QE# x N3 GR by OPC is a signal which goes to a 1 when the x-th asynchronous instruction in the asynchronous queue is N3 field GR and so on. The N1 field in the instruction buffer 1B is decoded and 1B N1 NOT 0 goes to a 1 when all 0s are not detected. When the N1 area is 0, the specified instruction makes no conflicts (data-dependent relationship) with the queued instruction. When N1 is 0, there is no data-dependent relationship because the contents of GRO or FRO specified by N1 are zero-fixed. Conversely, when 1B N1 NOT 0 is 1, there is the possibility of conflicts. AND 1 outputs a 1 when the N1 area is GR and the N1 area is not O. Likewise, when the N1 area is GR and the N1 area is not 0, 1 becomes 1 at the output of AND 2. The same is performed on N3. AND 5 outputs a 1 when the N3 area is GR and the N3 area is not 0. AND 6 outputs a 1 when the N3 area is FR and the N3 area is not 0. But, each of the ANDs 5, 6 is supplied with AQE#X LEP valid, which is a signal which is obtained by decoding the last entry pointer LEP of the queue and goes to a 1 when the entry #X whose asynchronization process is not yet executed is before the last entry or does not yet produce the result of the execution. The ANDS 3, 4 see whether N1 in the instruction buffer is GR, its contents are not 0, and the same GRN1 as it is the same GR indicated by N3 of queuing. It is determined whether N1 of OPC is GR and the GR has become N3 of a queued instruction, that is, whether N3 of the GR instruction buffer receiving the results of an asynchronous queue process is the same as N3 of the asynchronous queue. But, each of ANDs 5, 6 is supplied with AQE#X LEP valid, which is a signal which is obtained by decoding the last entry pointer of the queue and goes to a 1 when the #X-th entry whose asynchronous process has not been executed yet is before the last entry or has not yet produced the result of the execution. The ANDs 3, 4 see whether N1 in the instruction buffer is FR, its contents are not 0, and the same GRN1 as it is the same FR indicated by N3 of queuing. It is determined whether N1 of OPC is Gr and the GR has become N3 of a queued instruction, that is, whether N3 of the FR instruction buffer receiving the results of an asynchronous queue process is the same as N3 of the asynchronous queue. By ORing the outputs of the ANDs 3 and 4, a signal indicating the presence or absence of the whole dependent relationship is produced. Each of the ANDs 3 and 4 produces a signal which goes to a 1 when a comparison in 5 bits between the contents of N3 of the asynchronous queue entry and the contents of N1 of the instruction buffer indicates equality. QE#1N3 eqn 113N1 is input as a condition. That is, there is a data-dependent relationship when N1 of GR specified is equal to N3 (N3 used as the result) of GR of the asynchronous queue. The same is true of F1. When F1 of IB is equal to F3 of the queue, there is a data-dependent relationship. Since the number of the instruction buffer is one and the number of the asynchronous queues is 32, the number of the circuits which are the same as that of Fig. 14 is 32. Fig. 15 illustrates a second embodiment of the present invention which is distinct from the first embodiment shown in Fig. 7 in that, instead of using the asynchronous process queue copy register, an asynchronous process freeze signal is applied to the asynchronous process queue to fix the contents of the asynchronous process queue. Further, the second embodiment is distinct from the first embodiment in that SEP, LEP, EXIDB, EXIDR are made accessible as CR and an asynchronous process reset signal 1 is used as the asynchronous process freeze signal 1. Fig. 16 is a flowchart of the operation of the instruction execute controller in the second embodiment which corresponds to the flowchart of the first embodiment shown in Fig. 11B. First, following [B] of Fig. 11A, a determination is made as to whether the asynchronous process terminate signal is 0. When YES, a determination is made as to whether SRETC is 0 or whether the asynchronous process program interruption signal is 1. If NO, a determination is made as to whether SVCC is 0. When SVCC is not 0, SVCC is copied into INTTYPE, a 0 is set to SVCC, and OPRS - PSR, PSR - NPSR are set. In this case, the EAL value remains unchanged. In the presence of an asynchronous process program interruption, a 1 is set to PRS When SVCC is 0, an external interruption signal with the highest level is selected. Let the selected level be L. OPSR ← PSR, INTTYPE ← L + 0 x 20, PSR - NPSR with L set to EAL. After OIC ← IC, IC ← INTB + INTTYPE*16, return is made to A. When SVCC is not zero or the asynchronous process program interruption signal is one, if SVCC is not 0, IC is decremented by 4 and SVCC is set to zero. Next, a determination is made as to whether or not the asynchronous process program interruption signal is one. When YES, the asynchronous process freeze signal is set to one and SRETC is copied into LSRETC. 0 x 10 is set in INTTYPE and OPSR ← PSR, PSR ← NPSR. The EAL value remains unchanged and, in the presence of an asynchronous process program interruption, one is set in PSR. When the asynchronous process program interruption signal is not one, SRETC is copied into LSRETC without making the asynchronous process freeze signal one. Fig. 17 illustrates a flowchart of the RTN instruction shown in [C] of Fig. 11A in accordance with the second embodiment, which corresponds to Fig. 13 of the first embodiment. When LEP is zero (SEP is one). PSR ← OPSR, IC ← OIC and LEP is handled as NOP when it is not zero. [C] comes to an end. As described above, according to the present invention, there is provided an interruption handling system which can speed up asynchronous CPU resource using processes, execute basic CPU resource using processes used by an interruption handler asynchronously and produce the interruption handler easily. Further, asynchronous execution of basic asynchronous CPU resource using processes used by the interruption handler is possible and for a necessary CPU resource using process dependent factor, an interruption system for permitting an original program to be resumed becomes possible after termination of a corresponding process by the interruption handler.

Claims: An interruption handling system comprising: an instruction buffer (IB) to store an instruction; and queuing means for determining for the instruction stored in the instruction buffer (IB) which of a synchronous process or an asynchronous process is indicated and queuing the instruction when an asynchronous process is indicated; characterised by further comprising: means for indicating, when more than one queued asynchronous process is terminated under exceptional circumstances, contents and termination methods of all of the queued asynchronous processes terminated under exceptional circumstances, according to a data-dependent relationship and an interruption factor so as to enable resumption of each queued asynchronous process, the said exceptional circumstances including: without beginning processing; with an exception in a case where an interruption is generated as a synchronous process or as an asynchronous process by an external interruption; wherein a data-dependent relationship exists between two processes if the later process uses the result of the prior process or the later process overwrites the result of the prior process; and wherein an interruption factor indicates a satisfied condition causing the interruption. An interruption handling system according to claim 1, wherein said means for indicating includes means for saving all queued asynchronous processes in a register (asynchronous process copy register) different from said queuing means. An interruption handling system according to claim 1, wherein said means for indicating includes means for freezing (fixing) the at least one queued asynchronous process in said queuing means. An interruption handling system according to any preceding claim, further comprising: data-dependent relationship checking means for detecting a data-dependent relationship by checking whether a register (GR, FR) designated by said queued instruction and a register (GR, FR) designated by said input instruction are identical; and processing means for checking a data-dependent relationship between a prior process in an asynchronous queue and a later process queued after the prior process in said asynchronous queue and for executing processes while keeping the data-dependent relationship therebetween. An interruption handling system according to any preceding claim, further comprising: control procedures for resuming asynchronous processes terminated under exceptional circumstances. An interruption handling system according to any preceding claim, wherein processes for performing inputting from CPU resources such as registers (GR, FR) outputting from said CPU resources or both of them are classified into two types of synchronous CPU resource using processes and asynchronous CPU resource using processes, and the system further comprises: (1) synchronous instruction/asynchronous instruction processing means 1 ○ for initiating a synchronous CPU resource using process by an instruction, executing it synchronously with the execution of the instruction and terminating the synchronous CPU resource using process initiated by the instruction at the termination of the execution of the instruction and 2 ○ for initiating an asynchronous CPU resource using process by an instruction, executing it asynchronously with the execution of the instruction and terminating the asynchronous CPU resource using process initiated by the instruction after the termination of the execution of the instruction; (2) data-dependent relationship processing means in which, when an asynchronous CPU resource using process (preceding process) for performing an outputting operation to a CPU resource is initiated by an instruction and when an output to the resource of the preceding process is used as input in a CPU resource using process (succeeding process) initiated by an instruction issued after the instruction which has initiated the preceding process, that is when there is a data-dependent relationship, the input to the resource in the succeeding process is waited until the output to the resource is terminated in the preceding process, when the CPU resource using process (succeeding process) performs an output operation to a resource, the succeeding process performs output operation to the resource after access to the resource by all of CPU resource using processes (preceding processes) initiated prior to the succeeding process, when the succeeding process is a synchronous CPU resource using process, the termination of an instruction designating the succeeding process is delayed until access to a related resource in the prior process, that is, a program counter remains pointing to the instruction initiating the succeeding instruction, when the succeeding instruction is an asynchronous CPU resource using process, the termination of the execution of the instruction initiating the succeeding instruction may be delayed until access to the resource by the preceding process is terminated and access to the resource by the succeeding process may be delayed though the execution of the instruction initiating the succeeding instruction is completed and the succeeding process is initiated, when the execution of the asynchronous CPU resource using process is initiated, the output to the resource in the succeeding CPU resource using process is waited until its input is terminated; (3) state waiting means in which, when a CPU resource using process dependent interruption factor is detected in a CPU resource using process and an interruption is generated without directly depending on a result of the CPU resource using process, the interruption operations occur: (A) though the execution of a new instruction is not initiated, the instruction being executed continues to execute and the asynchronous CPU resource using process having its execution initiated waits for the executable CPU resource using process to terminate and for its state to vary no longer; (B) asynchronous CPU resource using process terminating means, after the termination of the CPU resource using process in step (A), terminate all the asynchronous CPU resource using processes which were being executed at the time of the initiation of the interruption operation, and synchronous CPU resource using process terminating means terminate the synchronous CPU resource using process upon termination of the instruction initiating the process and the synchronous CPU resource using process being executed when the (A) operation occurs also terminates. An interruption handling system according to claim 6, further comprising CPU resource using process dependent interruption control means, when part of synchronous CPU resource using processes and part of asynchronous CPU resource using processes detects the CPU resource using process dependent interruption factor and uses the output of the process as an input in the succeeding process, for making the result of the execution of the succeeding process different from an expected execution result. An interruption handling system according to claim 7, wherein the CPU resource using process dependent factor is an interruption factor detected when a specific event is generated while a CPU resource using process is being executed and the output of the process in which the CPU resource using process interruption factor is detected is the expected result, the interruption factor indicating that the use of the process output as an input in the succeeding process is not the expected result. An interruption handling system according to claim 6, wherein said asynchronous CPU resource using process terminating means completes without detecting a CPU resource using process dependent factor and the output of the process is the expected output. An interruption handling system according to claim 6, wherein said asynchronous CPU resource using process terminating means detects the CPU resource using process dependent factor and terminates the execution. An interruption handling system according to claim 6, wherein said asynchronous CPU resource using process terminating means is a process in which the asynchronous CPU resource using process uses the output to the resource of the preceding process, and the CPU resource using asynchronous process is terminated unprocessed when the preceding process detects a CPU resource using process dependent interruption factor and does not perform expected outputting, and the data-dependent relationship for the output of the process terminated unprocessed is erased. An interruption handling system according to claim 6, wherein said asynchronous CPU resource using process terminating means terminates an asynchronous CPU resource using process using said output of the process terminated unprocessed as an input as it is unexecuted and the data-dependent relationship for the output of the process terminated unexecuted is erased. An interruption handling system according to claim 6, wherein, when at least one asynchronous CPU resource using process dependent interruption factor is detected, said asynchronous CPU resource using process terminating process may terminate an asynchronous CPU resource using process which has already been initiated by an instruction and has no data-dependent relationship with the interruption factor as it is unexecuted. An interruption handling system according to claim 6, wherein said synchronous CPU terminating means completes without detecting a CPU resource using process dependent factor. An interruption handling system according to claim 6, wherein said synchronous CPU terminating means terminates the execution of a process by detecting a CPU resource using process dependent interruption factor. An interruption handling system according to claim 6, wherein (C) when none of CPU resource using process dependent interruption factors are detected: an interruption factor which has initiated an interruption operation is a CPU resource using process independent interruption factor and hardware is interruption generating means which generates an interruption corresponding to an interruption factor has initiated an interruption operation, (B) when at least one CPU resource using process dependent interruption factor is detected: interruption informing means is provided which simultaneously informs all of programs of information on CPU resource using asynchronous processes and CPU resource using synchronous processes by one CPU resource using process dependent interruption without depending on an interruption factor which has initiated the interruption operation, thereby performing a compound CPU resource using process dependent process, by performing the interruption operation of (3), that a CPU resource using process dependent interruption factor resulting from an asynchronous CPU resource using process whose execution has been initiated by a program which has been executed prior to the generation of an interruption is not detected after the generation of the interruption is ensured, and that all the CPU resources have been released after the generation of the interruption is ensured. An interruption handling system according to claim 6, wherein (5) further, when a CPU resource using process dependent interruption is generated, if only a CPU resource using process dependent interruption factor expected to be resumed is dependent as an interruption factor, there is the possibility that the original program can be resumed after the proper processing of all of generated CPU resource using process dependent interruptions which are expected to be resumed, resume-expected CPU resource using process interruption means is provided for each of processes which generated resume-expected CPU resource using process dependent interruptions and CPU resource using processes terminated unexecuted at the time of generation of a CPU resource using process dependent factor, for 1 ○ re-executing a process detecting a designated resume-expected CPU resource using process dependent interruption factor and a process terminated unexecuted when a CPU resource using process returning to the interruption-originating program, 2 ○ an interruption factor processing program displays information enough to simulate a process on a program at the time of an interruption, when a certain kind of CPU resource using process dependent interruption factor in which a program of the factor generating source to expected to resume and it is necessary to maintain the input data upon interruption, there is provided a resumption-expected CPU resources using process interruption means for terminating all the succeeding process in which the input resource of the process generating the factor is determined as the output destination, when the interruption factor is generated, thereby enabling a program generating an interruption factor to be resumed when a resume-expected CPU resource using process dependent interruption factor is generated. The interruption handling system according to claim 17, wherein: a part of CPU resource using process dependent interruption factors, being the kinds of CPU resource using process dependent interruption factors, which is sometimes expected to resume a program generating the interruption factor after executing an appropriate process by the corresponding interruption factor processing program and becomes an interruption factor e.g. for a page absence, is called a resume-expected CPU resource using process dependent interruption factor. An interruption handling system according to claim 1, further comprising a synchronous CPU resource using process initiated by a command for designating the process for using resources of a central processing unit (CPU) at least including a register (GR, FR) and executed synchronously with the execution of said command, as well as an asynchronous CPU resource using process initiated by a command for designating the process for using the resource of said central processing unit (CPU) and executed asynchronously with the execution of said command; said interruption handling system performing a control for preserving a data dependency relation between said synchronous CPU resource using process and an asynchronous CPU resource using process or between asynchronous CPU resource using processes; said interruption handling system for use by a data processor capable of performing an interruption generated either during an execution of said synchronous CPU resource using process or during an execution of an asynchronous CPU resource using process, said interruption generated for an interruption factor dependent on resource using process by said central processing unit (CPU) such as a program interruption and an interruption factor independent of a resource using process by said central processing unit (CPU) such as an input/output interruption; when any of said interruption factors is detected, i.e. upon terminating a command invoking said synchronous CPU resource using process and/or said asynchronous CPU resource using processes being executed by said central processing unit, said interruption processing system restraining a start of the next command, waiting for the termination of executing said plural asynchronous CPU resource using processes already initiated for a current execution, and causing a predetermined storing means to store a terminating condition for said asynchronous CPU resource using process; and said interruption handling system generating an interruption factor dependent on said asynchronous CPU resource using process when all executions of said asynchronous CPU resource using processes are terminated, said interruption handling system also restoring a hardware state of said central processing unit based on said asynchronous CPU resource using process terminating condition stored in said predetermined storing means when an interruption for said interruption factor generated is terminated. A method of operating a command processor comprising the steps of: storing an instruction; determining for the stored instruction which of a synchronous process and an asynchronous process is indicated; and queuing the instruction when an asynchronous process is indicated in the determining step; characterised by further comprising the step of: indicating, when more than one queued asynchronous process is terminated under exceptional circumstances, contents and termination methods of all the queued asynchronous processes terminated under the exceptional circumstances, in accordance with a data-dependent relationship and an interruption factor so as to enable resumption of each queued asynchronous process, the said exceptional circumstances including: without beginning processing; with an exception in a case where an interruption is generated as a synchronous process or as an asynchronous process by an external interruption; wherein a data-dependent relationship exists between two processes if the later process uses the result of the prior process or the later process overwrites the result of the prior process; and wherein an interruption factor indicates a satisfied condition causing the interruption.

Inventors: NAKAYAMA YOZO, UENO HARUHIKO, NAKAYAMA, YOZO, UENO, HARUHIKO, NAKAYAMA, YOZO, SAGAMINO-SAKURA, UENO, HARUHIKO, ROOM 1 FUJITOKI-SO 541, MIYAUCHI
Applicants: FUJITSU LTD, FUJITSU LIMITED
Application year: 1991
Main classification: G06F9
IPC codes: G06F9