JP2011107848A - Device, method and program for predicting size of executable object - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To support the efficient arrangement of wide range variables in a short direct addressing validating memory region (first region). <P>SOLUTION: A compiler 1 translates a source code 2 to generate a rearrangeable object 4, and generates a wide range variable reference information file 3 based on a memory reference instruction size table 9. A wide range variable list display part 5 predicts the size of an executable object based on the generated object 4 and the file 3. The table 9 describes the changing amounts of an instruction size due to the difference of the arrangement region of the wide range variables. The file 3 describes the changing amounts of a reference instruction size due to the difference of the arrangement region of the wide range variables. On the basis of the input of the changed wide range variables, the code size difference of the changed wide range variables is obtained from the calculation result, and the size of the object is adjusted, and the prediction value of the executable object size is calculated and displayed. <P>COPYRIGHT: (C)2011,JPO&amp;INPIT

Description

  The present invention relates to an executable object size prediction apparatus, a size prediction method thereof, and a program thereof.

  A short direct addressable memory area, which is an arbitrary memory area that can be accessed with a small code amount, is known. In the case of a device having a short direct addressable memory area, an instruction size for accessing the short direct addressable memory area is smaller than an instruction size for accessing a normal memory area. For this reason, the global variable arranged in the short direct addressable memory area can be accessed with a smaller code amount than the variable arranged in the memory area accessed by the normal addressing. (Patent Document 1, Non-Patent Document 1). Therefore, it is possible to improve the code efficiency of the program by appropriately selecting the global variable to be arranged in the short direct addressable memory area from the program.

  As a method for designating a global variable to be arranged in a short direct addressable memory area, there is a method of adding a description instructing the global variable to be arranged in the short direct addressable memory area in the source code (Non-patent Document 2). . Hereinafter, an information processing system for designating a wide-area variable in the short direct addressable memory area arrangement will be described with reference to FIG. FIG. 1 is a block diagram showing the configuration of the information processing system. This figure shows the configuration of the information processing system, and further shows the relationship between each tool and each input / output file when a global variable is specified in the short direct addressable memory area. This information processing system includes a compiler 101 and a linker 107. The compiler 101 translates the input source code 102-1 to 102-3 and generates relocatable objects 104-1 to 104-3. At this time, a code to be accessed by short direct addressing is generated for a wide-area variable designated to be arranged in the short direct addressable memory area in the source code 102. The linker 107 combines the plurality of relocatable objects 104-1 to 104-3 generated by the compiler 101, resolves external references and determines absolute addresses, and generates an executable object 108.

  Next, the operation of the information processing system will be described. FIG. 2 is a flowchart showing the operation of the information processing system. This figure shows the flow of processing for allocating a global variable in a short direct addressable memory area. First, regarding the source code 102-1 to 102-3, it is assumed that a link error other than a compile error or an oversize has been solved. The user modifies the source code 102-1 to 102-3 by an input operation to the information processing system, and adds a description instructing to be arranged in the short direct addressable memory area in the wide area variable (step S101). Next, the user executes the build of the source code 102-1 to 102-3 by an input operation to the information processing system (step S102). Subsequently, the compiler 101 compiles the source codes 102-1 to 102-3 to generate relocatable objects 104-1 to 104-3 (step S103). Next, the linker 107 links the relocatable objects to generate an executable object 108 (step S104). Thereafter, the user determines whether or not the code size of the executable object 108 satisfies a predetermined condition (step S105). As a result of the determination, when the code size of the executable object 108 does not satisfy the predetermined condition (step S105: NO), the above steps S101 to S104 are repeated. If the code size of the executable object 108 satisfies a predetermined condition (step S105: YES), the process for allocating the global variable in the short direct addressable memory area is terminated.

  As other related technologies, Patent Document 2 (Japanese Patent Application Laid-Open No. 2006-311610) and Patent Document 3 (Japanese Patent Application Laid-Open No. 09-186703) disclose data including a wired connection communication network system and a wireless access system. In the telecommunications system carrying as (C1-C10), in the radio system, there remains space available in the header field of the cell to transfer cell-oriented data for internal control in the radio system. A technique using a short addressing scheme is described. In Patent Document 4 (Japanese Patent Laid-Open No. 10-027129), the CPU accesses the upper short addressing area of the expansion RAM when the expansion RAM is present, and the CPU reads the address decoder unit by the switching setting signal when the expansion RAM 6 is not present. A technique for accessing an alternative area existing at the top of the standard RAM by controlling the above is described. In Patent Document 5 (Japanese Patent Laid-Open No. 05-35495), a variable having a high-speed access memory is allocated to the high-speed access memory in the order of variable processing, and variables that cannot be allocated to the high-speed access memory are A technique for allocating to memory is described. Patent Document 6 (Japanese Patent Laid-Open No. 10-124325) describes a technique for determining an arrangement area according to the access frequency of each variable. In Patent Document 7 (Japanese Patent Laid-Open No. 2004-38597) and Patent Document 8 (Japanese Patent Laid-Open No. 2006-114069), a compiler for a processor having a global area that can be accessed with one instruction is accessed with one instruction for each variable. A technique is described that makes it possible to specify an arrangement in a possible area or other area. Patent Document 9 (Japanese Patent Application Laid-Open No. 2006-58991) describes a technique for arranging data with a large number of accesses at a position close to a base address in order to reduce the program size and execution cycle.

JP 2002-099422 A JP 2006-311610 A JP 09-186703 A Japanese Patent Laid-Open No. 10-027129 JP 05-35495 A JP-A-10-124325 JP 2004-38597 A JP 2006-114069 A JP 2006-58991 A

NEC Electronics 78K / 0 Series Common User's Manual Instructions U12326JJ4V0UM00 NEC Electronics CC78K0 C Compiler User's Manual Language Edition U17016JJ1V0UM00

  As shown in the description of FIG. 1 and FIG. 2 above, when trial and error are performed such that a global variable is selected so as to improve the code efficiency of the program and placed in a short direct addressable memory area, a predetermined condition is satisfied. The following process must be repeated until That is, correction of the source code (addition of a description instructing the global variable to be placed in the short direct addressable memory area, step S101), execution instruction of the build process (step S102), compilation process (step S103), and Link processing (step S104). This repetitive process takes a very long time, which is not preferable in terms of work efficiency of program development.

  In FIG. 1, the compiler 101 processes each of the source codes 102-1, 102-2, and 102-3 one by one, and generates relocatable objects 104-1, 104-2, and 104-3. For this reason, the code size of the entire program is not known until the link process (step S104) for linking all object codes. For this reason, the code size of the executable object 108 cannot be known by the end of the build process (step S102). Therefore, it is necessary to execute the process up to the link process (step S104), which takes time, which is not preferable in terms of work efficiency of program development.

  Hereinafter, means for solving the problem will be described using the numbers and symbols used in the embodiments for carrying out the invention. These numbers and symbols are added with parentheses in order to clarify the correspondence between the description of the claims and the mode for carrying out the invention. However, these numbers and symbols should not be used for interpreting the technical scope of the invention described in the claims.

  The executable object size prediction apparatus of the present invention comprises a compiler (1) and a global variable list display section (5). The compiler (1) translates a plurality of source codes (2) to generate a plurality of relocatable objects (4), and based on the memory reference instruction size table (9) and the plurality of source codes (2) A plurality of global variable reference information files (3) are generated. The global variable list display unit (5) is generated by linking a plurality of relocatable objects (4) based on a plurality of relocatable objects (4) and a plurality of global variable reference information files (3). Perform size estimation of executable objects. However, the memory reference instruction size table (9) includes the code size of the instruction generated when the global variable is arranged in the first area as the short direct addressable area, and the memory in which the global variable is other than the first area. The difference in code size from the code size of the instruction generated when it is arranged in the second area as the area is described for each memory reference instruction. The file global variable reference information file (3) includes a code size required to refer to the global variable when the global variable included in the source code (2) is arranged in the first area, and the global It shows the code size difference from the code size required to refer to the global variable when it is assumed that the variable is arranged in the second area. Based on the global variable reference information file (3), the global variable list display unit (5) shows the relationship between each global variable, the area where the global variable is arranged, and the code size difference between the global variables. calculate. Then, based on the input of the changed global variable that changes the area to be arranged in each global variable, the code size difference of the changed global variable is obtained from the calculation result, and the changed global variable is used by using the code size difference. Adjust the code size of relocatable objects that contain variables. Based on the code size of the plurality of relocatable objects after adjustment, the predicted value of the executable object size is calculated using the same algorithm as that of the link.

  In the executable object size prediction apparatus of the present invention, the compiler (1) has a plurality of global variable reference information files corresponding to a plurality of relocatable objects (4) based on the memory reference instruction size table (9). 3) is generated. As a result, the global variable list display unit (5), based on the global variable reference information file (3), each global variable, the area where each global variable is arranged, and the code size difference between each global variable, Can be calculated. The code size of the changed global variable in the relocatable object can be adjusted based on this relationship and the changed global variable in which the area to be arranged among the global variables is changed. As a result, it is possible to calculate the predicted value of the executable object size based on the adjusted code size of the relocatable object.

  The executable object size prediction method and the program thereof according to the present invention include a step of translating a plurality of source codes (2) to generate a plurality of relocatable objects (4), and a memory reference instruction size table (9). Based on the step of generating a plurality of global variable reference information files (3) based on the plurality of relocatable objects (4) and the plurality of global variable reference information files (3), And 4) performing a size estimation of the executable object generated by linking the above. However, the memory reference instruction size table (9) includes the code size of the instruction generated when the global variable is arranged in the first area as the short direct addressable area, and the memory in which the global variable is other than the first area. The difference in code size from the code size of the instruction generated when it is arranged in the second area as the area is described for each memory reference instruction. The file global variable reference information file (3) includes a code size required to refer to the global variable when the global variable included in the source code (2) is arranged in the first area, and the global It shows the code size difference from the code size required to refer to the global variable when it is assumed that the variable is arranged in the second area. The step of executing the size prediction calculates the relationship between each global variable, the area where each global variable is arranged, and the code size difference between each global variable based on the global variable reference information file (3). Based on the input of the step and the change global variable that changes the area to be arranged among each global variable, obtain the code size difference of the changed global variable from the calculation result, and change using the code size difference Based on the step of adjusting the code size of the relocatable object including the global variable and the code size of the plurality of relocatable objects after adjustment, the predicted value of the executable object size is calculated using the same algorithm as that of the link. Steps.

  In the executable object size prediction method and the program thereof according to the present invention, the same effects as those of the executable object size prediction apparatus can be obtained.

  According to the present invention, it is possible to reduce the time required for trial and error to select a wide area variable so as to improve the code efficiency of the program and to arrange it in a short direct addressable memory area. That is, the development period can be shortened.

FIG. 1 is a block diagram showing the configuration of the information processing system. FIG. 2 is a flowchart showing the operation of the information processing system. FIG. 3 is a block diagram showing the configuration of the executable object size prediction apparatus according to the embodiment of the present invention. FIG. 4 is a block diagram showing details of the wide-area variable list display unit according to the embodiment of the present invention. FIG. 5 is a schematic diagram showing an example of a GUI screen of the wide area variable list display unit according to the embodiment of the present invention. FIG. 6 is a schematic diagram showing an example of the format of the global variable placement designation file according to the embodiment of the present invention. FIG. 7 is a schematic diagram showing an example of the format of the global variable reference information file according to the embodiment of the present invention. FIG. 8 is a schematic diagram showing an example of a memory reference instruction size table according to the embodiment of the present invention. FIG. 9 is a schematic diagram showing an example of an object size information table according to the embodiment of the present invention. FIG. 10 is a schematic diagram showing an example of the global variable reference information matrix according to the embodiment of the present invention. FIG. 11 is a flowchart showing the operation of the executable object size predicting apparatus according to the embodiment of the present invention. FIG. 12 is a flowchart showing the size prediction process according to the embodiment of the present invention.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Embodiments of an executable object size predicting apparatus, a size predicting method thereof, and a program thereof according to the present invention will be described below with reference to the accompanying drawings.

First, the configuration of the executable object size predicting apparatus according to the embodiment of the present invention will be described.
FIG. 3 is a block diagram showing the configuration of the executable object size prediction apparatus according to the embodiment of the present invention. This figure shows the configuration of the size predicting device 50, and further shows the relationship between each tool and each input / output file when a wide-area variable is specified in the short direct addressable memory area. An executable object size prediction program (executable object size prediction method) of the present invention is installed in an information processing apparatus exemplified by a personal computer, and functions as the executable object size prediction apparatus 50 of the present invention. The size prediction apparatus 50 includes a compiler 1, a linker 7, a wide area variable list display unit 5, a storage unit 10, an input device 11, and a display device 12.

  The compiler 1, the linker 7, and the wide area variable list display unit 5 can be realized by a combination of software, software, and hardware. For example, the compiler 1, the linker 7, and the wide area variable list display unit 5 can be realized by a program having these functions, a CPU (Central Processing Unit) used for executing these programs, and a main memory. The storage unit 10 is exemplified by a memory and a hard disk device, the input device 11 is exemplified by a mouse and a keyboard, and the display device 12 is exemplified by a flat panel display.

  The compiler 1 translates the input source codes 2-1 to 2-3 and generates relocatable objects 4-1 to 4-3. At this time, a code to be accessed by short direct addressing is generated for a wide-area variable designated to be placed in the short direct addressable memory area in the source code 2. The compiler 1 further has a function of specifying a global variable to be arranged in the short direct addressable memory area by an input file (global variable arrangement designation file 6). The compiler 1 further has a function of generating and outputting a plurality of global variable reference information files 3-1 to 3-3 based on a memory reference instruction size table 9 (described later) and source codes 2-1 to 2-3. . In the global variable reference information files 3-1 to 3-3, when it is assumed that the global variable is arranged in the short direct addressable area, the code size required to refer to the global variable, and the global variable are normal This file indicates the difference from the code size required to refer to the global variable when it is assumed that it is located in the memory area.

  The linker 7 combines the plurality of relocatable objects 4-1 to 4-3 generated by the compiler 1, resolves external references, determines absolute addresses, and generates an executable object 8. The input device 11 is a device by which a user performs an input operation on the size prediction device 50. The display device 12 displays the content of information processing in the size prediction device 50 and the content of input operation by the user. The storage unit 10 stores various files and data (for example, the global variable reference information file 3, the global variable placement designation file 6, and the memory reference instruction size table 9) that are input, generated, changed, and output in the present embodiment. is doing. The storage unit 10 may store the source code 2, the compiler 1, the relocatable object 4, the linker 7, and the executable object 8.

  The global variable list display unit 5 performs size prediction of the executable object based on the relocatable object 4 and the global variable reference information file 3 generated by the compiler 1. FIG. 4 is a block diagram showing details of the global variable list display unit 5 according to the embodiment of the present invention. This figure shows the configuration of the wide area variable list display section, and further shows the flow of processing for designating the placement of wide area variables in the short direct addressable memory area. The global variable list display unit 5 includes a global variable arrangement designation / list display unit 21, an object size information table 22, and a global variable reference information matrix 23.

  The global variable arrangement designation / list display unit 21 acquires information from the relocatable objects 4 (4-1 to 4-3) generated by the compiler 1 and generates an object size information table 22. Further, the global variable arrangement designation / list display unit 21 acquires information from the global variable reference information file 3 (3-1 to 3-3) generated by the compiler 1, and generates a global variable reference information matrix 23. Furthermore, the global variable arrangement designation / list display unit 21 generates / updates the global variable arrangement designation file 6 based on the object size information table 22, the global variable reference information matrix 23, and the input information by the user operation. Further, the global variable arrangement designation / list display unit 21 displays a list of global variables in the program using a GUI. Furthermore, the wide area variable designation / list display unit 21 performs size prediction of the executable object based on the relocatable object 4 and the wide area variable reference information file 3.

  FIG. 5 is a schematic diagram showing an example of a GUI screen of the wide area variable list display unit 5 according to the embodiment of the present invention. The GUI screen 30 is displayed on the display device 12 by the global variable arrangement designation / list display unit 21 of the global variable list display unit 5. The GUI screen 30 includes a table 31, an executable object size (predicted value) display field 32 (32-1 to 32-3), and a virtual link execution button 33. The table 31 includes a check box field, a global variable name field, an arrangement area field, a size field, a reference size difference field, and a file name field.

  In the check box column, check boxes are displayed corresponding to the global variables described in the global variable name column. When the user designates the global variable described in the column of the global variable name in the short direct addressable memory area, the user checks the check box with the input device 11. When checked, the arrangement area display becomes “Saddr”. That is, “Saddr” indicates a wide-area variable that is designated for placement in the short direct addressable area. When the user does not check the check box, the display of the arrangement area is “Normal”. That is, “Normal” indicates a global variable arranged in a normal memory area. Checking the check box and removing the check are both performed based on the input operation using the input device 11 of the user. The initial screen is all “Normal”.

  As a result of the user input operation, when the remaining size of the short direct addressable memory area becomes 0 (zero), the global variable placement designation / list display unit 21 cannot newly check the check box, and informs the GUI of that. It is displayed on the screen 30. When a size larger than the remaining size is designated, the area variable placement designation / list display unit 21 rejects the input and displays the fact on the GUI screen 30. However, the remaining size of the short direct addressable memory area is obtained as follows. First, the user designates the size of the short direct addressable memory area in advance from the input device 11 with the settable size as a maximum value. The remaining size of the short direct addressable memory area is calculated by subtracting the currently used Saddr size from the size input by the user. The Saddr size used is obtained as the sum of the sizes of the rows in which the segment attribute column is “SADDR” in the object size information table 22 (see FIG. 9 for details).

  In the global variable name column, the name of the global variable in the file described in the file name column (example: g_var11) is displayed. In the arrangement area column, the global variable is displayed as “Saddr” when the arrangement is designated in the short direct addressable memory area, and “Normal” is designated when the arrangement is designated in the normal memory area. In the size column, the size of the variable type of the global variable (example: 2 (bytes)) is displayed. In the reference size difference column, the difference between the memory size used when the global variable is allocated in the short direct addressable memory area and the memory size used when the allocation is specified in the normal memory area (example) : 90 (bytes)) is displayed. In the file name column, the name (example: file1.c) of a file (source code) including the global variable described in the global variable name column is displayed.

The global variable name column, arrangement region column, size column, reference size difference column, and file name column are based on the object size information table 22, the global variable reference information matrix 23, and the global variable allocation specification file 6. The wide area variable designation / list display unit 21 generates and displays it. For example, the check box and the arrangement area can be “Sadder” that is included in the global variable arrangement designation file 6 (described later). As the global variable name, the reference size difference, and the file name, the global variable name, the sum of the reference code size (change amount), and the file name of the global variable reference information matrix 23 (described later) can be used. The size can be obtained from the correspondence between the global variable and the variable type in the global variable reference information file 3 (see FIG. 7 for details). For example, in the case of the global variable name “g_var11”, since the variable type is an int type, it is 2 bytes. However, the size of the variable type varies depending on the type of the compiler 1, but in the present embodiment, the description is given assuming the following. The char type is 1 byte, the short type is 2 bytes, the long type is 4 bytes, and the pointer type (char * / short * / int * / long *) is 2 bytes.
However, for example, the global variable name “g_var11” of “file name” is not only “file1.c” but also “file2.c,” from the global variable reference information matrix 23 (see FIG. 10 for details). file 3.c, file 4.c, ... ". Similarly, the global variable name “g_var12” includes not only “file1.c” but also “file2.c, file4.c,...” From the global variable reference information matrix 23 (FIG. 10). Yes. The same applies hereinafter.

  The virtual link execution button 33 is a button for causing the global variable arrangement designation / list display unit 21 to execute the size prediction of the executable object. However, “virtual link” is an executable object size prediction process. When the virtual link execution button 33 is pressed by the user's input operation, the global variable arrangement designation / list display unit 21 executes size prediction of the executable object. The executable object size (predicted value) display field 32 (32-1 to 32-3) displays an execution result of the size prediction of the executable object by the global variable layout designation / list display unit 21. That is, the CODE attribute object is displayed in the display column 32-1, the SADDR attribute object is displayed in the display column 32-2, and the DATA attribute object result is displayed in the display column 32-3. If the size is exceeded, this is displayed in this column. Details of the size prediction of the executable object will be described later.

  As described above, the global variable arrangement designation / list display unit 21 responds to a user input operation together with the function to generate / update the object size information table 22, the global variable reference information matrix 23, and the global variable arrangement designation file 6. Then, a function for designating the arrangement of the global variable (whether it is a short direct addressable memory area or a normal memory area) from the list display on the GUI screen 30, and the size information of the global variable reference information file 3 and the relocatable object 4 Is provided with a function for predicting the size of the executable object 8.

  FIG. 6 is a schematic diagram showing an example of the format of the global variable placement designation file according to the embodiment of the present invention. The global variable arrangement designation file 6 is a file that is generated / updated by the global variable arrangement designation / list display section 21 of the global variable list display section 5 and used by the compiler 1 as an input file. The global variable allocation specification file 6 describes information on global variables to be allocated and specified in the short direct addressable memory area among the global variables defined in the program (source code (source file)). Here, the name of the global variable (global variable name), the variable type of the global variable (variable type), and the name of the source file containing the global variable (source file name) are described in association with each other. Yes. However, in the first process, the global variable arrangement designation file 6 does not exist, and is generated by the global variable arrangement designation / list display unit 21 after the first process.

  On the GUI screen 30 in FIG. 5, a wide area variable whose check box is checked is a wide area variable that is designated for placement in the short direct addressable memory area. The global variable allocation designation / list display unit 21 outputs the global variable information whose check box is checked to the global variable allocation specification file 6 at the timing when the virtual link execution button 33 is pressed, and specifies the global variable allocation specification. File 6 is generated / updated.

  FIG. 7 is a schematic diagram showing an example of the format of the global variable reference information file according to the embodiment of the present invention. The global variable reference information file 3 is a file generated by the compiler 1 in source file units. For each source file (source file name), assuming that each global variable (global variable name, variable type) is located in the short direct addressable memory area, the code size required to refer to it, Describe the difference (reference code size (variation)) from the code size required to refer to it when it is assumed that it is arranged in a normal memory area. When the compiler 1 outputs an instruction that refers to a global variable at the time of code generation, the compiler 1 acquires a change amount of the instruction size due to a difference in the allocation area of the global variable by a memory reference instruction size table 9 (described later) in FIG. Then, this information is generated by adding the obtained change amount of the instruction size to the reference code size (change amount) of the global variable in the global variable reference information file 3.

For example, focus on the global variable g_var11 in the global variable reference information file 3 in FIG. The reference code size (change amount) of g_var11 is 10. An example of such a result is shown below.
(Example 1) When the instruction type “movw var, ax” in the memory reference instruction size table 9 in FIG. 8 is output 10 times as an instruction for referring to the global variable g_var11 in the source file, “movw var, ax” Since the difference in code size is 1, 1 × 10 is 10.
(Example 2) As an instruction to refer to the global variable g_var11 in the source file, the instruction type “movw var, ax” in the memory reference instruction size table 9 of FIG. 8 is five times, and “sub a, var” is five times. , The difference in code size between “movw var, ax” and “sub a, var” is 1, so that 1 × 5 + 1 × 5 is 10.

  FIG. 7 shows that compiler 1 is file1. It is an example of the global variable reference information file 3 generated when compiling c. file2. c, file3. When c,... are compiled, a similar global variable reference information file 3 is generated. When the global variable reference information file 3 allocates each global variable to a short direct addressable memory area, the code size required to refer to it and when each global variable is allocated to a normal memory area The difference from the code size required to refer to it can be obtained.

  FIG. 8 is a schematic diagram showing an example of a memory reference instruction size table according to the embodiment of the present invention. The memory reference instruction size table 9 is a table used when the compiler 1 generates the global variable reference information file 3. Regarding each memory reference instruction (instruction type), when a global variable is placed in a normal memory area, the size of the instruction to be generated (code size A, unit: bytes) is placed in the short direct addressable area The size of the instruction to be generated in this case (code size B, unit: byte) and the difference between the sizes (code size difference, unit: byte) are described. The contents and format of the table depend on the instruction set architecture of the target microcomputer and the code generation method of the compiler. Here, an example in the case of an instruction set architecture provided with a register-memory operation instruction in a two-operand format is shown. The memory reference instruction size table 9 is prepared in advance.

  FIG. 9 is a schematic diagram showing an example of an object size information table according to the embodiment of the present invention. The object size information table 22 is a table managed by the global variable placement designation / list display unit 21 of the global variable list display unit 5. The global variable arrangement designation / list display unit 21 receives the relocatable object 4 as an input and initially generates the object size information table 22. After that, the size of each segment in the object size information table 22 is corrected according to the change in the designation of the arrangement of each global variable on the GUI screen 30 in FIG. This corrected value is used in the size predicting process of the executable object 8. The object size information table 22 includes a relocatable object 4 (file name column), a segment (segment attribute column) included in the relocatable object 4, and a size of the segment (size column, unit: byte). ).

  FIG. 10 is a schematic diagram showing an example of the global variable reference information matrix according to the embodiment of the present invention. The global variable reference information matrix 23 is a table managed by the global variable arrangement designation / list display unit 21 of the global variable list display unit 5. The elements in the m-th row and the n-th column in the matrix are m-th row relocatable objects (example: file1.o, file2) when the arrangement of the global variable in the n-th column (example: g_var11, g_var12, ...) is changed. ..., And the reference code size (change amount) (example: 10, 20,..., 10, 10,...). The global variable arrangement designation / list display unit 21 receives the global variable reference information file 3 generated by the compiler 1 for each source file, and generates / updates the global variable reference information matrix 23. The contents of the global variable reference information matrix 23 change only when the source code is changed and recompilation is performed, and is not changed by the change of the designation designation of each global variable on the GUI screen 30. .

  A wide area variable reference information matrix 23 in FIG. 10 is obtained by combining a plurality of wide area variable reference information files 3 as an m × n matrix. One row of the global variable reference information matrix 23 corresponds to one global variable reference information file 3. In this case, the file name is file1. c, file1. It can be read as o.

As shown in the description of FIG. 1 and FIG. 2, in the prior art, in order to select a wide area variable so as to improve the code efficiency of the program and place it in a short direct addressable memory area, It was necessary to repeat a series of flow of correction (adding a description instructing that the variable is arranged in a short direct addressable memory area), compiling processing, and linking processing.
However, in the present invention, on the GUI screen 30 of the global variable list display unit 5, the global variable to be arranged in the short direct addressable memory area is designated, and the executable object size prediction process (virtual link) is performed. It only needs to repeat the flow of execution.

  Next, the operation (size prediction method) of the executable object size prediction apparatus according to the embodiment of the present invention will be described with reference to the accompanying drawings. FIG. 11 is a flowchart showing the operation (size prediction method) of the executable object size prediction apparatus according to the embodiment of the present invention. This figure shows a flowchart of processing when a wide-area variable is designated to be allocated in a short direct addressable memory area. First, it is assumed that a link error other than a compile error or oversize has been solved for the source codes 2-1 to 2-3. In addition, it is assumed that the generation of the global variable reference information files 3-1 to 3-3 is made at the time of compilation.

  First, as the first process, the build process is executed on the source code 2 (2-1 to 2-3) based on the user's input operation as in steps S102 to S103 described in FIG. Thereafter, the compiler 1 receives the source code 2 (2-1 to 2-3) and the memory reference instruction size table 9 as inputs, and refers to the global variable allocation designation file 6 while referring to the source code 2 (2-1 to 2). A compilation process is executed on 2-3) to generate relocatable objects 4 (4-1 to 4-2). At the same time, the global variable reference information file 3 (3-1 to 3-3) is also generated. The relocatable object 4 (4-1 to 4-2) and the global variable reference information file 3 (3-1 to 3-3) are stored in the storage unit 10. However, in the first process, the global variable arrangement designation file 6 does not exist. Therefore, the compiler 1 operates on the assumption that all the global variables are specified for placement in normal memory.

  The global variable placement designation / list display unit 21 of the global variable list display unit 5 acquires information of the global variable reference information file 3 (3-1 to 3-3), and based on the information, the global variable reference information matrix 23 is acquired. Is generated (step S01). Subsequently, the global variable arrangement designation / list display unit 21 acquires information on the relocatable objects 4 (4-1 to 4-3), and generates an object size information table 22 based on the information (step S02). ).

  Next, the global variable placement designation / list display unit 21 acquires information on the global variables designated for placement in the short direct addressable memory area from the global variable placement designation file 6 (step S03). Then, the global variable arrangement designation / list display unit 21 aggregates and displays the information on the global variable reference information matrix 23, the object size information table 22, and the global variable arrangement designation file 6 on the display device 12. The display status on the display device 12 is exemplified in the GUI screen 30 of FIG. However, in the first process, since the global variable placement designation file 6 does not exist, all the wide variables are displayed as being designated in the normal memory.

  The user designates a global variable to be arranged in the short direct addressable memory area on the global variable list designation / list display unit 21 (GUI screen 30) of the global variable list display unit 5 by an input operation to the size prediction device 50. Yes (check the check box). That is, when the user selects a wide area variable so as to improve the code efficiency of the program and places it in a short direct addressable memory area through trial and error, the user selects the wide area variable designation / list display unit 21 (GUI screen 30). Specify a global variable to be placed in the memory area where short direct addressing is possible. The user presses the virtual link execution button 33 by an input operation to the size prediction device 50 (step S04).

  The global variable arrangement designation / list display unit 21 generates / updates the global variable arrangement designation file 6 (step S05). Then, the wide area variable designation / list display unit 21 executes an executable object size prediction process (step S06). The size prediction process (virtual link process) will be described later.

  The global variable arrangement designation / list display unit 21 determines whether the code size of the executable object 8 is satisfactory (step S07). The determination can be made, for example, by comparison with a preset code size (which may be set by the user). Then, until the size of the executable object becomes satisfactory (step S07: YES), the location of the global variable is designated on the global variable list display unit 5, and the virtual link is executed again (step S04 to step S04). S06). As described above, the second and subsequent wide area variable designation and size prediction processing (virtual link; step S04 to step S06) are completed only within the wide area variable list display unit 5. That is, in the present embodiment, it is only necessary to repeat the flow of the size predicting process for the executable object 8, so that the time can be reduced.

  Thereafter, the user executes a build of the source code 2 (2-1 to 2-3) by an input operation to the size prediction device 50 (step S08). Subsequently, the compiler 1 refers to the global variable arrangement designation file 6 and compiles the source code 2 (2-1 to 2-3) to generate the relocatable object 4 (4-1 to 4-3). (Step S09). When compiling here, it is not necessary to specify the generation of the global variable reference information file 3 (3-1 to 3-3). Next, the linker 7 generates an executable object 8 by linking the relocatable objects (step S10).

  As described above, in the present embodiment, an executable object with improved code efficiency can be created.

  Next, the size prediction process (virtual link process) according to the embodiment of the present invention will be described. The size prediction process (virtual link process) is a process executed in step S06 in FIG. FIG. 12 is a flowchart showing size prediction processing (virtual link processing) according to the embodiment of the present invention.

  First, the wide area variable designation / list display unit 21 selects one wide area variable from among a plurality of wide area variables on the GUI screen 30 (step S21). However, the selection method is exemplified by a method of selecting in order from the top, for example.

The wide area variable designation / list display unit 21 determines whether or not the current arrangement area of the wide area variable is different from the previous arrangement area (step S22). However, the current arrangement area is identified by the presence / absence of a check box on the GUI screen 30 after completion of the user input operation (short direct addressable memory area if checked). The previous allocation area is identified by whether or not it is included in the global variable allocation specification file 6 (if it is included, the memory area can be short direct addressable). Then, the determination method is performed in a state in which both of the recognized arrangement areas are changed. However, in the first process, since there is no wide area variable designation file, the operation is performed assuming that all wide variables are designated in the normal memory. Specifically, it is checked whether the check of the check box of the global variable on the GUI screen 30 in FIG. 5 has changed (the state checked from the unchecked state or the state checked from the checked state). .
If it is different (changed) (step S22: YES), the process proceeds to step S23. If not different (no change) (step S22: NO), the process proceeds to step S26.

  The wide-area variable placement designation / list display unit 21 determines the manner of change of the placement region (step S23). When the mode of change is from the short direct addressable memory area to the normal memory area (step S23: case-A), the process proceeds to step S24. On the other hand, when the mode of change is from a normal memory area to a short direct addressable memory area (step S23: case-B), the process proceeds to step S25. That is, when the check of the check box of the global variable on the GUI screen 30 in FIG. 5 changes from the checked state to the unchecked state (changes the global variable placement area from “Saddr” to “Normal”. In the case of: case-A), the process proceeds to step S24. On the other hand, when the check of the check box of the global variable on the GUI screen 30 in FIG. 5 changes from the unchecked state to the checked state (changes the allocation area of the global variable from “Normal” to “Saddr”. In the case of: case-B), the process proceeds to step S25.

In the case of the change from the short direct addressable memory area to the normal memory area (case-A), the wide area variable designation / list display unit 21 executes the following process (step S24).
First, from the global variable reference information matrix 23 (FIG. 10), the code size change amount of the relocatable object 4 that refers to the focused global variable is acquired. For example, assume that attention is paid to g_var11 in FIG. In this case, from the global variable reference information matrix 23 of FIG. As a code size change amount related to o, 10 is acquired. Subsequently, 10 is acquired as the code size change amount related to file 2.0. The same applies hereinafter. This code size change amount acquisition processing is performed for the number of files registered in the wide-area variable reference information matrix 23 of FIG.
Then, the obtained code size change amount is added to the CODE attribute segment size of the corresponding relocatable object 4 in the object size information table 22 (FIG. 9). For example, in the object size information table 22 of FIG. o, the file attribute of the obtained file1. The code size change amount 10 of o is added. The file name is file2. o, the file attribute of the obtained file2. The code size change amount 10 of o is added. The same applies hereinafter. The process of adding the segment attribute to the CODE size column is performed for the number of files registered in the object size information table 22 of FIG.

In the case of a change from the normal memory area to the short direct addressable memory area (case-B), the wide area variable designation / list display unit 21 executes the following process (step S25).
First, from the global variable reference information matrix 23 (FIG. 10), the code size change amount of the relocatable object 4 that refers to the focused global variable is acquired. For example, assume that attention is paid to g_var12 in FIG. In this case, from the global variable reference information matrix 23 of FIG. 20 is acquired as the code size change amount related to o. Subsequently, 10 is acquired as the code size change amount related to file 2.0. The same applies hereinafter. This code size change amount acquisition processing is performed for the number of files registered in the wide-area variable reference matrix 23 of FIG.
Then, the obtained code size change amount is subtracted from the CODE attribute segment size of the corresponding relocatable object 4 in the object size information table 22 (FIG. 9). For example, in the object size information table 22 of FIG. o, the file attribute obtained from the value 100 in the size column of the CODE segment attribute is file1. The code size change amount 20 of o is subtracted. The file name is file2. o, the file 2. obtained from the value 200 in the size field of the segment attribute C0DE. The code size change amount 10 of o is subtracted. The same applies hereinafter. The subtraction processing to the size column in which the segment attribute is CODE is performed for the number of files registered in the object size information table 22 of FIG.

  The global variable arrangement designation / list display unit 21 repeats the above processing (steps S22 to S25) for all of the multiple global variables on the GUI screen 30. That is, the wide area variable designation / list display unit 21 determines whether or not the above processing has been completed for all of the plurality of wide area variables on the GUI screen 30 (step S26). If the above process is completed for all of the wide variables (step S26: YES), the process proceeds to step S27. If the above process is not completed for all of the wide variables (step S26: NO), the process of step S21 is performed. Proceed to

Next, the wide-area variable arrangement designation / list display unit 21 updates the object size information table 22 by the following processing (step S27).
For each relocatable object 4, the size of the global variable designated for placement in the short direct addressable area is added in consideration of alignment. That is, for each global variable on the GUI screen 30 in FIG. 5, the size of the global variable having the same file name in the file name column is added while the check box is checked. For example, file1. In the case of c, the check box is checked and the file name in the file name column is file1. Add the size of the global variable of c.
Then, the SADDR attribute segment size of the corresponding relocatable object 4 in the object size information table 22 is updated. That is, the corresponding part of the object size information table 22 in FIG. 9 is updated based on the result of adding the sizes of the global variables. For example, file1. In the case of c, the file name is file1. o, Update by replacing the size column with the segment attribute SADDR with the result of adding the size of the global variable to the value of the size column.

Subsequently, the global variable arrangement designation / list display unit 21 updates the object size information table 22 by the following processing (step S28).
For each relocatable object 4, the size of the global variable designated for placement in the normal memory area is added in consideration of the alignment. That is, for each global variable on the GUI screen 30 in FIG. 5, the size of the global variable having the same file name in the file name column is added while the check box is not checked. For example, file2. In the case of c, the check box is not checked, and the file name in the file name column is file2. Add the size of the global variable of c.
Then, the DATA attribute segment size of the corresponding relocatable object 4 in the object size information table 22 is updated. That is, the corresponding part of the object size information table 22 in FIG. 9 is updated based on the result of adding the sizes of the global variables. For example, file2. In the case of c, the file name is file2. o, Update by replacing the size field of which the segment attribute is DATA with the result of adding the size of the global variable to the value of the size field.

  Thereafter, the global variable placement designation / list display unit 21 calculates the size of the executable object 8 by the same algorithm as that of the linker 7 based on the code size of the relocatable object 4 after the above size change (step S29). ). That is, the sizes of the rows having the same attribute in the object size information table 22 of FIG. 9 are added. Each result is displayed. On the GUI screen 30 of FIG. 5, the executable object size (predicted value) display column 32-1 displays the result of adding the CODE attribute line size in consideration of alignment. Similarly, the display columns 32-2 and 32-3 display the results of adding the sizes of the rows of the SADDR attribute and the DATA attribute in consideration of the alignment.

  As described above, the size prediction process (virtual link process) according to the embodiment of the present invention is performed.

  The code size prediction process of the executable object 8 by the size prediction process (virtual link) according to the present embodiment is faster than the compile process and the link process. For this reason, it is possible to shorten the time required for trial and error to select a wide area variable so as to improve the code efficiency of the program and arrange it in the memory area capable of short direct addressing.

In the prior art, the time required for one source code correction is t_m, the time required for one compilation process is t_c, and the time required for one link process is t_l. When selecting a global variable so as to improve the code efficiency of the program and performing trial and error N times so as to place it in a short direct addressable memory area, the total time t_total_1 required for this is:
t_total_1 = N × (t_m + t_c + t_l) (1)
In the present invention, the time required for designating a global variable to be arranged in the short direct addressable memory area on the GUI screen 30 of the global variable list display unit 5 is t_m ′, and the compilation specifying the generation of the global variable reference information file 3 is specified. The time required for processing is t_cfile, and the time required to calculate the amount of change in the size of the relocatable object 4 is t_e, and the size of the executable object 8 is calculated by the same algorithm as the linker 7 If the time required for the calculation is t_vl, the total time required for N trials and errors (t_total_2) is
t_toal_2
= T_cfile + N × (t_m ′ + t_e + t_vl) + (t_c + t_l) (2)
Here, assuming that t_m≈t_tm ′, t_l≈t_vl, and t_cfile = 2 × t_c, Equation (2) is
total_2
≈ N × (t_m + t_l) + N × t_e + 3 × t_c + t_l Equation (2) ′
It becomes.
Here, since t_e <t_c, when N >> 1, t_total_2 <t_total_1. That is, the total time of N trials and errors in the present invention is shorter than the total time of N trials and errors in the prior art.

  In the present invention, based on the reference information (global variable reference information file 3) of the global variable output by the compiler 1 and the size information of the relocatable object 4, the global variable list display unit 5 determines the location of a certain global variable. Predict changes in executable object size when changed. As a result, it is possible to reduce the time required for trial and error to select a wide area variable so as to improve the code efficiency of the program and to arrange it in the short direct addressable memory area. That is, the development period can be shortened.

  The program and data structure of the present invention may be recorded on a computer-readable storage medium and read into the information processing apparatus from the storage medium.

  The present invention is not limited to the embodiments described above, and it is obvious that the embodiments can be appropriately modified or changed within the scope of the technical idea of the present invention.

DESCRIPTION OF SYMBOLS 1 Compiler 2, 2-1 to 2-3 Source code 3, 3-1 to 3-3 Global variable reference information file 4, 4-1 to 4-3 Relocatable object 5 Global variable list display part 6 Global variable allocation Designated file 7 Linker 8 Executable object 9 Memory reference instruction size table 10 Storage unit 11 Input device 12 Display device 21 Wide area variable arrangement designation / list display section 22 Object size information table 23 Wide area variable reference information matrix 30 GUI screen 31 Table 32, 32-1 to 32-3 Executable Object Size (Predicted Value) Display Field 33 Virtual Link Execution Button 50 Size Predictor 101 Compiler 102, 102-1 to 102-3 Source Code 104, 104-1 to 104-3 Relocation Possible object 107 Linker 108 Line objects

Claims (13)

A compiler that translates a plurality of source codes to generate a plurality of relocatable objects, and generates a plurality of global variable reference information files based on the memory reference instruction size table and the plurality of source codes;
A global variable list display unit that performs size prediction of an executable object generated by linking the plurality of relocatable objects based on the plurality of relocatable objects and the plurality of global variable reference information files; Comprising
The memory reference instruction size table includes a code size of an instruction to be generated when a global variable is arranged in the first area as a short direct addressable area, and the global variable as a memory area other than the first area. Describe the code size difference with the code size of the instruction to be generated when arranged in the second area for each memory reference instruction,
The file global variable reference information file includes a code size required to refer to the global variable when each global variable included in the source code is arranged in the first area, and the global variable includes Indicating the code size difference from the code size required to refer to the global variable when it is assumed to be arranged in the second region,
The global variable list display section
Based on the global variable reference information file, calculate the relationship between the global variables, the area where the global variables are arranged, and the code size difference of the global variables,
Based on the input of the changed global variable to change the area to be arranged in each of the global variables, obtain the code size difference of the changed global variable from the calculation result, using the code size difference, Adjust the code size of the relocatable object containing the change global variable,
An executable object size predicting device that calculates a predicted value of an executable object size using the same algorithm as a link based on the code sizes of the plurality of relocatable objects after adjustment. The apparatus for predicting the size of an executable object according to claim 1,
The global variable list display section
Based on the relocatable object, generate an object size information table associating the relocatable object, a segment included in the relocatable object, and the size of the segment,
Based on the global variable reference information file, generate a global variable reference information matrix indicating the code size difference of the relocatable object when the area where each global variable is arranged is changed,
Based on the object size information table and the global variable reference information matrix, the relationship between the global variables, the area where the global variables are arranged, and the code size difference of the global variables is calculated. Executable object size prediction device. The apparatus for predicting the size of an executable object according to claim 1,
The global variable list display unit generates a global variable arrangement designation file that designates a global variable to be arranged in the first area based on the changed global variable. The apparatus for predicting the size of an executable object according to claim 1,
The global variable list display section
Displaying the calculation result on a display device;
An apparatus for predicting the size of an executable object that receives the changed global variable that a user inputs to the display via an input device. The size estimation apparatus of the executable object according to claim 4,
The global variable list display section
Displaying the code size of the plurality of relocatable objects after the adjustment on the display device;
When the remaining amount of the first area is insufficient, an indication that the remaining amount is insufficient is displayed on the display device. In the size estimation apparatus of the executable object of Claim 4 or 5,
The global variable list display section
Displaying the predicted value on the display device;
When the predicted value exceeds the ROM size, an indication that the size has been exceeded is displayed on the display device. Translating multiple source code to generate multiple relocatable objects;
Generating a plurality of global variable reference information files based on a memory reference instruction size table and the plurality of source codes;
Performing size prediction of an executable object generated by linking the plurality of relocatable objects based on the plurality of relocatable objects and the plurality of global variable reference information files, and
The memory reference instruction size table includes a code size of an instruction to be generated when a global variable is arranged in the first area as a short direct addressable area, and the global variable as a memory area other than the first area. Describe the code size difference with the code size of the instruction to be generated when arranged in the second area for each memory reference instruction,
The file global variable reference information file includes a code size required to refer to the global variable when each global variable included in the source code is arranged in the first area, and the global variable includes Indicating the code size difference from the code size required to refer to the global variable when it is assumed to be arranged in the second region,
Performing the size prediction comprises:
Based on the global variable reference information file, calculating a relationship between each global variable, an area where the global variable is arranged, and a code size difference between the global variables;
Based on the input of the changed global variable to change the area to be arranged in each of the global variables, obtain the code size difference of the changed global variable from the calculation result, using the code size difference, Adjusting the code size of the relocatable object including a modified global variable;
A method for predicting an executable object size based on the code sizes of the plurality of relocatable objects after adjustment using the same algorithm as the link. The method for predicting the size of an executable object according to claim 7,
The step of calculating the relationship includes:
Generating an object size information table associating the relocatable object, the segment included in the relocatable object, and the size of the segment based on the relocatable object;
Generating a global variable reference information matrix indicating the code size difference of the relocatable object when the area in which each global variable is arranged is changed based on the global variable reference information file;
Based on the object size information table and the global variable reference information matrix, the relationship between the global variables, the area where the global variables are arranged, and the code size difference of the global variables is calculated. A method for predicting the size of an executable object including steps and. The method for predicting the size of an executable object according to claim 7,
The step of calculating the predicted value includes a step of generating a wide area variable designation file for designating a global variable to be arranged in the first area based on the changed global variable. The method for predicting the size of an executable object according to claim 7,
The step of adjusting the code size includes:
Displaying the calculation result on a display device;
Receiving the modified global variable that the user inputs to the display via an input device. A method for predicting the size of an executable object. The method for predicting the size of an executable object according to claim 10.
The step of adjusting the code size includes:
Displaying the code size of the plurality of relocatable objects after the adjustment on the display device;
A method for predicting the size of an executable object, further comprising: displaying on the display device that the remaining capacity of the first area is insufficient. The method for predicting the size of an executable object according to claim 10 or 11,
The step of calculating the predicted value includes
Displaying the predicted value on the display device;
When the predicted value exceeds the ROM size, a display indicating that the size has been exceeded is displayed on the display device.   A program that causes a computer to execute the method for predicting the size of an executable object according to any one of claims 7 to 12.

Images