CA1290067C - System for generating program object modules - Google Patents
System for generating program object modulesInfo
- Publication number
- CA1290067C CA1290067C CA000556676A CA556676A CA1290067C CA 1290067 C CA1290067 C CA 1290067C CA 000556676 A CA000556676 A CA 000556676A CA 556676 A CA556676 A CA 556676A CA 1290067 C CA1290067 C CA 1290067C
- Authority
- CA
- Canada
- Prior art keywords
- format
- instructions
- program
- object module
- computing system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/52—Binary to binary
Abstract
A SYSTEM FOR GENERATING PROGRAM OBJECT MODULES
Abstract A system for generating program object modules or decks of object code for selected computing systems is provided. The object module is generated from a conventional source program. The system has compiler means for generating an object module from the source program which module 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 for then converting this first instruction format into a second instruction format which is loadable into the selected computing system. The present system is particularly advanta-geous when the instructions in the first format are arranged in an order unrelated to the function of the instructions in the object module while the instruc-tions in the second or converted format are arranged in a plurality of sections, each of the sections containing instructions performing a related function in the program of the object module.
Abstract A system for generating program object modules or decks of object code for selected computing systems is provided. The object module is generated from a conventional source program. The system has compiler means for generating an object module from the source program which module 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 for then converting this first instruction format into a second instruction format which is loadable into the selected computing system. The present system is particularly advanta-geous when the instructions in the first format are arranged in an order unrelated to the function of the instructions in the object module while the instruc-tions in the second or converted format are arranged in a plurality of sections, each of the sections containing instructions performing a related function in the program of the object module.
Description
. (s , ~9~7 Description A SYSTEM FOR GENERATING PROGRAM OB~ECT MODULES
Technical Field This invention relates to systems for generating computer programs, and is particularly directed to svstems for generating program object modules, i.e., program and object code for selected computing sys-tems.
Background Art Over the past several years, there has been averv rapid e~pansion in numbers and variety of comput-ers in general usage. This expansion has beenparticularly 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 relative-ly 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.
~`
A~9-87-007 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 e~isting compiler for the particular program which has been developed for an already existing computer having functional character-istics 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.
In situations where there is an already existing ; 20 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 compil-er 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 ccmputer. 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 format quite different from the formats which may be required in order to be readable or loadable into the selected newly developed computers. This appears to be particularly the case ~T9-87-007 lX9~7 when there i8 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 unorganized 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 ~dition, March lg80, published by IBM Corporation. The reason that the program files for S370 had such relakively unorganized 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 re~uire 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 p~ogramming, the conventional approach would be to develop a new compiler for each of the source programs for S370 which are desired to be used ,~,r~
.0, 1290(~
on new personal computers entering the marketplace.
This can be, of course, relatively time consuming and quite costly. ~~
Summary of the Invention 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 instruc-tions 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 involves a system for generating a program object module for a selected computing system from a program source which comprises means for compiling an object module from said program source, said object module having instructions which are individually executable in said computing system but arranged in a first format which is not loadable into the computing system. Further, means are provid-ed for converting said first instruction format into a second format which is loadable into said computing system.
In other words, 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 ~L~d~ ~6~
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 particularl~ advanta-geous 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 organized instructions can be generated through the use of compilers which produce object modules having generally unorganized instruc-tions as in the previously described System 370 objectmodules. 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 a plurality of sections each of which contain instructions per-forming a related function in the program of the object module. Instructions arranged in such an organized format are loadable into the selected computer. Thus, the result is an object module for the selected new computer.
AT9-~7-007 .~
~2~7 With the system thus described, currently avail-able 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 com~uter. Then means are provided for converting just the format into one wherein instructions are organized in sections accord-ing 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.
~ 20 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 a plurality of sections with each containing instruc-tions 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.
Brief Description of the Drawing Referring now to the drawings, wherein a pre-ferred embodiment of the invention is illustrated, and ~0~
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 instruc-tions are executable on selected or target machine.
Pig. 3 is a fiow chart showing in a very general-ized 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 illus-trative preferred embodiment of the present invention.
Best Mode for Carryin~ Out the Invention In the specific embodiment of the present inven-tion, the source program utilized 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
.~
0~7 Journal of Research and Development", Vol. 27, ~Jo. 3, May, 1983, pages 237 through 246 and particularly starting page 241. The program PL.8 has been exten-sivelv 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 mav be considered as unorganized 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 general'y described hereinabove in connec-tion 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 com-mencing with a PL.8 source program, step 10, in the flow chart. In step 11, the source program is pro-cessed by a syntax analyzer 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 optimized so that faster running machine code will result. At this point, steps branch to entry "A" in Figure 2.
To elaborate on ~Ihat takes place in the next two steps, let us assume that the present compiler is formed by modifying an exis~ing compiler which was developed to generate 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 module of instructions that are execu-table on the target computer which is an 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. Accord-ingly, the table of executable instructions andpseudocode 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 the de-scribed IsM RT PC through the use of the above select-ed 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 unorganized 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 instruc-tions to be arranged in a format having a plurality of sections and each of the sections containing instruc-tions 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 .~ , 12~
the present invention, Fig. 3, the program ob-,ect module having the firs~ 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 organized format is handleable ; i.~., 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 unorganized format described above to the organized format required by the IBM RT PC AIX system. For purposes of understand-ing the present invention, it should be recognized that a direct conversion could be made from the first format required by System 370 to the second organized format required by the IRM RT PC AIX. However, in the present embodiment for purposes of expediency, the transformation or conversion went throuqh two stages.
The first stage involved transforming the above described unorganized System 370 object format to an organized 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 ,.~
lZ~(~0~7 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 ~ormat 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 had already been developed. It was accordingly considered much simpler to then further convert from the organized 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 de-scribed a conversion of a program object module having the first relatively unorganized 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 perform-ing 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.
; 30 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 relocat~on 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 Technica~ Reference", Appendix B, commencing with page ~6. Essentially, the relocation addresses are adjusted responsive to the quantity of text recorded in step 23.
Once all the records have been read and pro-cessed, then a TOC object module organized 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 embodi-ment, the target computer, the IBM RT PC requires that ~Z9~ 7 the instructions be arranged in an a.out format.
Previouslv referenced as being described in detail in Chapter 4 of "IBM RT PC Aavanced 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 de-scribed in detail in Chapter 4 of the previously referenced "IBM RT PC Advanced Interactive Executive Operating System AIX Operating System Technical 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, Julyl 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.
," ~
~2~
Next, step 43, the a.out header is generated by filling in the length inf,~rmation 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 th a.out object module file in the format described in Figure 5 and the conversion is complete.
While the invention has b,een particularly shown and described with reference to a preferred embodiment it will be understood by those skilled in the art that various other changes in form and detail may be made without departing from the spirit and scope of the invention.
Technical Field This invention relates to systems for generating computer programs, and is particularly directed to svstems for generating program object modules, i.e., program and object code for selected computing sys-tems.
Background Art Over the past several years, there has been averv rapid e~pansion in numbers and variety of comput-ers in general usage. This expansion has beenparticularly 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 relative-ly 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.
~`
A~9-87-007 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 e~isting compiler for the particular program which has been developed for an already existing computer having functional character-istics 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.
In situations where there is an already existing ; 20 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 compil-er 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 ccmputer. 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 format quite different from the formats which may be required in order to be readable or loadable into the selected newly developed computers. This appears to be particularly the case ~T9-87-007 lX9~7 when there i8 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 unorganized 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 ~dition, March lg80, published by IBM Corporation. The reason that the program files for S370 had such relakively unorganized 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 re~uire 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 p~ogramming, the conventional approach would be to develop a new compiler for each of the source programs for S370 which are desired to be used ,~,r~
.0, 1290(~
on new personal computers entering the marketplace.
This can be, of course, relatively time consuming and quite costly. ~~
Summary of the Invention 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 instruc-tions 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 involves a system for generating a program object module for a selected computing system from a program source which comprises means for compiling an object module from said program source, said object module having instructions which are individually executable in said computing system but arranged in a first format which is not loadable into the computing system. Further, means are provid-ed for converting said first instruction format into a second format which is loadable into said computing system.
In other words, 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 ~L~d~ ~6~
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 particularl~ advanta-geous 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 organized instructions can be generated through the use of compilers which produce object modules having generally unorganized instruc-tions as in the previously described System 370 objectmodules. 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 a plurality of sections each of which contain instructions per-forming a related function in the program of the object module. Instructions arranged in such an organized format are loadable into the selected computer. Thus, the result is an object module for the selected new computer.
AT9-~7-007 .~
~2~7 With the system thus described, currently avail-able 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 com~uter. Then means are provided for converting just the format into one wherein instructions are organized in sections accord-ing 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.
~ 20 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 a plurality of sections with each containing instruc-tions 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.
Brief Description of the Drawing Referring now to the drawings, wherein a pre-ferred embodiment of the invention is illustrated, and ~0~
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 instruc-tions are executable on selected or target machine.
Pig. 3 is a fiow chart showing in a very general-ized 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 illus-trative preferred embodiment of the present invention.
Best Mode for Carryin~ Out the Invention In the specific embodiment of the present inven-tion, the source program utilized 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
.~
0~7 Journal of Research and Development", Vol. 27, ~Jo. 3, May, 1983, pages 237 through 246 and particularly starting page 241. The program PL.8 has been exten-sivelv 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 mav be considered as unorganized 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 general'y described hereinabove in connec-tion 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 com-mencing with a PL.8 source program, step 10, in the flow chart. In step 11, the source program is pro-cessed by a syntax analyzer 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 optimized so that faster running machine code will result. At this point, steps branch to entry "A" in Figure 2.
To elaborate on ~Ihat takes place in the next two steps, let us assume that the present compiler is formed by modifying an exis~ing compiler which was developed to generate 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 module of instructions that are execu-table on the target computer which is an 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. Accord-ingly, the table of executable instructions andpseudocode 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 the de-scribed IsM RT PC through the use of the above select-ed 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 unorganized 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 instruc-tions to be arranged in a format having a plurality of sections and each of the sections containing instruc-tions 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 .~ , 12~
the present invention, Fig. 3, the program ob-,ect module having the firs~ 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 organized format is handleable ; i.~., 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 unorganized format described above to the organized format required by the IBM RT PC AIX system. For purposes of understand-ing the present invention, it should be recognized that a direct conversion could be made from the first format required by System 370 to the second organized format required by the IRM RT PC AIX. However, in the present embodiment for purposes of expediency, the transformation or conversion went throuqh two stages.
The first stage involved transforming the above described unorganized System 370 object format to an organized 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 ,.~
lZ~(~0~7 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 ~ormat 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 had already been developed. It was accordingly considered much simpler to then further convert from the organized 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 de-scribed a conversion of a program object module having the first relatively unorganized 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 perform-ing 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.
; 30 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 relocat~on 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 Technica~ Reference", Appendix B, commencing with page ~6. Essentially, the relocation addresses are adjusted responsive to the quantity of text recorded in step 23.
Once all the records have been read and pro-cessed, then a TOC object module organized 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 embodi-ment, the target computer, the IBM RT PC requires that ~Z9~ 7 the instructions be arranged in an a.out format.
Previouslv referenced as being described in detail in Chapter 4 of "IBM RT PC Aavanced 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 de-scribed in detail in Chapter 4 of the previously referenced "IBM RT PC Advanced Interactive Executive Operating System AIX Operating System Technical 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, Julyl 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.
," ~
~2~
Next, step 43, the a.out header is generated by filling in the length inf,~rmation 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 th a.out object module file in the format described in Figure 5 and the conversion is complete.
While the invention has b,een particularly shown and described with reference to a preferred embodiment it will be understood by those skilled in the art that various other changes in form and detail may be made without departing from the spirit and scope of the invention.
Claims (12)
1. A system for generating a program object module for a selected computing system from a program source comprising:
means for compiling an object module from said program source, said object module having instructions for said computing system arranged in a first format not loadable into said comput-ing system, and means for converting said first instruction format into a second format loadable into said computing system.
means for compiling an object module from said program source, said object module having instructions for said computing system arranged in a first format not loadable into said comput-ing system, and means for converting said first instruction format into a second format loadable into said computing system.
2. The system of Claim 1 wherein the instructions in said second format are arranged in a plurality of sections, each of said sections containing instructions performing a related function in said program of said object module.
3. The system of Claim 2 wherein the instructions in said first format are arranged in an order unrelated to the function of said instructions in the program of said object module.
4. A system for generating a plurality of different program object modules for a selected computing system from a corresponding plurality of differ-ent program sources comprising:
means for compiling a plurality of different program object modules from said source modules, said object modules each having instructions for said computing system arranged in a first format not loadable into said computing system, and means for converting said first instruction format into a second format loadable into said computing system.
means for compiling a plurality of different program object modules from said source modules, said object modules each having instructions for said computing system arranged in a first format not loadable into said computing system, and means for converting said first instruction format into a second format loadable into said computing system.
5. The system of Claim 4 wherein the instructions in said second format are arranged in a plurality of sections, each of said sections containing instructions performing a related function in said program of each respective object module.
6. The system of Claim 5 wherein the instructions in said first format are arranged in an order unrelated to the function of said instructions in the respective program of each object module.
7. A method for generating a program object module for a selected computing system from a program source comprising compiling an object module from said program source, said object module having instructions for said computing system arranged in a first format not loadable into said computing system, and converting said first instruction format into a second format loadable into said computing system.
8. The method of Claim 7 wherein the instructions in said second format are arranged in a plurality of sections, each of said sections containing instructions performing a related function in said program of said object module.
9. The method of Claim 8 wherein the instructions in said first format are arranged in an order unrelated to the function of said instructions in the program of said object module.
10. A method for generating a plurality of different program object modules for a selected computing system from a corresponding plurality of differ-ent program sources comprising compiling a plurality of different program object modules from said source modules, said object modules each having instructions for said computing system arranged in a first format not loadable into said computing system, and converting said first instruction format into a second format loadable into said computing system.
11. The method of Claim 10 wherein the instructions in said second format are arranged in a plurality of sections, each of said sections containing instructions performing a related function in said program of each respective object module.
12. The method of Claim 11 wherein the instructions in said first format are arranged in an order unrelated to the function of said instructions in the respective program of each object module.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US014,412 | 1987-02-13 | ||
| US07/014,412 US4791558A (en) | 1987-02-13 | 1987-02-13 | System and method for generating an object module in a first format and then converting the first format into a format which is loadable into a selected computer |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA1290067C true CA1290067C (en) | 1991-10-01 |
Family
ID=21765329
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA000556676A Expired - Fee Related CA1290067C (en) | 1987-02-13 | 1988-01-15 | System for generating program object modules |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US4791558A (en) |
| JP (1) | JPH0778741B2 (en) |
| BR (1) | BR8800329A (en) |
| CA (1) | CA1290067C (en) |
Families Citing this family (87)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5142681A (en) * | 1986-07-07 | 1992-08-25 | International Business Machines Corporation | APL-to-Fortran translators |
| JP2516387Y2 (en) * | 1987-08-19 | 1996-11-06 | 三洋電機株式会社 | Information file device |
| US4961133A (en) * | 1987-11-06 | 1990-10-02 | Visystems, Inc. | Method for providing a virtual execution environment on a target computer using a virtual software machine |
| US5067072A (en) * | 1987-11-06 | 1991-11-19 | Visystems, Inc. | Virtual software machine which preprocesses application program to isolate execution dependencies and uses target computer processes to implement the execution dependencies |
| JPH01277934A (en) * | 1988-04-29 | 1989-11-08 | Nec Corp | Switching system for parameter list reference method |
| US5117496A (en) * | 1988-05-23 | 1992-05-26 | Hewlett-Packard Company | Method for recording and replaying mouse commands by recording the commands and the identities of elements affected by the commands |
| US5261103A (en) * | 1988-09-12 | 1993-11-09 | Hitachi, Ltd. | Method of and system for compiling source program |
| US5345587A (en) * | 1988-09-14 | 1994-09-06 | Digital Equipment Corporation | Extensible entity management system including a dispatching kernel and modules which independently interpret and execute commands |
| US5230049A (en) * | 1988-11-29 | 1993-07-20 | International Business Machines Corporation | Program source code translator |
| US5313614A (en) * | 1988-12-06 | 1994-05-17 | At&T Bell Laboratories | Method and apparatus for direct conversion of programs in object code form between different hardware architecture computer systems |
| CA2002201C (en) * | 1988-12-06 | 1999-04-27 | John Charles Goettelmann | Translation technique |
| US5119465A (en) * | 1989-06-19 | 1992-06-02 | Digital Equipment Corporation | System for selectively converting plurality of source data structures through corresponding source intermediate structures, and target intermediate structures into selected target structure |
| JPH03149614A (en) * | 1989-08-31 | 1991-06-26 | Univ California | Information processing system and memory processing |
| EP0423989A3 (en) * | 1989-10-16 | 1992-09-23 | Hewlett-Packard Company | Software compiler and linker with improved line number table |
| DE69031936T2 (en) * | 1989-11-17 | 1998-06-10 | Digital Equipment Corp | System and method for storing firmware in an address-independent format |
| US5109504A (en) * | 1989-12-29 | 1992-04-28 | Texas Instruments Incorporated | Graphics program adaptor |
| US5423023A (en) * | 1990-06-25 | 1995-06-06 | Prime Computer, Inc. | Method and apparatus for providing a user configurable system which integrates and manages a plurality of different task and software tools |
| US5297285A (en) * | 1991-07-23 | 1994-03-22 | Telefonaktiebolaget L M Ericsson | System for dynamically linking modular portions of computer software |
| US5530866A (en) * | 1991-07-30 | 1996-06-25 | Tera Computer Company | Register allocation methods having upward pass for determining and propagating variable usage information and downward pass for binding; both passes utilizing interference graphs via coloring |
| US5396417A (en) * | 1991-11-01 | 1995-03-07 | Capitol Cities/Abc, Inc. | Product distribution equipment and method |
| US5365606A (en) * | 1991-11-27 | 1994-11-15 | Visystems, Inc. | Virtual software machine running multiple program modules in a single address space of a target computer |
| CA2077273C (en) * | 1991-12-12 | 1996-12-03 | Mike H. Conner | Language neutral objects |
| US5361350A (en) * | 1991-12-12 | 1994-11-01 | International Business Machines Corporation | Object oriented method management system and software for managing class method names in a computer system |
| US5421016A (en) * | 1991-12-12 | 1995-05-30 | International Business Machines Corporation | System and method for dynamically invoking object methods from an application designed for static method invocation |
| JPH05257664A (en) * | 1991-12-12 | 1993-10-08 | Internatl Business Mach Corp <Ibm> | System and method for generating version-independent object-oriented application program |
| EP0546682A3 (en) * | 1991-12-12 | 1993-12-08 | Ibm | Parent class shadowing |
| EP0548869B1 (en) * | 1991-12-23 | 2000-06-14 | Microsoft Corporation | Method for integrating a discrete subprogram into a main program |
| WO1993023817A1 (en) * | 1992-05-08 | 1993-11-25 | Release Management Systems (Rms) | Data interchange system |
| US5469572A (en) * | 1992-12-01 | 1995-11-21 | Taylor; James M. | Post compile optimizer for linkable object code |
| US5740405A (en) * | 1992-12-17 | 1998-04-14 | Microsoft Corporation | Method and system for providing data compatibility between different versions of a software program |
| US5715460A (en) * | 1993-06-14 | 1998-02-03 | International Business Machine Corp. | Template based facility for formatting compiler output |
| US5842205A (en) * | 1993-12-02 | 1998-11-24 | Vie Systems, Inc. | Method and process of inter-machine communication and generalized method for program preparation therefor |
| US5774644A (en) * | 1993-12-17 | 1998-06-30 | International Business Machines Corporation | Method and apparatus for generating a pair of interoperating communications programs |
| JPH07271777A (en) * | 1994-03-31 | 1995-10-20 | Fujitsu Ltd | Character code management system of decentralized information processing system |
| WO1995029440A1 (en) * | 1994-04-21 | 1995-11-02 | British Telecommunications Public Limited Company | Interface device and method |
| US5627997A (en) * | 1994-06-07 | 1997-05-06 | Microsoft Corporation | Method and system for converting computer mail messages using an extensible set of conversion routines |
| US5619685A (en) * | 1994-11-04 | 1997-04-08 | Ball Corporation | Run-time dynamically adaptive computer process for facilitating communication between computer programs |
| US5640558A (en) * | 1995-05-31 | 1997-06-17 | International Business Machines Corporation | Identifying and analyzing multiple level class relationships in an object oriented system by parsing source code without compilation |
| JP3201716B2 (en) * | 1996-02-22 | 2001-08-27 | シャープ株式会社 | Computer equipment |
| EP0932865B1 (en) | 1996-10-25 | 2002-08-14 | SCHLUMBERGER Systèmes | Using a high level programming language with a microcontroller |
| US5875336A (en) * | 1997-03-31 | 1999-02-23 | International Business Machines Corporation | Method and system for translating a non-native bytecode to a set of codes native to a processor within a computer system |
| US6960133B1 (en) | 2000-08-28 | 2005-11-01 | Igt | Slot machine game having a plurality of ways for a user to obtain payouts based on selection of one or more symbols (power pays) |
| US5920721A (en) * | 1997-06-11 | 1999-07-06 | Digital Equipment Corporation | Compiler generating functionally-alike code sequences in an executable program intended for execution in different run-time environments |
| EP1010070B1 (en) | 1997-09-01 | 2002-10-23 | Fujitsu Siemens Computers GmbH | Method for converting an object code into a programme code |
| US6105033A (en) * | 1997-12-29 | 2000-08-15 | Bull Hn Information Systems Inc. | Method and apparatus for detecting and removing obsolete cache entries for enhancing cache system operation |
| US6128628A (en) * | 1998-02-27 | 2000-10-03 | Mci Communication Corporation | Meta data processing for converting performance data into a generic format |
| US6453356B1 (en) | 1998-04-15 | 2002-09-17 | Adc Telecommunications, Inc. | Data exchange system and method |
| US6208345B1 (en) | 1998-04-15 | 2001-03-27 | Adc Telecommunications, Inc. | Visual data integration system and method |
| US6578194B1 (en) * | 1999-09-08 | 2003-06-10 | International Business Machines Corporation | System and method using extended relocation types and operations in relocating operations |
| US6769985B1 (en) * | 2000-05-31 | 2004-08-03 | Igt | Gaming device and method for enhancing the issuance or transfer of an award |
| GB2362969B (en) * | 2000-05-31 | 2004-09-22 | Ibm | Message transformation selection tool and method |
| US7699699B2 (en) | 2000-06-23 | 2010-04-20 | Igt | Gaming device having multiple selectable display interfaces based on player's wagers |
| US6731313B1 (en) | 2000-06-23 | 2004-05-04 | Igt | Gaming device having touch activated alternating or changing symbol |
| US7695363B2 (en) | 2000-06-23 | 2010-04-13 | Igt | Gaming device having multiple display interfaces |
| US6935955B1 (en) | 2000-09-07 | 2005-08-30 | Igt | Gaming device with award and deduction proximity-based sound effect feature |
| US6739973B1 (en) | 2000-10-11 | 2004-05-25 | Igt | Gaming device having changed or generated player stimuli |
| US6749502B2 (en) | 2001-03-21 | 2004-06-15 | Igt | Gaming device having a multi-characteristic matching game |
| US7040983B2 (en) | 2001-03-21 | 2006-05-09 | Igt | Gaming device having a multi-round, multi-characteristic matching game |
| US7165054B2 (en) * | 2001-09-14 | 2007-01-16 | Knowledgextensions, Inc. | Custom electronic learning system and method |
| US7901291B2 (en) | 2001-09-28 | 2011-03-08 | Igt | Gaming device operable with platform independent code and method |
| US7666098B2 (en) | 2001-10-15 | 2010-02-23 | Igt | Gaming device having modified reel spin sounds to highlight and enhance positive player outcomes |
| US6848996B2 (en) | 2001-10-15 | 2005-02-01 | Igt | Gaming device with sound recording changes associated with player inputs |
| US7708642B2 (en) | 2001-10-15 | 2010-05-04 | Igt | Gaming device having pitch-shifted sound and music |
| US7092869B2 (en) * | 2001-11-14 | 2006-08-15 | Ronald Hilton | Memory address prediction under emulation |
| US20030093774A1 (en) * | 2001-11-14 | 2003-05-15 | Ronald Hilton | State-specific variants of translated code under emulation |
| US7228529B2 (en) | 2002-08-27 | 2007-06-05 | International Business Machines Corporation | Restructuring computer programs |
| WO2004084098A2 (en) * | 2003-03-17 | 2004-09-30 | Robert Dant | Database identification system |
| US7789748B2 (en) | 2003-09-04 | 2010-09-07 | Igt | Gaming device having player-selectable music |
| US7105736B2 (en) | 2003-09-09 | 2006-09-12 | Igt | Gaming device having a system for dynamically aligning background music with play session events |
| US20050065937A1 (en) * | 2003-09-22 | 2005-03-24 | International Business Machines Corporation | Virtual resources method, system, and service |
| US7585219B2 (en) * | 2004-09-30 | 2009-09-08 | Igt | Gaming device having a matching symbol game |
| US8043155B2 (en) | 2004-10-18 | 2011-10-25 | Igt | Gaming device having a plurality of wildcard symbol patterns |
| CN100442234C (en) * | 2005-06-21 | 2008-12-10 | 国际商业机器公司 | Software package constructing method and system for embedded system |
| US7792666B2 (en) * | 2006-05-03 | 2010-09-07 | Sony Computer Entertainment Inc. | Translation block invalidation prehints in emulation of a target system on a host system |
| US20070234316A1 (en) * | 2006-03-07 | 2007-10-04 | Sap Ag | Methods and systems for development of software for complex systems |
| US8060356B2 (en) | 2007-12-19 | 2011-11-15 | Sony Computer Entertainment Inc. | Processor emulation using fragment level translation |
| US7991915B2 (en) * | 2008-05-05 | 2011-08-02 | Sentilla Corporation | Software platform for radio network |
| US8591308B2 (en) | 2008-09-10 | 2013-11-26 | Igt | Gaming system and method providing indication of notable symbols including audible indication |
| CN102902568B (en) * | 2011-07-27 | 2016-08-17 | 国际商业机器公司 | The method and system that a kind of content table access for processing application program is overflowed |
| US8615745B2 (en) * | 2011-10-03 | 2013-12-24 | International Business Machines Corporation | Compiling code for an enhanced application binary interface (ABI) with decode time instruction optimization |
| EP2610739B1 (en) * | 2011-12-29 | 2017-09-27 | Software AG | Method and system for executing a 3GL program and / or an assembler program within a 4GL runtime environment |
| US8460090B1 (en) | 2012-01-20 | 2013-06-11 | Igt | Gaming system, gaming device, and method providing an estimated emotional state of a player based on the occurrence of one or more designated events |
| US8740689B2 (en) | 2012-07-06 | 2014-06-03 | Igt | Gaming system and method configured to operate a game associated with a reflector symbol |
| US9245407B2 (en) | 2012-07-06 | 2016-01-26 | Igt | Gaming system and method that determines awards based on quantities of symbols included in one or more strings of related symbols displayed along one or more paylines |
| US9192857B2 (en) | 2013-07-23 | 2015-11-24 | Igt | Beat synchronization in a game |
| US9947170B2 (en) | 2015-09-28 | 2018-04-17 | Igt | Time synchronization of gaming machines |
| JP6780576B2 (en) * | 2017-04-27 | 2020-11-04 | トヨタ自動車株式会社 | Analysis method presentation system, method and program |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB1405353A (en) * | 1973-02-13 | 1975-09-10 | Burroughs Corp | Process and apparatus for automatic generation of mini-computer instructions for dicrete classes of applications |
| US4536840A (en) * | 1982-09-30 | 1985-08-20 | Ronald Borta | Autogrammer |
-
1987
- 1987-02-13 US US07/014,412 patent/US4791558A/en not_active Expired - Lifetime
- 1987-12-15 JP JP62315461A patent/JPH0778741B2/en not_active Expired - Fee Related
-
1988
- 1988-01-15 CA CA000556676A patent/CA1290067C/en not_active Expired - Fee Related
- 1988-01-20 BR BR8800329A patent/BR8800329A/en not_active Application Discontinuation
Also Published As
| Publication number | Publication date |
|---|---|
| BR8800329A (en) | 1988-09-13 |
| JPH0778741B2 (en) | 1995-08-23 |
| US4791558A (en) | 1988-12-13 |
| JPS63201834A (en) | 1988-08-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA1290067C (en) | System for generating program object modules | |
| US7162709B2 (en) | System and method for common code generation | |
| Miecznikowski et al. | Decompiling Java using staged encapsulation | |
| JP3246438B2 (en) | Variable target compilation processing method, its processing device, storage medium for its program, and storage medium for conversion table | |
| US5889995A (en) | Using constant selectors for method identification | |
| JP2004272922A (en) | Direct instruction for executing emulation computer technique | |
| EP0348563B1 (en) | A system and method for generating program object modules | |
| US20020199169A1 (en) | Representation of Java data types in virtual machines | |
| JP2002182926A (en) | Compiling method and computer readable recording medium | |
| Freiburghouse | The multics PL/1 compiler | |
| JP2000122876A (en) | Information processor | |
| US20040045018A1 (en) | Using address space bridge in postoptimizer to route indirect calls at runtime | |
| Jones | Assembly language as object code | |
| Sampson | Translating CMS-2 to Ada | |
| JP3018783B2 (en) | Compilation method | |
| Dandamudi | Installing and using nasm | |
| TW434510B (en) | Method for conditionally loading segments of programs | |
| Montuelle | CUFOM: the CERN Universal Format for Object Modules | |
| JPH0561687A (en) | Processing system for compiler | |
| Coulter et al. | Machine independence: the problem of portability | |
| Weight et al. | A Microcode Compiler That Runs on the IBM AT and Supports Cascadable Microcomputers. Part 2 | |
| JPH05173800A (en) | Constant arranging method for program conversion | |
| Lakshminarayana et al. | Tool—A New Language for Real Time Control Applications | |
| Fulton et al. | ABACUS/X an incremental compiler for minicomputer use | |
| Dotzel et al. | The Programming Language Modula-2 and its Environment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| MKLA | Lapsed |