A system and method for generating program object modules

Abstract: The object module is generated from a conventional source program (10). The system has compiler means for generating an object module (17) from the source program (10) which module (17) has the necessary instructions for executing the desired program in the selected computing system but these instructions are arranged in a first format which is not loadable or readable into the selected computing system. The present system has further means (19) for then conver­ ting this first instruction format (18) into a second instruction format (20) which is loadable into the selected computing system. The present system is particularly advantageous when the instructions in the first format (18) are arranged in an order unrelated to the function of the in­ structions in the object module (17) while the instructions in the second or converted format (20) are arranged in a plurality of sections (31, 32, 33, 34, 35, 36, 37, 38), each of the sections containing instructions performing a related function in the program of the object module.

Description: This invention relates to systems for generating computer programs, and is particularly directed to systems for generating program object modules, i.e., program and object code for selected computing systems. Over the past several years, there has been a very rapid expansion in numbers and variety of computers in general usage. This expansion has been particularly rapid in the number and variety of personal computers of increasing scope and computing power. Along with this rapid expansion, has of course come an ever increasing demand for programs generated to run on this wide variety of computers. Conventionally, when a new computer is developed and enters the marketplace, in addition to a relatively few programs which are originally developed for a new computer, there is a demand for making many existing programs operable on the new computer. This is often accomplished by developing compiler means which decode instructions originating as source code and output program object modules having the complete sequence of instructions in object code necessary to run the desired program on the selected computer. The object module instruction must be executable on the selected computer and in addition, these instructions must be arranged in a format which is readable or loadable into the selected computer. When a new computer first hits the marketplace, there is often an immediate demand to make literally hundreds of existing programs available on this new computer. Thus, in developing compilers to make these existing programs available on the new computer, it is often most expedient to use an existing compiler for the particular program which has been developed for an already existing computer having functional characteristics close to the new computer and then making a minimum number of changes in the compiler necessary to change the existing compiler into one that will generate a program object module executable on the new computer. In order for the object module to be executable on this new computer, the instructions in the object module must be individually executable on the computer and the instructions must be arranged in a format which is readable by or loadable into the new computer. "The XASS-U Cross Assembler Handles Any Custom MPU or Word Length" Y Kunimine, JEE Journal of Electronic Engineering, Vol 23 No 237 September 1986 pp 95-98 concerns a general purpose or multi purpose assembler which is used to aid development of a variety of products with custom or semi-custom multiprocessors. In situations where there is an already existing computer which accepts and handles program object modules having instructions arranged in the same format as the instruction arrangement format required by the new computer, and there is an available compiler for the desired program for this existing computer, it is usually a relatively easy task to change the compiler so as to have it now generate the desired program object module for the new computer. However, there are a great many program compilers for a wide variety of programs for existing computers which compilers are only capable of producing object modules with instructions having formats which may be required in order to be readable or loadable in to the selected newly developed computers. This appears to be particularly the case when there is a demand for programs originally developed for the existing IBM System 370. The IBM System 370 required program object modules in which the instructions are arranged in a general format which may be considered as unorganised in relation to the functions to be performed by the instructions in the format. The general format of IBM S370 object modules or files is described in the manual "S370 OS/VS Linkage Editor Logic" (SY26-38-15-) Second Edition, March 1980, published by IBM Corporation. The reason that the program files for S370 had such relatively unorganised instruction format arrangement was that a great deal of this programming came out of the older punched card deck technology. Thus, the still existing term "object deck" is still used for such program object modules. On the other hand, the newer computers of recent years and particularly in the personal computer area generally require program object modules wherein the instructions are arranged in a format having a plurality of sections and each of the sections contains instructions performing a related function in the program of the object module. Typical of such an object module is the IBM RT PC AIX a.out object file or module described in Chapter 4 of "IBM RT PC Advanced Interactive Executive Operating System AIX Operating System Technical Reference Manual", First Edition, published November, 1985 by IBM Corporation. Because the instruction formats in the object modules required by the newer personal computers of the type described are completely different from the format of instructions in the object modules of existing S370 programming, the conventional approach would be to develop a new compiler for each of the source programs for S370 which are desired to be used on new personal computers entering the marketplace. This can be, of course, relatively time consuming and quite costly. The present invention involves the recognition that it is possible to avoid developing a completely new compiler for an existing program to be executed on a new machine even though the format of the instructions in the object module required in order to be loadable into the new computer is completely different from the format of the instruction in the object module producible by the existing compilers. The present invention is defined in claims 1 to 4. The compiling means which may be an existing compiler is modified slightly so as to produce an object module having instruction for said new computing system i.e. individually executable by said computing system, but arranged in a format which is not loadable or readable into the new computing system. Then in combination, means are provided for converting first instruction format which is not loadable into the new computing system into a second format which is loadable into the new computing system. Thus, since the instructions generated are readable into and executable on the new computer, once the format has been changed, the instructions will now be arranged in a format which is executable on the new computing system. The present invention is particularly advantageous when used to generate program object modules for newer computer systems which object modules have their instructions arranged in a format having a plurality of sections each of which contains instructions performing a related function in the program of the object module. With the present invention, such program modules of organised instructions can be generated through the use of compilers which produce object modules having generally unorganised instructions as in the previously described System 370 object modules. In accordance with the present invention, specific means may be provided for compiling an object module from a source program which object module has instructions which individually are executable in a selected computer but which instructions are arranged in a first format having an order unrelated to the function of the instructions in the program of the object module. In this case, because the selected computer is one which cannot handle instructions in such an unrelated format, the resulting object module is not loadable into the selected computer. Further means are now provided for converting this first and unrelated instruction format into a second format wherein the instructions are arranged in plurality of sections each of which contain instructions performing a related function in the program of the object module. Instructions arranged in such an organised format are loadable into the selected computer. Thus, the result is an object module for the selected new computer. With the system thus described, currently available compilers for a wide variety of programs which are capable of producing object modules wherein the instructions are in a format unrelated to function may still be useful. In this case, a relatively minor modification in the compiler may be made so as to generate appropriate individual instructions for the selected computer but having a format because of its arrangement unrelated to program function is not loadable into the selected computer. Then means are provided for converting just the format into one wherein instructions are organised in sections according to function and which is thus loadable into the selected computer. The result is that a wide variety of older programs and compilers generated for the System 370, for example, may be used in the combination of the present invention to produce object modules for some of the newer personal computers. Perhaps an even more significant aspect of the present invention is that once means for converting a first instruction format e.g. the previously described format unrelated to function, into a second format loadable into the selected computing system e.g. a format wherein the instructions are arranged in plurality of sections with each containing instructions performing a related function in the program, then the same conversion means may be used to convert a wide variety of object modules having said first format into object modules having second format. Referring now to the drawings, wherein a preferred embodiment of the invention is illustrated, and wherein like reference numerals are used throughout to designate like parts; Fig. 1 is a flow chart of the operations involved in proceeding from a source program through a compiler program to produce a program object module having a first format. Fig. 2 is a flow chart of the operations involved in the procedure of Fig. 1 detailing how the compiler program of Figure 1 tailors the instructions output in the object module so that these individual instructions are executable on selected or target machine. Fig. 3 is a flow chart showing in a very generalised form the conversion of a program object module having a first format into a program object module having the second format. Fig. 4 is a flow chart of the operations involved during the conversion step of Figure 3 in going through a first leg of conversion from program object module having the first format into a program object module having the TOC "Table of Contents" format. Fig. 5 is a representation of a typical a.out object module format showing the arrangement of instructions in sections each related to the function of the instructions in the program. Fig. 6 is a flow chart of the operations involved in the conversion of a TOC object module to the a.out object module required by the IBM RT PC in the illustrative preferred embodiment of the present invention. In the specific embodiment of the present invention, the source program utilised was PL.8 developed by IBM Corporation. This program is well known in the art and its components as well as the components of a typical compiler are described for example in the "IBM Journal of Research and Development", Vol. 27, No. 3, May, 1983, pages 237 through 246 and particularly starting page 241. The program PL.8 has been extensively used on the IBM System 370. In connection with the program, the PL.8 compiler for System 370 produces instructions arranged in a general format which may be considered as unorganised in relation to the functions to be performed by the instructions in the format. The general format of object modules or files thus produced is generally described hereinabove in connection with "S370 OS/VS Linkage Editor Logic" (SY26-38-15-) Second Edition, March 1980, published by IBM Corporation. With reference to Figure 1, let us assume commencing with a PL.8 source program, step 10, in the flow chart. In step 11, the source program is processed by a syntax analyser which reads the input representing the user's program and checks for correct program statement syntax. Next, step 12, the compiler generates internal pseudocode which is an intermediate representation of the source program. Next, step 13, the pseudocode is optimised so that faster running machine code will result. At this point, steps branch to entry "A" in Figure 2. To elaborate on what takes place in the next two steps, let us assume that the present compiler is formed by modifying an existing compiler which was developed to generated a program object module of the PL.8 program for the previously described System 370 computer as the target. In the present embodiment, this original compiler is modified to provide a program object of instructions that are executable on the target computer which is a IBM RT PC with an AIX operating system previously referenced as being described in Chapter 4 of "IBM RT PC Advanced Interactive Executive Operating System AIX Operating System Technical Reference Manual", First Edition, published November, 1985 by IBM Corporation. Accordingly, the table of executable instructions and pseudocode transformation algorithms will be the main modifications in the existing PL.8 compiler for the System 370. The modification will involve a new table of executable instructions and generally minor revisions to the pseudocode transformation algorithms to produce executable instructions for the IBM RT PC. In step 14, the correct instruction opcode table is selected for transforming the pseudocode into machine instructions which are executable on the target computer. Next, step 15, the pseudocode is transformed into corresponding executable instructions for described IBM RT PC through the use of the above selected instruction opcode table. As a result, the output is, step 16, a module of instructions to carry out the PL.8 program which instructions are executable on the described IBM RT PC. These executable instructions make up the resulting program object module, step 17, Figure 1. This module has a first format in which the instructions while individually executable on the described IBM RT PC are arranged in a first format which is essentially unorganised in relation to the functions performed by the instructions in the format. The instructions thus arranged cannot be handled by the described IBM RT PC which requires the instructions to be arranged in a format having a plurality of sections and each of the sections containing instructions performing a related function in the program for the instructions to be readable or loadable into the IBM RT PC. Thus, in its broadest sense according to the present invention, Fig 3, the program object module having the first format is input 18 to an object module format converter 19 which converts the format of the instruction to an arrangement having a plurality of sections with each of the sections containing instructions performing a related function in the program. This object module output, step 20, having this second or organised format is handleable i.e., loadable or readable into the above described IBM RT PC having the AIX operating system. Since, as previously mentioned, the individual instructions are already executable on the RT PC AIX system, we thus have generated the requisite program object module. We will now describe in greater detail step 19 of Figure 3 which involves the conversion of the object module format from the relatively unorganised format described above to the organised format required by the IBM RT PC AIX system. For purposes of understanding the present invention, it should be recognised that a direct conversion could be made from the first format required by System 370 to the second organised format required by the IBM RT PC AIX. However, in the present embodiment for purposes of expediency, the transformation or conversion went through two stages. The first stage involved transforming the above described unorganised System 370 object format to an organised format known as the "Table of Contents" (TOC) object module format. This TOC module format is an existing format described in the IBM publication "Virtual Resource Manager Technical Reference for the IBM RT PC", First Edition (November, 1985), Appendix B. Then as will be hereinafter described, the object module, the format of which has been converted to the TOC format is then taken through a second conversion step wherein the format is converted to the above referenced format required by the IBM RT PC AIX system. The reason for this two stage conversion was that a mechanism for conversion of the System 370 object module format into the TOC object module format wherein the instructions are arranged in a format with sections each containing instructions performing a related function in the program of the object module has already been developed. It was accordingly considered much simpler to then further convert from the organised TOC object module format into the desired IBM RT PC AIX object module format which is known as "a.out". With reference to Figure 4, there will be described a conversion of program object module having the first relatively unorganised format into a module having the above described TOC format wherein the instructions are arranged in a plurality of sections, each of the sections containing instructions performing a related function in the program of the object module. Steps 21 through 24 are repeated until all records have been read and processed. Step 21, the instructions in the object module are read, one record at a time. Then, step 22 ESD, if there is a symbol record, the symbols in the symbol dictionary are recorded in a table in a procedure which involves adding symbols to the symbol table and then allocating sufficient sections in storage to contain the text or code represented by the symbols. Next, step 23, text data is recorded. This involves placing the code or text for a symbol entry into the storage sections allocated above. Then, step 24, the RLD or record relocation data is added to a relocation table and the referenced code or text is adjusted by the appropriate relocation address. For an elaboration of how this relocation entry is made, reference is made to the above described "Virtual Resource Manager Technical Reference", Appendix B, commencing with page B6. Essentially, the relocation addresses are adjusted responsive to the quantity of text recorded in step 23. Once all the records have been read and processed, then a TOC object module organised in a sectioned format is output in step 25. This format which is described in detail in the above listed "Virtual Resource Manager Technical Reference", comprises a header section 26 containing information required to run the object module, followed by a read-only section 27 consisting of executable object code and constants, followed by a read-write section 28 consisting of the read-write data of the module, followed by a loader section 29 which contains the symbol (ESD) and relocation (RLD) information required by a relocating loader, followed by a binder section 30 which contains all the symbol (ESD) and all the relocation (RLD) information for the module which is all the information required by a binder to bind this TOC object module with another TOC object module. The format of the binder section is the same as the format of the loader section. The resulting TOC object module generated as described hereinabove will have the instructions which are individually executable on the IBM RT PC-AIX system arranged in a format in which the instructions are ordered in a plurality of sections with each section containing instructions performing a related function in the program. While the TOC program object module could be capable of being loadable or readable into a given computer system, in the present embodiment, the target computer, the IBM RT PC requires that the instructions be arranged in an a.out format. Previously referenced as being described in detail in Chapter 4 of "IBM RT PC Advanced Interactive Executive Operating System AIX Operating System Technical Reference Manual". Because the a.out format like the TOC format is one wherein the instructions are arranged in a series of sections according to instruction function in the program, conversion from the TOC format to the a.out format is a relatively simple one. The a.out module format is shown in Figure 5. The format of the a.out module in Figure 5 contains a header section 31, sections of read-only code 32 called text, sections of read-write data 33 called data, a text relocate section 34 and a data relocate section 35, a symbol table section 36, a line number table section 37 and a string table section 38. All of the above are described in detail in Chapter 4 of the previously referenced "IBM RT PC Advanced Interactive Executive Operating System AIX Operating System Technical Executive Reference Manual". Conversion from an a.out module format to a TOC module format is already known in the art. Please refer to the IBM Technical Disclosure Bulletin, Vol. 29, No.2, July, 1986, pages 880-881. Now with respect to Figure 6, there will be described the conversion of a TOC object module shown in Figure 4 to an a.out object module shown in Figure 5. First, step 40, the TOC object file module is read. Next, step 41, the origin addresses (absolute load addresses) are set for both the text section and the data section. Next, step 42, both the text (code) and the data are relocated by the amounts specified in the above origins. During this relocate step, the relocation (RLD), symbol table, optional line number table, and string table of the a.out module are built. Next, step 43, the a.out header is generated by filling in the length information for the subsequent a.out module sections which were built in the previous step. At this point, step 44, the elements of the a.out object file generated in the above steps are output to the a.out object module file in the format described in Figure 5 and the conversion is complete.

Claims: A system for generating a program object module executable on a first computing system from a program source, the system comprising: means for compiling the program source into an object module in a first format, the object module in the first format having instructions individually executable on the first computing system but arranged in an order such that the object module in the first format is not loadable in the first computing system; and means for converting the order of the instructions in the object module in the first format such that they are arranged in a plurality of sections, the instructions in each section performing a related function in the program object module, the program object module in the second format being loadable and executable in the first computing system. A system for generating a plurality of different program object modules executable on a first computing system from a corresponding plurality of different program sources, the system comprising: means for compiling the plurality of program sources into respective object modules in a first format, the object modules in the first format having instructions individually executable on the first computing system but arranged in an order such that the object modules in the first format are not loadable in the first computing system; and means for converting the order of the instructions in the object modules in the first format such that they are arranged in a plurality of sections, the instructions in each section performing a related function in the program object modules, the program object modules in the second format being loadable and executable in the first computing system. A method for generating a program object module executable on a first computing system from a program source , comprising: compiling the program source into an object module in a first format, the object module in the first format having instructions individually executable on the first computing system but arranged in an order such that the object module in the first format is not loadable in the first computing system; and converting the order of the instructions in the object module in the first format such that they are arranged in a plurality of sections, the instructions in each section performing a related function in the program object module, the program object module in the second format being loadable and executable in the first computing system. A method for generating a plurality of different program object modules executable on a first computing system from a corresponding plurality of different program sources comprising: compiling the plurality of program source into respective object modules in a first format, the object module in the first format having instructions individually executable on the first computing system but arranged in an order such that the object modules in the first format are not loadable in the first computing system; and converting the order of the instructions in the object modules in the first format such that they are arranged in a plurality of sections, the instructions in each section performing a related function in the program object module, the program object modules in the second format being loadable and executable in the first computing system.

Inventors: CHAITIN GREGORY JOHN, HOAGLAND CLIFFORD HOMER, STEPHENSON MARC JOEL, CHAITIN, GREGORY JOHN, HOAGLAND, CLIFFORD HOMER, STEPHENSON, MARC JOEL
Applicants: IBM, INTERNATIONAL BUSINESS MACHINES CORPORATION
Application year: 1988
Main classification: G06F9
IPC codes: G06F9