JPH0214334A - Debug device for data flow program - Google Patents

Abstract

PURPOSE:To easily and exactly execute the development of a data flow program by obtaining the condition of a change for the execution order and parameter value of a source program, which corresponds to the execution of the data flow program. CONSTITUTION:A debug executing device 10 simulates internal operation by data from an input file 20, the various types of instructions concerning debug from a command file 30 and the various types of information from an internal file 50. Then, the executed result of a data flow graph is stored in a result file 70. When the debug is executed, the node number of an executed node, names 210 of all the parameters in a function to be presently observed are displayed and also, the source program, to which the parameter belongs, is displayed with being divided into an unexecuted row 220 and an executed row 230. Thus, the development of the data flow program is easily and exactly executed.

Description

[Detailed Description of the Invention] [Industrial Application Field] The present invention relates to a debugging device for a data flow program, and in particular, it is possible to debug a source program by displaying a source program expanded into a data flow program as a variable. Related to debugging equipment.

[Prior Art] A conventional computer is a Neumann type computer in which various instructions are stored as programs in a program memory, and a program counter sequentially specifies addresses in the program memory to sequentially read out the instructions and execute the instructions. is the majority.

On the other hand, a data flow type information processing device is a type of non-Neumann type computer that does not have the concept of sequential execution of instructions using a program counter.

Such a data flow type information processing device follows an architecture that assumes that instructions are processed in parallel. As soon as the data to be operated on is available, instructions can be executed. Since multiple instructions are simultaneously driven by the data, the program is executed in parallel according to the natural flow of data. As a result, the time required for calculation can be significantly reduced.

FIG. 5 is a schematic block diagram showing an example of a conventional data flow type information processing device, and FIG. 6 is a diagram showing the basic structure of a data packet circulating through each part of the information processing device shown in FIG. 7 is a diagram showing a part of the data flow program stored in the program memory.

First, the configuration and general operation of the data flow type information processing apparatus will be described with reference to FIGS. 5, 6, and 7. Destination information is stored in the destination field of the data packet shown in FIG. 6, command information is stored in the command field, and operand data is stored in the data 1 field or data 2 field.

In FIG. 5, the program storage unit (PS) 1 includes a program memory, and as shown in FIG. 7, a data flow program consisting of destination information and command information is stored in the program memory. The program storage unit 1 reads destination information and instruction information by addressing based on the destination information of the data packet, stores each information in the destination field and instruction field of the data packet, and outputs the information to input buffers y2a and 2b consisting of FIFOs. .

A pair data detector (FC) 2 waits for data packets input from the program storage unit 1 via input buffers 2a and 2b, and selects one of the two data packets with matching destination information. The operand data of the other data packet is stored in a predetermined data field of the other data packet, and the manual buffer 3 consisting of FIFO is
Output to a. Note that at this time, one of the data packets mentioned above disappears.

The arithmetic processing unit (FP) 3 decodes the command information of the data packet input from the paired data detection unit 2 via the input buffer 3a, performs predetermined arithmetic processing on the two operand data, and outputs the result. It is stored in the data field of the data packet and output to the branching unit 4.

Based on the destination information of the data packet, the branching unit 4 either supplies the data packet to the input buffer 1a made up of FIFO, or sends the data packet to the input buffer 5a made up of FIFO.
It is applied to an external data memory (EDS) 6 via the external data memory (EDS) 6. Data packets from the input buffer 1a or data packets output from the external data memory 5 via the output buffer 5b are provided to a merging section 6, and the merging section 6 provides these data packets to the program storage section 1 on a first-come, first-served basis.

In the data flow type information processing device shown in FIG. 5, a data packet is sent from program storage unit 1 to data detection unit 2 to arithmetic processing unit 3 to branching unit 4 (→external data memory 5)→merging unit 6→ As the program storage unit 1 continues to rotate, arithmetic processing based on the program stored in the program storage unit 1 progresses.

FIG. 8 is a diagram showing a schematic configuration of the program storage section 1 shown in FIG. 5. As shown in FIG. In FIG. 8, an input data latch section 11 holds destination information and operand data of data packets, and instruction information is erased. The retained operand, new destination information and instruction information read from the program memory 13 based on the destination information are provided to the output data latch section 14 and latched. The destination information latched by the input data latch section 11 is given to the address calculation section 12, and the address of the program memory 13 is calculated from the destination information.

The program memory 13 stores a data flow program consisting of destination information and command information as shown in FIG.

[Problems to be Solved by the Invention] In the data flow type information processing device described above, an instruction can be executed as soon as the data to be subjected to an operation is prepared,
Programs are executed in parallel and asynchronously following the natural flow of data. Therefore, when a source program written to be executed on a normal von Neumann computer is expanded into a data flow program and executed, the execution order does not necessarily match the execution order on a von Neumann computer. There was a problem in that it was not possible to discover and correct errors in the source program by simply tracing the program.

Further, there are problems in that it is more difficult to discover errors when executing the developed data flow program, and it is also very difficult to know the correspondence with the source program.

Therefore, a main object of the present invention is to provide a debugging device for efficiently debugging a dataflow program executable on a dataflow type information processing device.

[Means for Solving the Problems] A data flow program debugging device according to the present invention includes a program storage means, a program execution means, a state storage means, a data transition storage means, a debug information storage means, and a debug information storage means. It is composed of a display means and a control means, the program storage means stores a data flow program, the program execution means includes a plurality of functional parts that simulate functions corresponding to the plurality of component parts in the processing device, and sequentially executes the data flow program stored in the program storage means. The state storage means stores changes in each variable defined in the source program of a plurality of functional parts of the program execution means, and the data transition storage means stores changes in each variable defined in the source program of a plurality of functional parts of the program execution means, and the data transition storage means stores changes in each variable defined in the source program of a plurality of functional parts of the program execution means. The debug information storage means stores debug information indicating the correspondence between each variable of the source program and each node of the data flow program, and the debug information storage means stores the progress status of processing and execution corresponding to each variable of the source program. The means controls the program execution means, the state storage means, and the data transition storage means according to the debug information stored in the debug information storage means. The debug information display means displays debug information regarding each variable of the source program in connection with the execution of each node of the data flow program.

[Operation] The debugging device according to the present invention creates a file indicating the correspondence between a source program and a data flow program, and the correspondence between variables in the source program and variables when executed as a data flow program. Therefore, the processing status of variables can be displayed in response to data flow programs that are executed sequentially. In addition, when executing a program in a simulated manner, the program is sequentially progressed each time a variable is determined by executing an instruction, and the state and data transition of each component of the data flow information processing device are The information is sequentially stored in the state storage means and the data transition storage means.

As a result, the execution order and execution information of the source program corresponding to the data flow program can be obtained.

[Example] FIG. 1 is a schematic block diagram of an embodiment of the present invention.

In FIG. 1, a debug execution device 1o is a part that simulates the internal operation of the data flow information processing device, and executes the operations of each component of the data flow type information processing device. As this debug execution device 10, a general information processing device (Neumann type computer) is used. The debug execution device 10 includes an input file 20, a command file 30, a console 40, and an internal file 50.
, the debug display file 60 , the result file 70 and the display 80 are connected.

The input file 20 is a part for inputting data necessary for causing the debug execution device 10 to execute a data flow program and perform debugging. This human file 20 includes a program file 21 and a debug information file 22. The program file 21 stores object programs of data flow programs and data used therein. Further, the debug information file 22 stores a source program list and information indicating the correspondence between the source program and the object program developed in a data flow type. The command file 30 stores various instructions related to debugging.
stores a group of commands to be executed by batch processing.

The console 40 is used to input various specifications related to debugging. The internal file 50 stores each line information used inside the debug execution device 10, and includes a PS file 51, a data packet file 52, and an EDS file/EDS map file (hereinafter referred to as the EDS file) 53. The PS file 51 stores a data flow program obtained by converting an object program given from the program file 21 into a format executable by the debug execution device 10. The data packets stored in the data packet file 52 correspond to data packets that circulate through each part of the data flow type information processing apparatus shown in FIG. 5 described above.

The EDS file 53 stores information regarding the storage contents and storage area allocation of a portion corresponding to the external data memory 5 shown in FIG.

The debug display file 60 stores changes in the display during debug execution in the debug execution device 10, and the result file 70 stores the results of execution of the data flow graph by the debug execution device 10.

Therefore, the results of the arithmetic processing based on the data flow program are stored in this result file 70. The display 80 displays the contents of the debug display file 60, the contents of the result file 70, and messages.

The object program given from the program file 21 is converted into a data flow program executable by the debug execution device 10 and stored in the PS file 51. Furthermore, data given from the program file 21 is stored in a data packet file 52. The debug processing by the debug execution device 10 shown in FIG. 1 is executed according to commands input from the console 40 or commands stored in the command file 30.

2 is a diagram showing an example of a source program debugged by the debug device shown in FIG. 1, FIG. 3 is a diagram showing a flow graph based on the source program shown in FIG. The figure is a diagram showing an example of a debug execution result according to an embodiment of the present invention.

In the flow graph shown in FIG. 3, the numbers in the circles on the right side indicate execution rank values, and the numbers on the left side indicate node numbers assigned in ascending order of the execution rank values. It is assumed that the programs are executed in the order of their node numbers. Therefore, when the source program shown in FIG. 2 is executed in the order of the node numbers, the display as shown in FIG. 4 will be displayed along with debugging.

First, the format of the display shown in FIG. 4 will be explained. When debugging, as shown in Figure 4, 10
The node number of the executed node is displayed at position 0, and the variable names 210 of all variables belonging to the currently viewed function are displayed, as well as all lines in the source program to which the variables belong. , a line that has not been executed 220 and a line that has been executed 230 are displayed separately.

The unexecuted line 220 is a line that has not yet been executed in the executable format developed into the data flow program, among all the lines in the source program to which the variable indicated by the variable name 210 belongs. The position indicates the line number. Since that line has not yet been executed, naturally the value of the variable in that line has not yet been determined.

Furthermore, the executed line 230 is a line that has already been executed among all lines in the source program to which the variable indicated by the variable name 210 belongs, and the line number is indicated at the position. That line has already been executed, and what value that variable had as a result of that line being executed is shown in parentheses. Note that it is possible that a plurality of unexecuted lines 220 and executed lines 230 exist for the same variable, and therefore, the plurality of values are separated by the symbol "," and displayed in order.

Node number 100. executed as described above. Variable name 21
0. Lines not executed 220. line executed, 230
As the data flow program is executed, the display changes as shown in FIG.

In other words, each piece of information displayed by the execution of the node 10 shown in FIG. The executed line 231 is changed, and finally the node 16 is executed, and the variable name 212
．． Instead of an unexecuted line 222 and an executed line 232, lines necessary for debugging are sequentially provided.

Next, we will explain in detail how the display changes as each node is executed. Since the value of the variable "X" is determined by the execution of node 10, the line number 10 related to the variable "X" that was displayed at the position of the unexecuted line 220 is displayed at the position of the executed line 230. Displayed together with the result (91). At the same time, variables inp, a, "b', c" belonging to those 10 rows
Similarly, the display moves from the position of line 220 that has not been executed to the position of line 230 that has been executed. However, the values of variables other than the variable "X" are not changed, so the variable values shown in parentheses are the same as the values in the 10th line and earlier.

Next, the expression on the 11th line is completed by the execution of node 13 shown in FIG. The display moves, and the calculation result (9) is shown in parentheses.
5) will be displayed.

Furthermore, the display of the other variable "CX" belonging to the 11th line also moves.

Finally, by executing the node 16, the expression on the 14th line is completed, and the output variable “ou” displayed at the variable name 212 position is
The value of "t" is determined as (2370) as written in the position of line 232 indicating that it has been executed, and the data flow program mentioned as an example ends.
In addition to "t", the display moves from line 222, which is not executed, to line 232, which is executed for the variable "Yr z". As a result, the values of all variables are determined, and the display moves.

As described above, debug information is provided, and the execution order and execution information regarding the source program to be executed by the data flow type information processing device are obtained.

[Effects of the Invention] As described above, according to the present invention, it is possible to obtain the execution order of the source program corresponding to the execution of the data flow program and the status of changes in variable values, that is, the processing and execution information of the source program. . Therefore, data flow programs can be developed neatly and accurately.

[Brief explanation of the drawing]

FIG. 1 is a schematic block diagram of an embodiment of the present invention. FIG. 2 is a diagram showing an example of a source program. Third
The figure shows an example of the case where the source program shown in FIG. 2 is developed into a data flow program. FIG. 4 is a display example of the execution results of debugging according to an embodiment of the present invention. FIG. 5 is a schematic block diagram of a conventional data flow type information processing device. FIG. 6 is a diagram showing the structure of a data packet circulating through each part of the information processing apparatus shown in FIG. 5. FIG. 7 is a diagram showing a portion of the data flow program stored in the program memory. FIG. 8 is a block diagram showing the configuration of the program storage section of the data flow information processing device. In the figure, 10 is a debug execution device, 20 is a manual file, 21 is a program file, 22 is a debug information file, 30 is a command file, 40 is a console, 50 is an internal file, 51 is a PS file, 52 is a data packet file, 53 is EDS file/EDS
A map file, 60 a debug display file, 70 a result file, and 80 a display. 1st session Figure 2 Program wain (inp; 0ut) inpu'L int inp; out, puL int OU'C; [ int a ” +07 int b = 20; int C = 47 irlj w, x, Xi X = inp −t a fb ” Ctw= c
-t-X; N = (b + c) umbrella X5 Z = Wya

Claims (1)

[Scope of Claims] A data flow program debugging device for debugging the operation of a data flow program in units of variables described in a source program, comprising: a program storage means for storing the data flow program; a program execution means that includes a plurality of functional parts that simulate functions corresponding to a plurality of component parts in a processing device to be executed, and that sequentially executes the data flow program stored in the program storage means; state storage means for storing changes in each variable defined in the source program of the plurality of functional parts of the means; Processes corresponding to each variable of the source program, data transition storage means for storing the execution progress status, debug information for storing debug information indicating the correspondence between each variable of the source program and each node of the data flow program storage means, debug information display means for displaying debug information regarding each variable of the source program in connection with the execution of each node of the data flow program, and the program according to the debug information stored in the debug information storage means. A debugging device for a data flow program, comprising an execution means, a control means for controlling the state storage means, and the data transition storage means.