JPH0438528A - In-line developing system for source program - Google Patents

Abstract

PURPOSE:To improve translation performance and file accessing performance by executing the in-line development of a source program prepared by a user into the source program of a calling source. CONSTITUTION:When a translating mechanism 1 is activated while preparing an in-line development process source program 2 and a calling source program 3 including an in-line development process call, a syntax analysis part 100 inputs the source program 2, executes syntax analysis and translates the program into an intermediate language. This intermediate language is stored in a main storage device 5. A segment memory allocation part 101 decides which position of the main storage device 5 stores an in-line development process segment 130 as the set of prepared intermediate languages. In that case, when an area for preparing the segment 130 in the main storage device 5 is lacked, the segment 130 is tentatively saved in an external storage device 6. Then, when the segment is required, it is recovered.

Description

[Detailed Description of the Invention] [Industrial Application Field] The present invention relates to a method of compiling a program written in a computer language, and in particular expands a source program inline to its caller and executes it, as shown in Figure 1. Concerning a method for generating efficient target programs.

[Conventional technology]

A preprocessor method is known as a conventional inline expansion method.

Regarding this method, see “Source Program Product V
O52/VO53FORTRAN77 source analysis function
FORT77/5AFJ 8080-3-272-10
It is described on page 20. The method described therein generates a new source program by expanding the calling procedure inline at the location where the inline expansion procedure is called.

That is, in FIG. 2, the preprocessor 8 executes a source program MAIN3 including an inline expansion procedure source program 5UB2 and an inline expansion procedure call 31.
When inputting, the source program 5U is placed at the inline expansion procedure call 31 of the source program MAIN3.
Expand B2 inline and create a new source program M
Outputs AIN7. The translation mechanism 9 inputs and translates this new source program 7 to generate the target program 4.

[Problem to be solved by the invention]

The above-mentioned conventional technology has a problem in that the operability is complicated because it requires a two-step procedure of creating an inline developed source program and translating the created source program. Furthermore, the source program developed inline is incorporated into the calling source program to create a new source program, making maintenance difficult.

An object of the present invention is to provide a means for inline expansion of a source program in a one-step procedure, which has the effect that the operation can be completed in one step, and the source program is one before inline expansion. Since it can be a book, it also has the effect of being easier to maintain.

[Means for solving the problem] In order to achieve the above purpose, the translation mechanism inputs a source program to be expanded inline, and the translation mechanism's parsing unit performs lexical and syntactic analysis to generate intermediate words. A segment memory allocation unit is provided for storing data in an area on a storage device.

It also includes a segment memory management unit that inputs a calling source program including a call to an inline expansion procedure and expands an intermediate word at a position where the inline expansion procedure is called.

〔Example〕

Next, embodiments of the present invention will be described with reference to the drawings.

FIG. 3 shows the configuration of a translation mechanism to which the present invention is applied.

1 is a translation mechanism, and a segment memory allocation unit 101
A syntax analysis unit 100. Segment memory management section 11
1, and a code generation section 120.

2 is the source program of the inline expansion procedure, 3 is the calling source program that includes the inline expansion procedure call, 4 is the target program file in which the translated target program is stored, 5 is the main storage device, and 6 is the external storage It is a device.

In FIG. 3, an inline expansion procedure source program 2 (hereinafter referred to as source program SUB) and a calling source program 3 including an inline expansion procedure call
(hereinafter referred to as source program MAIN) is prepared and the translation mechanism 1 is started. First, the syntax analysis unit 100 inputs the source program 5UB2, parses the syntax, and translates it into intermediate language.

The intermediate word is stored in main memory M5. The created collection of intermediate words will be referred to as an inline expansion procedure segment 130. At this time, the segment memory allocation unit 101 determines where in the main memory 5 the segment is to be stored. At this time, if there is insufficient area for creating segments in the main storage device i5, the segments are temporarily saved to the external storage device If6.

When the input of the source program 5UB2 is completed, the source program MAIN3 is input next, parsed, translated into intermediate language 140, and stored in the main storage device 5.

When the input of the source program MAIN3 is completed, the processing of the syntax analysis unit 100 is also completed, and then the inline expansion unit 110
is started.

The inline expansion unit 110 inputs the intermediate language 140 of the source program MAIN and inputs the intermediate language 140 of the source program MAIN to call position 1 of the external procedure SUB.
41, an intermediate word 150 obtained by inline expansion of the segment 130 of the source program SUB is stored on the main storage device. At this time, the intermediate language 140 of the source program MAIN
The segment memory management unit 111 determines whether the external procedure 5UB 141 called in is created as an inline expansion procedure segment 130.

The code generation unit 120 generates an intermediate word 150 after inline expansion.
is input, code is generated, and target program 4 is output.

FIG. 3 is an outline of the translation mechanism to which the present invention is applied.

Next, details of processing by the segment memory allocation unit 101 and the segment memory management unit 111 will be explained.

First, a table applied in the present invention will be explained using FIG. 4.

Module management table (MCT) 300: Created for inline expansion procedures. MCTMSCTP field 301 to register a pointer to the MSCT that manages the location of the inline expansion procedure segment, MCTNM field 302 to register the external procedure name, MCTNEXT field 303 to register the chain to the MCT for the next inline expansion procedure, MCT number It consists of an MCTN○ field 304 for registering.

Module area management table (MSCT) 310: Created corresponding to the MEMCT that manages the area in which the inline expansion procedure segment is created.

MSCTMEMP that registers a pointer to MEMCT that manages the area where the segment is stored on the main storage device
Field 311, MSCTDAS to register the destination address of the external storage device when the segment area is insufficient
D field 312, if the segment is multiple MEMCTs
The MSCTNEXT field 313 is used to register a chain to the next MSCT when spanning an area managed by the MSCTNEXT field.

Memory management table (MEMCT) 320: Manages the main storage area allocated for segments. MEMADDR field 321 that manages the area of the main storage device in fixed amounts and registers its address. It consists of a MEMMSCTP field 322 for registering a pointer to the MSCT that manages the segment currently using its own area, and a MEMMCTNO field 323 for registering the MCT number of the segment.

Main storage area management table (SCT) 330: Manages areas of the main storage device for segments and other areas for segments. It consists of a 5CTADDR field 331 for registering the address of the segment area and a 5CTSIZE field 332 for registering its capacity.

[Processing of segment memory allocation part]

The detailed processing of the segment memory allocation unit 101 will be explained using FIG. 5, FIG. 6, and FIG. 7. FIG. 5 is a processing flow of the segment memory allocation section, FIG. 6 is a data structure diagram when there is sufficient segment area, and FIG. 7 is a data structure diagram when there is a shortage of segment areas in FIG. 6.

The segment memory allocation unit 101 is activated by the syntax analysis unit 100. That is, the syntax analysis unit 100 first divides the main storage area into a segment area and other areas 5CT33.
The segment area address is registered in the 5CTADDR field 331 of 0, and the capacity is registered in the 5CTSIZE field 332.

After this, inline expansion procedure source program 5UB
2 is input, the syntax is analyzed, and an inline expansion procedure segment 130 is created. Since the segment area is managed by the segment memory allocation unit 101, the syntax analysis unit 10
0 activates the segment memory allocation unit 101 when the first source of the inline expansion procedure is input and when the segment area is insufficient.

In FIG. 5, when the segment memory allocation unit 101 is activated, it determines whether it is inputting a source at the beginning of an inline expansion procedure. MC when inputting the first source
Register the external procedure name SUB in the MCTNM field 302-1 of T300-1, and register 1, which is the MCT number of this segment, in the MCTNO field 304-1 (processing 1
001°1002).

Next, in order to determine the segment area for this inline expansion procedure, it is checked whether a certain segment area exists in the 5CT 330. If a segment area exists, MEMCT320-
1, and registers the segment area address in the MEMADDR field 321-1 and the MCT number of the segment, 1, in the MEMMCTNO field 323-1. From now on, this area will be used as the SCT segment area 33.
1 and managed by MEMCT 320-1 (processing 1003.1010).

After creating MEMCT320-1, next MSCT310
-11 is created. The MgCr 210 manages which MEMCT 320 manages the segment area in which the inline expansion procedure segment exists. M.S.
A pointer to the MEMCT is registered in the CTMEMP field 311-11 in the MEMMSCTP field 322-1, and a pointer to the MSCT 310-11 using its own area is also registered in the MEMCT 320-1. Since a segment includes a pointer in its information, it is always stored in the same segment area (process 1008).

In FIG. 6, the SUB inline expansion procedure segment requires segment areas managed by two MEMCTs 320-1.3202. Therefore, the segments are segment-1130-1, segment-2
MgCr 210-11 and 310-12 are created which are divided into 130-2 and manage the location of each segment.

The above is the flow of processing when there is a segment area, but the case where the segment area is insufficient will be explained using FIGS. 5 and 7. Inline deployment procedure 5UBI
When inputting the first source of , the syntax analysis unit 100 starts the segment memory management unit 101 . First, the segment memory management unit 101 creates an MCT 300-2 and reserves a segment area for the segment. In this case, since there is no free segment area, the MEMCT 320 used by other inline expansion procedure segments is searched.

Since the inline expansion procedure segment does not exchange information across multiple inline expansion procedures, the same segment area can be shared by multiple inline expansion procedure segments.

Therefore, MEMMCTN○ of MEMCT320-1
Since field 323-1 is 1 indicating the MCT number of SUB, this area is assigned to segment 13 of 5UB1.
Decided to use it as 0-1.

First, it is necessary to output SUB segment-1 to the external storage device 6 to make this area free.

Therefore, the segment memory management unit 101
MEMMSCTP field 322-1 of T320-1
MSCT310-11 of the segment using this area is obtained from the MSCT pointer of . MgCr210
-11 is determined root MSCTADDR field 312-
Check whether the external storage device address is registered in 11. Once a segment is created, its information does not change. Therefore, if it has already been registered, there is no need to output SUB segment -1130-1 to the external storage device 6 (processes 1004 and 1005).

If it is not registered, output segment-1 of SUB to external storage device 6 and send the destination address to MSCTDAS.
Register in D field 312-11 (process 1006)
.

With the above processing, the area managed by MEMCT320-1 becomes free, and since this area will be used by the 5UBI segment from now on, 2, which is the MCT number of 5UBI, is set in the MEMMCTNO field 323-1, and 5UBI is set in the MEMMSCTP field 322-1. Register a pointer to MgCr212-21 created for the segment (
Processing 1007).

Next, the segment memory management unit 101 uses the MSCT 310
ME that manages the segment area where the segment exists in the MSCTMEMP field 311-21 of -21
Register a pointer to MCT320-1 (process 100
B).

In process 1004, if there is no MEMCT 320 used in a segment of another inline expansion procedure, segment creation for the source program to be inline expanded is stopped. Therefore, the segment memory allocation unit 101 instructs the syntax analysis unit 100 to stop creating segments, and ends the process. However, the segments of other external procedures that have already been created remain valid and are subject to inline expansion (process 1009).

The MEMCT 320 of the segment being processed is determined by the above processing, and the syntax analysis unit 100 stores the inline expansion procedure segment in the segment area managed by this MEMCT 320.

[Processing of segment memory management unit]

The detailed processing of the segment memory management unit 111 will be explained using FIG. 7, FIG. 8, and FIG. 9. FIG. 8 is a processing flow of the segment memory management unit, and FIG. 9 is a table state transition diagram when the source program SUB of the inline expansion procedure segment created in FIG. 7 is inline expanded into the calling source program.

The segment memory management unit 111 includes an inline expansion unit 1
10 makes an external procedure call 141 while processing the intermediate language 140
is activated when it is recognized.

First, the segment memory management unit 111 scans the MCT 300 to check whether an inline expansion procedure segment has been created for the external procedure name 5tTB of the external procedure call statement 141.

In Figure 7, MCTNM field 3 of MCT300-1
Since the name SUB is registered in 02-1, SU
It is found that an inline expansion procedure segment exists for B (processes 1101-1103).

The inline expansion management unit 111 performs the inline expansion procedure S
In order to store the UB segment in the main memory, the current location of the segment managed by each MSCT 310 is checked.

The segment for MCT300-1 is MSCT310
-11 and MSCT310-12.

First, MEMCT320-1 that manages the main storage area of the segment of MSCT310-11 is
Searched from field 311-11, MEMCT320
MCT30 of the segment currently using area -1
0 is determined from the MCT number in the MEMMCTNO field 323-1.

MCT number of MEMCTNO field 323-1 is 2
Therefore, M of inline expansion procedure segment SUB
It does not match the MCT number 1 of CT300-1. Therefore, it turns out that the segment managed by MSCT 310-11 does not exist in the main storage (processing 11
04-1106).

In order to store the segments managed by the MSCT 310-11 in the main storage device, it is first necessary to output the segment currently using this area to the external storage device 6 to make this area free. however.

Since the contents of a segment are not changed once they are created, if the segment has already been output to the external storage device [6], there is no need to output it again.

The MSCT 310-21 that manages the segment currently using this area is also determined from the MSCT pointer in the MEMMSCTP field 322-1.

Since no external storage device address is registered in the MSCTDASD field 322-1 of this MSCT 310-21, it is necessary to output the segment to the external storage device [6 (process 1107).

The segment management unit 111 saves the segment 131-1 of SUB 1, which uses the area of MEMCT 3120-1, to an external storage device! 6 and output the cutting edge address to MSC.
MSC after registering in TDASD field 312-21
T310-11 MSCTDASD field 312-
The segment is input from the address of the external storage device No. 11.

The segment area of MEMCT 320-1 stores the inline expansion procedure segment of external procedure name SUB, so SU is stored in the MEMMCTNO field 323-1.
1, which is the MCT number for B, and segment 130-1 of SUB in the MEMMSCTP field 322-1.
A pointer to the MSCT 310-11 that manages the is registered (processes 1108 and 1109).

Through the above processing, the segment of MSCT 310-11 is stored in the main memory. Since the inline expansion procedure segment for SUB is also managed by the MSCT 310-12, it is checked whether the segment is stored in the main memory.

The segment managed by MSCT310-12 is MEMC
It is stored in the segment area managed by T320-2. The MCT number of the MEMMCTNO field 323-2 of the MEMCT 320-2 is 1, which is the MCT number of the SUB.
Therefore, it turns out that it is already stored. Now S
Since all inline expansion procedure segments for UB are stored on the main memory, the segment memory management unit 1
11 ends the process. The inline expansion unit 110 expands the inline expansion procedure segment of the SUB on the main storage device into the intermediate language 150.

In this way, the inline expansion procedure segment is expanded into the intermediate language of the calling source program, and the code generation unit 120 generates a code and outputs the target program.

〔Effect of the invention〕

As described above, the present invention has the following effects by expanding a source program prepared by a user inline into a calling source program.

■Source programs to be expanded inline can be managed at the source level.

■Inline expansion is possible without making any changes to the calling source program.

■Since source programs that are expanded inline are stored as intermediate words during translation, translation performance and file access performance are improved when multiple locations are called.

[Brief Description of the Drawings] Figure 1 is a diagram showing inline expansion according to the method of the present invention;
FIG. 2 is a diagram showing inline expansion using a preprocessor method, and FIG. 3 is a configuration diagram of a translation mechanism to which the present invention is applied.
Figure 4 is a diagram showing a table applied to inline expansion.
Figure 5 is a processing flowchart of the segment memory allocation unit, Figure 6 is a diagram showing the data structure when creating a segment when there is sufficient segment area, and Figure 7 is the data structure when creating a segment when there is insufficient segment area. FIG. 8 is a processing flowchart of the segment memory management unit, and FIG. 9 is a table state transition diagram. DESCRIPTION OF SYMBOLS 1... Translation mechanism in the method of the present invention, 2... Source program of inline procedure, 3... Source program including inline expansion procedure call, 4... Target program, 5... Main storage device, 6... External storage device, 7... Source program after inline expansion in preprocessor method, 8... Preprocessor,
9... Translation mechanism in preprocessor system, 100
... Syntax analysis section, 111 ... Segment memory allocation section, 110 ... Inline expansion section, 111 ... Segment memory management section, 120 ... Code generation section, 1
30... Inline expansion procedure segment, 140...
... Caller source program intermediate language, 150... Intermediate language after inline expansion. Figure 1 No.? Diagram Diagram Diagram

Claims (1)

[Claims] 1. In a compiler that inputs a program written in a computer language such as FORTRAN and translates it into machine language, the first program module specified by the user is
means for translating the first program module into an intermediate language and storing it in a main memory in order to expand it inline at a quotation location in another second program module; An inline development method for a source program characterized by having a main memory management means that saves it to an external storage device when the main memory is insufficient and restores it when it becomes necessary.