Migration assistance using compiler metadata

• US 9,223,570 B2
• Filed: 05/02/2013
• Issued: 12/29/2015
• Est. Priority Date: 03/14/2013
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Kannan, Shakthi
• Primary Examiner(s): Chen, Xi D
• Application Number:
  US13/886,054
• Publication Number:
  US 20140282439A1
• Time in Patent Office: 971 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 8/76 Adapting program code to run in a different environment; Porting

Abstract

Systems and methods are migration assistance using compiler metadata. An example system includes a data module that receives data associated with a compiler. The data includes a set of rules associated with the compiler. The example system also includes an extraction module that extracts from the data, compiler metadata including the set of rules associated with the compiler. The example system further includes a database that stores the compiler metadata. The example system also includes a patch module that receives a program including source code, retrieves from the database the compiler metadata, and generates, without compiling the received program, a set of migration patches based on the received program and the compiler metadata. The set of migration patches includes one or more changes to the received program to abide by the set of rules associated with the compiler.

Claims

1. A computer-implemented method of migration assistance using compiler metadata comprising:

receiving first data associated with a first compiler, the first data including a first set of rules associated with the first compiler;

receiving second data associated with a second compiler, the second data including a second set of rules associated with the second compiler;

extracting first compiler metadata from the first data, the first compiler metadata including the first set of rules associated with the first compiler;

extracting second compiler metadata from the second data, the second compiler metadata including the second set of rules associated with the second compiler;

comparing the first and second compiler metadata;

identifying one or more differences between the first and second compiler metadata based on the comparison;

storing the one or more differences into a database;

receiving a program including source code;

retrieving the one or more differences between the first and second compiler metadata from the database; and

generating, without compiling the received program, a set of migration patches based on the received program and the one or more differences between the first and second compiler metadata.

2. The method of claim 1, comprising:

generating a second program by applying one or more migration patches of the set of migration patches to the first program;

compiling the second program using the second compiler; and

executing the second program, a result of the compilation of the second program being indicated in the set of migration patches.

3. The method of claim 1, comprising:

generating, without compiling the received program, a second set of migration patches based on the received program and the first compiler metadata, wherein the second set of migration patches includes one or more changes to the received program to abide by the set of rules associated with the first compiler.

4. The method of claim 3, further comprising:

generating a second program by applying one or more migration patches of the second set of migration patches to the first program;

compiling the second program using the second compiler; and

executing the second program, a result of the compilation of the second program being indicated in the second set migration patches.

5. A non-transitory machine-readable medium comprising a plurality of machine-readable instructions that when executed by one or more processors are adapted to cause the one or more processors to perform a method comprising:

receiving, by one or more processors, first data associated with a first compiler, the first data including a first set of rules associated with the first compiler;

receiving second data associated with a second compiler, the second data including a second set of rules associated with the second compiler;

extracting first compiler metadata from the first data, the first compiler metadata including the first set of rules associated with the first compiler;

extracting second compiler metadata from the second data, the second compiler metadata including the second set of rules associated with the second compiler;

comparing the first and second compiler metadata;

identifying one or more differences between the first and second compiler metadata based on the comparison;

storing the one or more differences into a database;

receiving a program including source code;

retrieving the one or more differences between the first and second compiler metadata from the database; and

generating, without compiling the received program, a set of migration patches based on the received program and the one or more differences between the first and second compiler metadata.

6. A system for migration assistance using compiler metadata, the system comprising:

one or more processors;

a first data module, executable on the one or more processors, that receives first data associated with a first compiler, wherein the first data includes a first set of rules associated with the first compiler;

a second data module that receives second data associated with a second compiler, wherein the second data includes a second set of rules associated with the second compiler;

an extraction module that extracts first compiler metadata from the first data and extracts second compiler metadata from the second data, the first compiler metadata including the first set of rules associated with the first compiler, the second compiler metadata including the second set of rules associated with the second compiler;

a database that stores the first compiler metadata and the second compiler metadata in a memory;

a compare module that compares the first and second compiler metadata, identifies one or more differences between the first and second compiler metadata based on the comparison, and stores the one or more differences into the database; and

a patch module that receives a program, retrieves the one or more differences between the first and second compiler metadata from the database and generates, without compiling the received program, a set of migration patches based on the received program and the one or more differences between the first and second compiler metadata.

7. The system of claim 6, further comprising:

a generate module that generates a second program by applying one or more migration patches of the set of migration patches to the first program.

8. The system of claim 7, wherein the generate module compiles the second program using the second compiler to generate a machine representation of the second program, and executes the machine representation of the second program, wherein a result of the compilation of the second program is indicated in the set of migration patches.

9. The system of claim 6, wherein the patch module receives a request for the set of migration patches that includes one or more changes to the received program to abide by the second set of rules associated with the second compiler.

10. The system of claim 6, further comprising:

a host machine that hosts a set of virtual machines including a first virtual machine and a second virtual machine,

wherein the first virtual machine includes the first data module, the second virtual machine includes the second and is coupled to the database.

11. The system of claim 6, further comprising:

an association module that receives an input specifying the first compiler as a first target compiler and specifying the second compiler as a second target compiler, identifies the first compiler metadata as being associated with the first target compiler, and identifies the second compiler metadata as being associated with the second target compiler.

12. The system of claim 6, wherein the first compiler has previously compiled the received program, wherein the first compiler is different from the second compiler.

13. The system of claim 6, wherein the first and second compilers are of a common compiler type, and the second compiler is a newer version of the first compiler.

14. The system of claim 6, wherein the patch module sends the set of migration patches to a user.

15. The system of claim 6, wherein the compare module identifies one or more differences between the first and second sets of rules, and the patch module generates, without compiling the received program, the set of migration patches based on the received program and the one or more differences between the first and second sets of rules.

16. The system of claim 7, wherein the generate module compiles the second program using the second compiler, and executes the second program, wherein a result of the compilation of the second program is indicated in the second set migration patches.

17. The system of claim 6, further comprising:

a host machine that hosts a set of virtual machines including a first virtual machine and a second virtual machine,

wherein the first virtual machine includes the first data module, and is coupled to the database, and

the second virtual machine is coupled to the database and includes the second data module.

18. The system of claim 6, wherein one or more changes to the received program avoids one or more warnings based on compilation of the received program using the second compiler.

19. The system of claim 6, wherein one or more changes to the received program avoids one or more errors based on compilation of the received program using the second compiler.

20. The system of claim 6, wherein the second set of rules associated with the second compiler are at least one of a set of syntax rules and a set of semantic rules.