Patent Grant
11675575
The present invention generally relates to computer technology, specifically, to check validity of computer instructions at time of updating a computer program product, and more specifically checking validity of computer instructions that include, or are enclosed by macros.
Porting computer programs from one platform or source to another is important to enable the computer programs to be used on several platforms. For example, in the case of a cloud computing platform, several computer programs, such as open source programs are available to be used for particular functionality such as container support. Porting such computer programs from one platform (e.g., cloud computing platform, mobile computing platform, operating system, etc.) to another facilitates uninterrupted use of software that use such computer programs.
Existing technical solutions for analyzing computer programs and debugging computer instructions do not contemplate specific technical challenges that occur when updating large-scale enterprise level projects using with source code changes that may not be used by particular target computing platform(s). While several existing solutions exist for porting source code from one platform to the target computing platform, there is a need to improve the ported code, and particularly to filter the ported code specific to the target computing platform.
According to one or more embodiments of the present invention, a computer-implemented method includes receiving, by a processor, an updated version of a computer program, the updated version includes multiple source code changes. The method further includes preprocessing, by a compiler, the source code changes for a target computing platform, wherein preprocessing the source code changes by the compiler includes identifying a compile time condition associated with one or more computer instructions enclosed by a macro. Preprocessing the source code changes by the compiler further includes determining a current value of the compile time condition at the time of compiling the updated version of the computer program for the target computing platform. Preprocessing the source code changes by the compiler further includes determining object code corresponding to the one or more computer instructions based on the current value of the compile time condition. Preprocessing the source code changes by the compiler further includes storing a macro information record for the macro, the macro information record includes the compile time condition, the current value of the compile time condition, and an identification of the one or more computer instructions. The method further includes preprocessing, by a linker, the source code changes for the target computing platform. Preprocessing the source code changes by the linker includes determining that the object code corresponding to the one or more computer instructions is not included in an executable file, and updating the macro information record to indicate that the macro is not included in the executable file.
According to one or more embodiments of the present invention, a system includes a memory device, and one or more processing units coupled with the memory device. The one or more processing units are configured to perform a method for analyzing an updated version of a computer program for a target computing platform. The method includes receiving, by a processor, an updated version of a computer program, the updated version includes multiple source code changes. The method further includes preprocessing, by a compiler, the source code changes for a target computing platform, wherein preprocessing the source code changes by the compiler includes identifying a compile time condition associated with one or more computer instructions enclosed by a macro. Preprocessing the source code changes by the compiler further includes determining a current value of the compile time condition at the time of compiling the updated version of the computer program for the target computing platform. Preprocessing the source code changes by the compiler further includes determining object code corresponding to the one or more computer instructions based on the current value of the compile time condition. Preprocessing the source code changes by the compiler further includes storing a macro information record for the macro, the macro information record includes the compile time condition, the current value of the compile time condition, and an identification of the one or more computer instructions. The method further includes preprocessing, by a linker, the source code changes for the target computing platform. Preprocessing the source code changes by the linker includes determining that the object code corresponding to the one or more computer instructions is not included in an executable file, and updating the macro information record to indicate that the macro is not included in the executable file.
According to one or more embodiments of the present invention, a computer program product includes a computer-readable memory that has computer-executable instructions stored thereupon, the computer-executable instructions when executed by a processor cause the processor to perform a method for analyzing an updated version of a computer program. The method includes receiving, by a processor, an updated version of a computer program, the updated version includes multiple source code changes. The method further includes preprocessing, by a compiler, the source code changes for a target computing platform, wherein preprocessing the source code changes by the compiler includes identifying a compile time condition associated with one or more computer instructions enclosed by a macro. Preprocessing the source code changes by the compiler further includes determining a current value of the compile time condition at the time of compiling the updated version of the computer program for the target computing platform. Preprocessing the source code changes by the compiler further includes determining object code corresponding to the one or more computer instructions based on the current value of the compile time condition. Preprocessing the source code changes by the compiler further includes storing a macro information record for the macro, the macro information record includes the compile time condition, the current value of the compile time condition, and an identification of the one or more computer instructions. The method further includes preprocessing, by a linker, the source code changes for the target computing platform. Preprocessing the source code changes by the linker includes determining that the object code corresponding to the one or more computer instructions is not included in an executable file, and updating the macro information record to indicate that the macro is not included in the executable file.
According to one or more embodiments of the present invention, a method includes receiving, by a processor, a computer program comprising multiple source code files, each source code file comprising one or more computer instructions. The method further includes generating, by a compiler, a macro information by preprocessing the computer program for a specific target computing platform. Generating the macro information includes identifying a compile time condition associated with one or more computer instructions enclosed by a macro. Generating the macro information further includes determining a current value of the compile time condition at the time of compiling the updated version of the computer program for the target computing platform. Generating the macro information further includes determining object code corresponding to the one or more computer instructions based on the current value of the compile time condition. Generating the macro information further includes storing, in the macro information, a macro information record for the macro, the macro information record includes the compile time condition, the current value of the compile time condition, an identification of a location where the macro is defined, and an identification of a location where the macro is used. The method further includes processing, by a linker, the computer program in conjunction with the macro information. The processing by the linker includes determining that the object code corresponding to the one or more computer instructions is not included in an executable file, and updating the macro information record to indicate that the macro is not included in the executable file.
A computer program product includes a computer-readable memory that has computer-executable instructions stored thereupon, the computer-executable instructions when executed by a processor cause the processor to perform a method for analyzing a computer program. The method includes receiving, by a processor, a computer program comprising multiple source code files, each source code file comprising one or more computer instructions. The method further includes generating, by a compiler, a macro information by preprocessing the computer program for a specific target computing platform. Generating the macro information includes identifying a compile time condition associated with one or more computer instructions enclosed by a macro. Generating the macro information further includes determining a current value of the compile time condition at the time of compiling the updated version of the computer program for the target computing platform. Generating the macro information further includes determining object code corresponding to the one or more computer instructions based on the current value of the compile time condition. Generating the macro information further includes storing, in the macro information, a macro information record for the macro, the macro information record includes the compile time condition, the current value of the compile time condition, an identification of a location where the macro is defined, and an identification of a location where the macro is used. The method further includes processing, by a linker, the computer program in conjunction with the macro information. The processing by the linker includes determining that the object code corresponding to the one or more computer instructions is not included in an executable file, and updating the macro information record to indicate that the macro is not included in the executable file.
The above-described features can also be provided at least by a system, a computer program product, and a machine, among other types of implementations.
Embodiments of the present invention provide technical solutions to analyze/isolate the unneeded files/functions/code pieces in porting large-scale project in an efficient and improved manner compared to existing solutions. Embodiments of the present invention, accordingly, increase the efficiency of keeping large-scale projects current with upstream changes and branches that may include code changes made in an open source community. One or more embodiments of the present invention facilitate finding if the code update in upstream branches is needed to be included in a ported version. If it is not required for the target computing platform 130, the updates need not be analyzed and debugged. Further, one or more embodiments of the present invention facilitate editor/user interfaces of software development tools to provide highly readable and more friendly views of large-scale enterprise projects by marking sections of the computer program based on techniques described herein.
Additional technical features and benefits are realized through the techniques of the present invention. Embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed subject matter. For a better understanding, refer to the detailed description and to the drawings.
The specifics of the exclusive rights described herein are particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other features and advantages of the embodiments of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:
The diagrams depicted herein are illustrative. There can be many variations to the diagrams or the operations described therein without departing from the spirit of the invention. For instance, the actions can be performed in a differing order or actions can be added, deleted or modified. Also, the term “coupled” and variations thereof describe having a communications path between two elements and do not imply a direct connection between the elements with no intervening elements/connections between them. All of these variations are considered a part of the specification.
In the accompanying figures and following detailed description of the disclosed embodiments, the various elements illustrated in the figures are provided with two or three-digit reference numbers. With minor exceptions, the leftmost digit(s) of each reference number corresponds to the figure in which its element is first illustrated.
Technical solutions are described herein to validate, in a computer program, computer instructions that are enclosed by macros when the computer program is being updated (i.e., computer instructions are being added/modified). For a computing platform, it is a technical challenge to maintain a robust ecosystem that allows execution of computer programs that are available on other computing platforms, for example, competitor platforms, open source platforms, etc. For example, the computer programs can include libraries, tools, etc. that computer software/hardware developers (“developers”) desire to execute as part of, or to support their computer program. To facilitate execution of such computer programs, the computer program instructions (i.e., source code, code, executable instructions, etc.) of such computer programs have to be compiled for the particular computing platform.
Typically, computer programs include one or more macros. In computer programming, macros are a tool that allows a developer to re-use instructions. A macro is generally a rule or pattern that specifies how a certain input should be mapped to an output. The input and output may be a sequence of lexical tokens or characters, or a syntax tree. In programming languages, such as C/C++, a macro is often used to enclose computer program instructions, which are to be compiled only when certain condition(s) is met. Using a macro can make the source code of the computer program compact and avoid duplication efforts. However, the use of macro makes it technically challenging to parse the source code. Further, debugging the source code is also made technically challenging by use of macros.
Checking if computer instructions enclosed by a macro have been included (i.e., macro has been expanded) in an object file (result of compilation) is a technical challenge. This is because, for example, the definition of a macro can be included in a separate file from the file that actually includes (or uses) the macro. Alternatively, or in addition, the macro expansion can be overridden if the source code is compiled with specific runtime option (i.e., when the compiler is executed to compile the source code). Moreover, in enterprise level projects, the source code can be complicated, and can include several (hundreds) directories and (thousands) files in different hierarchy. Determining a macro defined in one of these files, which is then used in another can be a parsing challenge. Further, there can be different macros with the same macro name, but different instructions enclosed. This situation can be exacerbated because of the hierarchy. For example, multiple files can include respective macros with the same name, and a file, say file F1, can include two or more of such macro-defining files. Accordingly, it can be challenging to predict which of the macros was expanded at the time of compiling file F1.
In turn, the technical challenge of unpredictability of macro expansion makes it technically challenging to debug the computer programs that include macros. Accordingly, porting computer programs, such as open source computer programs, to a target computing platform is technically challenging. In addition, several tools such as aclocal, autoconfig, automake, libtool (all are libraries as part of GNU PROJECT®), MESON™ build system, NINJA™ build system, etc. can make the macros configuration and the root cause analyzing/locating (i.e., debugging) more complicated.
For example, consider computer programs developed using the C programming language. It should be understood that the technical challenges described herein may not be limited to particular programming languages. In the case of C, it can be difficult to make a software program portable because the C compiler differs from system to system. Alternatively, or in addition, certain library functions can be missing on some systems. Alternatively, or in addition, header files can have different names. To handle such challenges with portability, programmers generally use conditional code, with code blocks selected by means of preprocessor directives (#ifdef). For example, these preprocessor directives instruct the compiler to only compile certain portions of the computer program if the target system satisfies certain conditions, such as availability of library functions, etc. But because of the wide variety of systems, and build environments this approach can becomes unmanageable and hence, technical challenging.
Certain existing tools, such as AUTOTOOLS® are designed to address this problem more manageably. For example, AUTOTOOLS® includes settings/configuration such as autoheader, autoconf, automake etc., which are used to assume or generate intermediate files such as, configure.ac, Makefile.in, Makefile.am, aclocal.m4, etc. Such tools (e.g., AUTOTOOLS®, LIBTOOLS®, etc.) analyze the operating system, compiler options, etc., and collect and generate the macros definition or macros conditional code automatically. However, the existing tools make the code debugging more complicated because they add several macros and preprocessor directories (i.e., compile time conditions) for the various platforms/compilers to support. Additionally, such tools handle some cross-platform support without explicit knowledge of the user making it difficult for the user to debug the computer program in case of a failure.
Additionally, at present, existing solutions can facilitate pre-processing, for example compiling with a particular option (e.g., gcc with option “−E”) to generate one intermediate file which will expand all the macro, and also incorporate all the contents of included files. However, generating such an intermediary file can take a long time (hours) particularly in the case of large projects (thousands of lines of code). Further, such an intermediate file is not easily readable. For example, one source code file with 303 lines can expand to the intermediate file with 7148 lines.
Also, there are tools available such as VSCODE, that can analyze the source code and identify if one specific macro is defined or not within the file. Some existing tools can also change the visual representation of computer instructions enclosed by a macro, for example different color (e.g., grey) font, if the definition of the macro is not located in the same file as the file that is using the macro.
However, these methods are based on static analysis of the source code (i.e., they are unable to resolve the definition of macro in another file). Hence, the result is not accurate in many scenarios especially. For example, macros that are defined in included files or overridden in compiling options are commonly misidentified by such tools.
Further, several open-source software (i.e., computer programs) are now available to support or enhance functionality of enterprise-level projects and/or platforms. For example, there are several open-source tools that developers can avail to support cloud-platform development, especially for container support. Porting such open source tools from one platform to another critical for platform development organizations to build a robust ecosystem for their platform. Such porting of open-source tools that may be available on some platforms (“first platform”) to other platforms (“second platform”) (e.g., POWER®, AIX®, IBM Z®, etc.) can be a technical challenge. Without such porting, providing the functionality of the first platform on the second platform can be a technical challenge. For example, without such porting computer programs that are executable on the first platform may not be executable on the second platform. Alternatively, to make the computer programs that are executable on the first platform to be executable on the second platform, can require developers to overcome a steep learning curve.
The technical challenges faced during making computer programs from the first platform to be compatible (i.e., able to execute) with the second platform, and particularly with open-source computer programs include removing files/computer instructions that are not applicable with the second platform (i.e., target platform). For example, some files that are part of a computer program can be specific to certain platform or hardware, and not applicable to the target platform. Additionally, the computer program can include one or more functions that are not required in a ported version of the computer program for the target platform.
The technical challenges further include keeping the ported version of the computer program current with an upstream version of the computer program from the open-source community. For example, if there is a new version of the computer program, i.e., a code change in an upstream branch of the computer program, the updated computer instructions have to be checked and the ported version of the computer program for the target platform has to be changed accordingly.
Embodiments of the present invention address such technical challenges. Instead of consuming large-scale enterprise efforts on coding and testing ported versions of an open-source computer program for the target platform every time the computer program is updated, embodiments of the present invention determine if the updated code has to be ported (e.g., if such functionality already exists in the target platform), and if the porting is required, facilitate checking the validity of the source code for the target platform.
Accordingly, embodiments of the present invention are rooted in computing technology, and provide improvements to computing technology, particularly, computer software development. Embodiments of the present invention provide a practical application to check validity of updated computer instructions (i.e., source code) in a computer program that is to be ported to a target platform. Embodiments of the present invention, accordingly, reduce development effort and improve project delivery efficiency. Embodiments of the present invention address the technical challenges described herein by recording pre-processing information about code paragraphs (e.g., macros enclosed) according to compile time condition definition or compilation options. These records facilitate analyzing/debugging the computer instructions to check if the code paragraph has been compiled into object file. The linker also adds information to the records to check if the compiled code is linked into executable or library files. Because the records are generated based on compiling/linking options instead of analyzing static source code of the computer program, embodiments of the present invention provide dynamic result of checking the validity of the computer program, particularly the updates to the computer program.
Embodiments of the present invention provide technical solutions to address such technical challenges with improvements over the existing tools. Embodiments of the present invention are rooted in computing technology, particularly identifying computer program instructions in computer programs (i.e., source code). Further, embodiments of the present invention are rooted in computing technology because, they improve debugging of computer programs (i.e., source code) that include macros. Embodiments of the present invention provide a practical application to identify macros and debug computer programs that include macros. Without using the embodiments of the present invention, such an analysis, particularly for large enterprise projects, can be impractical, or cause significant delays in development, debugging, testing, and release.
Embodiments of the present invention facilitate processing computer programs during compiling and linking the computer program. The preprocessing information about computer instructions enclosed by a macro is recorded according to macro definition or compilation option. These records further facilitate to analyze/debug the computer programs to check if the computer instructions have been compiled into object file (result of compiling). Because embodiments of the present invention generate records based on compiling options instead of analyzing static source code, a dynamic compiling or linking result is provided.
The target computing platform 130 can be cloud computing platform architecture, an operating system, a processor architecture, or any other type of computing platform to which the computer program 106 is being ported. In other words, the computer program 106 may not have been developed (written) specifically for the target computing platform 130. The compilation and linking by the development tool 112 facilitates executing the computer program 106 on the target computing platform 130. Alternatively, or in addition, the development tool 112 improves the efficiency of execution of the computer program 106 when executing on the target computing platform 130.
The computer program 106 can include multiple source code files, including, for example but not limited to, a source code file 102 (“file” 102), and a source code file 103 (file 103). The computer program 106 can be open source in some embodiments of the present invention. It is understood that the computer program 106 can include several (hundreds, thousands) of source code files, although only two of them are depicted here. Each of the source code files (102, 103) can include several computer instructions (lines of code), for example, hundreds, thousands, etc. In one or more embodiments of the present invention, the source code files of the computer program 106 are organized in a hierarchical manner, for example using a directory structure (not shown).
One or more of the source code files in the computer program 106 uses macros 104. For example, the source code file 102 includes several macros 104. The depicted macros 104 can each be an instance of different macros. Alternatively, or in addition, the macros 104 can be associated with a conditional expansion. The conditional expansion can be dependent on one or more configurations of the compiler 110, that a user (e.g., developer) can adjust prior to executing the compiler 110. Alternatively, or in addition, the conditional expansion can be dependent on one or more environmental settings of the computing platform 130 (e.g., operating system level variables, hardware type, etc.). Alternatively, or in addition, the conditional expansion can be dependent on runtime option that the user provides at time of execution of the development tool 112 (i.e., compiler and linker). Other dependencies of the conditional expansion can be used in other embodiments of the present invention. In one or more embodiments of the present invention, the macros 104 that are used in the file 102 can be defined in the file 102 itself, or any other file in the computer program 106, for example the file 103.
The development tool 112 includes a user interface that is used to interact with the source code files 102, 103. A user can navigate the directory structure, and perform operations such as add, delete, copy, paste, move, edit, etc. with the source code files of the computer program 106. The user interface displays the computer instructions of the computer program using one or more contextual visual attributes. For example, computer instructions contents of different types (e.g., conditional statements, function calls, variables, keywords, macros, etc.) can be displayed using different color, different fonts, or other such visual attributes. The visual representation of the computer instructions can be adjusted by the development tool 112 based on results of the various features of one or more embodiments of the present invention.
Comparison results 220 of the two versions 242, 244 indicate a number of files that are the same, a number of files that are different, a number of files that are similar, a number of orphan files in each version. Here, “same files” includes a file where no change is detected in that file in the two versions 242, 244. “Similar files” includes a file where the change in that file, from the first version 242, to the second version 244, is less than a predetermined amount. For example, if the number of lines that have changed is less than a predetermined number of lines (e.g., 10 lines), or less than a predetermined proportion (e.g., 2% change). It is understood that while “changed lines” are used as a metric in the above example, other metrics, such as “changed characters,” “changed functions,” etc., can be used in other examples. When the change exceeds such a predetermined threshold, the file is deemed to be in the “different files” category. An “orphan file” is a file that exists in one version, but not in the other version. There can be an orphan file in the first version 242 (if that file does not exist in the second version 244); and similarly, the second version 244 can have an orphan file (second file) if that (second) file does not can exist in the first version 242.
One or more of the macros 104 are conditional. A dynamic compile time condition 202 is associated with such conditional macros, such that the computer instructions in the conditional macros 104 are compiled (i.e., converted to object 120 code) only if the associated compile time condition 202 is satisfied. If the compile time condition 202 is not satisfied the computer instructions in the conditional macro 104 are not included in the object 120. The compile time conditions 202 can indicate a combination type of hardware and software of the target computing platform 130. For example, a compile time condition 202 can indicate that the macro 104 is to be expanded only if the platform uses a particular operating system such as, LINUX®, AIX®, INTERIX®, Z/OS®, etc. Alternatively, or in addition, the compile time condition 202 can indicate that the macro 104 is to be expanded only if one or more other source code files (e.g., a header file) is included. In some examples, the expanded macro 104 can itself be an inclusion of additional source code files, such as a library, an application programming interface, etc. Alternatively, or in addition, the expanded macro 104 can cause a particular type of hardware component or software component to be “mounted.” Here, “mounting” includes acquiring access to the component, e.g., recognizing, reading, and processing a file system structure, a storage medium, etc., before registering the component for use. Several additional or alternative operations can be performed by the computer instructions enclosed in the macros 104 in one or more embodiments of the present invention.
Embodiments of the present invention provide technical solutions that facilitate detecting computer instructions that are enclosed in a macro 104, and further identifying the root cause of a conflict between an enclosed macro and the unenclosed macro. Alternatively, or in addition, embodiments of the present invention can identify macro redefinition paths across several source code files 102, 103, in the computer program 106 at the time of compiling. Alternatively, or in addition, one or more embodiments of the present invention facilitate representing (e.g., by highlighting, marking, etc.), in the development tool 112, the portions of the computer program 106 (e.g., lines of code) that were compiled into the object file 120, the conflicted macros 104, and macro redefinition paths. In one or more embodiments of the present invention, one or more portions of the computer program 106, such as macros 104, are annotated using predetermined annotations such as, MacroEnclosed, CurrentMacroValue, Preprocesstype, EarlierAssignedMacroValue, etc. In one or more embodiments of the present invention, values are assigned to the predetermined set of variables, such as MacroEnclosed, CurrentMacroValue, Preprocesstype, EarlierAssignedMacroValue, etc. The assigned values are used to facilitate represent the computer program 106 in a more readable manner. Further, the values are used to facilitate the user to perform root cause analysis in case of an error.
Further, in one or more embodiments of the present invention, a preprocessor collects and identifies and generates records of the computer instructions that are enclosed (and not enclosed) in macros 104. Further, the compiler 110 supports macro definition conflict by comparing compile time conditions 202 MacroEnclosed and CurrentMacroValue, to identify the impact on the corresponding macros 104. The compiler (and/or linker) 110 supports a macro redefinition path across source code files 102, 103 by locating the macro enclosed records with MacroEnclosed ‘ON’ and runtime options, such as Preprocesstype ‘D’, to compare AssignedMacroValue and EarlierAssignedMacroValue across the different files. Accordingly, one or more embodiments of the present invention facilitates to analyze and identify the root cause of a macro conflict which can cause computer instructions to be compiled (or not) into the object 120 file, and also provide macro redefinition warning across several source code files.
Embodiments of the present invention can achieve such technical solutions by generating the intermediate file 312 at compile time of the computer program 106. However, this information is not sufficient to guide the developers and to identify the portions of the computer program 106 pieces in the updated version (242) should be debugged (or analyzed) and which portions can be ignored. In large enterprise size computer programs (millions of lines of code), such information can improve (reduce) the development time and efforts by magnitudes.
For example, in the depicted scenario of
The development tool 112 also includes a macro preprocessor 410 that generates macro information 412 by analyzing the source code files of the computer program 106. The macro information 412 can include the compile time conditions 202, current values of the compile time conditions, assigned compile time condition values, macro names, preprocessor type, referred macro names, etc. The preprocessor type ‘S’ marks the source code scope enclosed by the macro; whereas ‘D’ marks the definition of macros. Other preprocessor types can be specified in other embodiments of the present invention. ReferredMacroName specifies a macro name to be used in macro condition during the preprocessing. It is understood that the formatting of the command 320 can be varied in other embodiments of the present invention.
The development tool 112 also includes an editor 404, for example, a graphical user interface (GUI). The editor 404 facilitates viewing and/or editing filenames, computer instructions in the files, line numbers of the computer instructions, macro names, compile time conditions 202, attributes of the compile time conditions 202 (e.g., type of value (e.g., integer, character, time, binary, etc.), condition to check, threshold to check, etc.), visual attributes (e.g., color, highlights, font size, font type, etc.), etc.
In addition, the development tool 112 includes the compiler 110 and the linker 115, which convert the computer program 106 into object code 120 and machine executable instructions for the target computing platform 130. In one or more embodiments of the present invention, the development tool 112 is a separate computing system from the computing platform 130. Alternatively, the development tool 112 is part of the computing platform 130, for example, a software executing on the computing platform 130. In other cases, the computing platform 130 can be considered as the development tool 112.
At block 504, in response to the received command, the macro preprocessor 410 parses the computer program 106 to generate the macro information 412. The macro information 412 can identify FileName, MacroEnclosed, LineNoStart/LineNoEnd, PreprocessType, MacroName, AssignedMacroValue, EarlierAssignedMacroValue, SpecificMacroType, ReferredMacroName, CurrentMacroValue, etc. Filename indicates the name of the file 102, 103 that uses the macro 104. MacroEnclosed indicates whether the macro 104 has a compile time condition 202 associated with it. LineNoStart indicates a starting line number in the file 102, 103 where the computer instructions of the macro 104 start. LineNoEnd indicates an ending line number of the macro 104. PreprocessType indicates an action relative to the compile time condition 202. MacroName indicates a name associated with the macro 104, typically provided by the developer. AssignedMacroValue indicates a value assigned to the compile time condition 202. SpecificMacroType indicates a type of the compile time condition 202 and/or the macro 104. ReferredMacroName indicates another macro 104 that may be referred by the macro 104 that is being parsed. CurrentMacroValue indicates a present value of the compile time condition 202, which can be different from the value that was assigned previously.
Such information can be identified by syntactic and semantic parsing of the computer instructions in the source code files 102, 103 of the computer program 106. In some examples, the command can specify particular subset of source code files 102, 103 to be parsed to generate the macro information 412.
The macro information 412 that is generated is stored in memory in some embodiments of the present invention. Alternatively, or in addition, the macro information 412 is stored in a file. For example, a file “<program name>.p” is created that stores the macro information 412. In some embodiments of the present invention a filename to store the macro information 412 can be specified in the command to trigger the preprocessing.
It should be noted that the above provided examples of the various parameters in the macro information 412 are not exhaustive, and that in one or more embodiments of the present invention the parameters can have other values assigned.
Referring to the flowchart of the method 500, at block 506 the compiler 110 compiles the computer instructions, which includes generating source code for the macro(s) 104, depending on the compile time conditions that enclose the macro.
Referring to the flowchart of method 800, the compiler 110 checks whether detecting macros has been enabled (block 502), at 802. At block 804, if the macro detection has been triggered, the compiler 110 scans the computer program 106 using the macro preprocessor 410 (at block 806), else, the compiler proceeds with typical macro processing according to existing solutions (at block 808).
At each computer instruction, the compiler 110 checks whether the present computer instruction is a definition of a compile time condition 202, at block 810. If the present computer instruction is a definition of a compile time condition 202 (e.g., “#undef MYDEF”), the compiler 110 assigns flag ‘D’ to the Preprocesstype, at block 812. Instead, if the computer instruction is a condition of a compile time condition 202 (e.g., “a.c” line 14-17), the compiler 110 assigns flag ‘S’ to Preprocesstype, at block 814. Further, in this case (flag S), the macro name, present value, and type are noted from the computer instruction, at block 816. Further, at block 810, there are computer instructions that are enclosed in the compile time condition 202, the MacroEnclosed is set to ‘ON’, (e.g., “a.c” line 14-19), otherwise, it is set to ‘OFF’ (e.g., “a.c” line 9-12). Macro information parameters including SpecificMacroType, ReferredMacroName, and and CurrentMacroValue are also recorded at this time in one or more embodiments of the present invention.
In the case of encountering a definition of a compile time condition 202 (flag D), the compiler 110 checks if the compile time condition 202 (e.g., ‘MYDEF’) was defined before, at block 818. The check is performed by searching the macro name through the existing information in the macro information 412. If the compile time condition 202 was defined before, the compiler 110 searches and obtains the last value assigned to the compile time condition 202 (e.g., ‘1’ in the ongoing example of MYDEF; 1 is passed by compiling command option ‘−DMYDEF’), at block 820. The obtained value is recorded into EarlierAssignedMacroValue.
The compiler 110 also collects the metadata associated with the macro 104 such as, file name, line numbers (start, end), etc., at block 822. The captured information is stored in the macro information 412 structure (e.g., separate file, database, memory, etc.), at block 824.
The compiler 110 repeats this process for each computer instruction in the computer program 106, and at least for macros 104 in the computer program. Once all of the macros 104 have been processed in this manner and the macro information 412 is captured, the compiler 110 continues to expand the macros 104 and compile the computer instructions in the computer program 106 as it typically does, at block 830.
Continuing with the flowchart of the method 500, at block 508, macro conflicts are checked in the source code that is expanded by the compiler 110.
The conflict checking facilitates identifying the root cause of the conflict between a macro 104 that is to be enclosed, but is not because of conflicting compile time conditions 202, as in this case. At blocks 902, 904, the compiler 110 selects the macro to be checked and checks it specific macro type, (i.e., the macro type is ‘T’ (target), or set by the user). In this example, ‘MYDEF’ is the selected macro to check. If the type of macro 104 is not a predetermined type, (such as ‘T’), the conflict check does not have to be performed, at block 906.
If the macro 104 is of the predetermined type(s), the compiler 110 searches macro information 412 for the ReferredMacroName (e.g., ‘MYDEF’), at block 908. In the example of file “a.c” 302, two records are identified (lines 8-12, and lines 12-16, which both use MYDEF in compile time condition 202).
At blocks 910 and 912, the next macro information 412 is read and the current value of the compile time condition 202 associated with the macro 104 is checked with the current value. If the compile time condition 202 is satisfied, the next record(s) are checked for conflicts in the same manner (repeat block 910). Alternatively, if the compile time condition 202 has an ambiguous evaluation (e.g., values switched between 1 and 0), the compiler 110 denotes the record in the macro information 412 as a potential conflict, at block 914.
Further, at block 916, the development tool 112 notifies the user of the potential conflict. The notification can be a popup window, a message, or any other type of electronic notification. Further, in the development tool 112, the computer instructions associated with the macro 104 are marked, at block 918. The marking can be performed by highlighting the computer instructions, for example, by changing one or more of: a foreground color, a background color, a font, etc. Alternatively, or in addition, the marking can include changing a border, annotations, etc. associated with the computer instructions of the macro 104. The method 900 is repeated for any additional records (block 910) of the macro 104.
In addition, the development tool also marks computer instructions associated with other compile time conditions 202 which trigger the conflict (e.g., compile time condition ‘PRO=0’ impacts ‘MYDEF’). The other compile time conditions 202 that interact with the macro 104 being checked can be identified from the macro information 412 record for the macro 104. For example, the macro information 412 can be searched to get the definition of the other compile time condition 202 (e.g., ‘PRO’).
In one or more examples, the user can specify one or more target macros 104 for which the conflicts are to be checked, for example, via the initiating command. Alternatively, or in addition, every distinct macro 104 is checked for conflicts in this manner.
Referring to the flowchart of method 500, once the conflicting macros are highlighted, at block 510, the development tool provides support for macro redefinition path.
The method 1000 includes, at block 1002, initiating a path-change detection of a macro 104, where the macro is defined in one file and used in one or more other files in the computer program 106. Further, a macro path-check option of the linker 115 is checked, at block 1004. If macro path-check option is not switched ON, for example, via the initiating command (block 502), via an environment variable, or any other setting that the linker 115 can check, the path change detection is terminated, at block 1006. Alternatively, if the setting is switch ON, a record from the macro information 412 is read for further analysis, at block 1008.
The analysis includes checking at least four conditions. Is MacroEnclosed ON (1010); is PreprocessType=D (1012); does EarlierAssignedMacroValue exists (1014); and is new compile time condition value equal to previous compile time condition value (1016). Based on the outcome of each of these condition checks, the record can be deemed to require a redefining a path, i.e., where the compile time condition is set and where it is used, at block 1018. This process is repeated for every record in the macro information 412.
In the ongoing example scenario, the value ‘1’ of macro ‘MYDEF’ is passed from the option ‘−DMYDEF’ in the compiling command. Considering that the path check is to be performed a records from files ‘a.p’/‘b.p’ is read. If the value of MacroEnclosed is ‘ON’ (1010) then ‘b.h’ line 2 is read, else, ‘b.h’ line 5-6 are read. Further, if the value of Preprocesstype is ‘D’ (1012), one set of computer instructions are to be used (i.e, ‘b.h’ line 2); else, a second set of computer instructions is to be used (i.e., ‘b.h’ line2-3). Next, if EarlierAssignedMacroValue exists (1012), (i.e., PRO exists per ‘b.h’ line 2); else other option has to be performed (i.e., ‘b.h’ line5). Further, if new value of compile time condition 202 is equal to earlier macro value (1016), then use the compile time condition 202 value (i.e., ‘b.c’ line3); else, if the values do not match, the record is marked for macro redefinition path.
In addition to detecting and using the above described macro information 412, one or more embodiments of the present invention facilitate updating source code in large-scale (enterprise) projects with support for multi-level and compiling-unit-crossed isolation including identifying compiled and linked source code. For this, in addition to the above information, the compiler 110 detects and provides a StatementCompiledValid states for each macro 104 (see
Accordingly, the macro preprocessor 410 in combination with the linker 115, can generate, at build time, the macro information 412 that can facilitate detecting a portion of source code in the compute program 102 that has not (or has) been compiled and linked into the execution file 125. or library files. The detection can further be used to update the user interface so as to guide the user to focus (i.e., analyze, edit, debug, etc.) on portions of the computer program 106, which is compiled and linked validly. Embodiments of the present invention, accordingly, reduce development effort and improves project efficiency of delivery.
The improvements are achieved based on generating the macro information 412 using the macro preprocessor, and further enhancing the macro information 412 using the linker 115 to preprocess the source code files 106 to determine the status values, for each macro 104, representing ObjectLinkedValid, FuncSectionLinkedValid and StatementCompiledValid. ObjectLinkedValid represents linking invalidity when the object file is not linked into the executable file 125. FuncSectionLinkedValid represents whether linking invalidity of a function in the computer program 106 when the (unused) function section is removed from the computer program 106. Using such information, the development tool 112 analyzes and removes computer instructions, such as objects and function sections that are not part of the executable file 125, and then updates the macro information 412, particularly the status of ObjectLinkedValid, and FuncSectionLinkedValid. The compiler 110 marks the flag StatementCompiledValid with the compiling validity if the computer instructions unenclosed by the compile time condition 202 are compiled into the object file 120.
In some embodiments of the present invention, the development tool 112 includes a source code isolation module 420 that determines the linking validity of portions of the object file 120 based on the value of the flag ‘ObjectLinkedValid’ from the macro information 412. If the value is invalid (e.g., ‘OFF’), then the source code isolation module 420 skips all the macro information records of the object file. Else, source code isolation module 420 continues to determine the validity of a linked function section, and indicates the validity based on the value of flag ‘FuncSectionLinkedValid’. For example, if the value is invalid (e.g., ‘OFF’), then the source code isolation module 420 skips the macro enclosed records of the function section. Otherwise, the source code isolation module 420 continues to determine validity of the source code segment compilation, and represents the validity using the flag ‘StatementCompiledValid’. If the value is valid (e.g., ‘ON’), then the source code isolation module 420 inserts the record into valid source sections. Otherwise, the source code isolation module 420 continues to determine validity of the macro and represent the validity using the flag ‘MacroEnclosed’. If the value is valid (e.g., ‘ON’), then the source code isolation module 420 inserts the record into valid source sections. The editor and user interface 404 can highlight the records of valid source code sections in one or more embodiments of the present invention.
At each computer instruction, the compiler 110 checks whether the present computer instruction is a definition of a compile time condition 202, at block 1410. If the present computer instruction is a definition of a compile time condition 202 (e.g., “#undef MYDEF”), the compiler 110 assigns flag ‘D’ to the Preprocesstype, at block 1412. Instead, if the computer instruction is a condition of a compile time condition 202 (e.g., “a.c” line 14-17), the development tool 112 checks if the value of the compile time condition 202, is ON, at block 1413. In other words, it is checked if the value of the compile time condition 202 facilitates compiling the enclosed macro 104.
If the compile time condition 202 exists, and if it is ON, the compiler 110 assigns flag ‘S’ to Preprocesstype, at block 1414. Further, in this case (flag S), the macro name, present value, and type are noted from the computer instruction, at block 1416. If the compile time condition 202 exists, and if it is OFF, the StatementCompiledValid flag is set to ‘ON,’ at block 1415.
Further, at block 1410, if there are computer instructions that are enclosed in the compile time condition 202, the MacroEnclosed is set to ‘ON’, (e.g., “a.c” line 14-19), otherwise, it is set to ‘OFF’ (e.g., “a.c” line 9-12). Macro information parameters including SpecificMacroType, ReferredMacroName, and and CurrentMacroValue are also recorded at this time in one or more embodiments of the present invention.
In the case of encountering a definition of a compile time condition 202 (flag D), the compiler 110 checks if the compile time condition 202 (e.g., ‘MYDEF’) was defined before, at block 1418. The check is performed by searching the macro name through the existing information in the macro information 412. If the compile time condition 202 was defined before, the development tool 112 searches and obtains the last value assigned to the compile time condition 202 (e.g., ‘1’ in the ongoing example of MYDEF; 1 is passed by compiling command option ‘−DMYDEF’), at block 1420. The obtained value is recorded into EarlierAssignedMacroValue.
The development tool 112 also collects the metadata associated with the macro 104 such as, file name, line numbers (start, end), etc., at block 1422. The captured information is stored in the macro information 412 structure (e.g., separate file, database, memory, etc.), at block 1424.
The development tool 112 repeats this process for each computer instruction in the computer program 106, and at least for macros 104 in the computer program. Once all of the macros 104 have been processed in this manner and the macro information 412 is captured, the development tool 112 continues to expand the macros 104 and compile and link the computer instructions in the computer program 106 as it typically does, at block 1430.
The development tool 112 determines if MacroEnclosed flag is ON, at 1502, and 1504. If the flag is OFF, the linker information is not added in the macro information 412. Otherwise, if the MacroEnclosed is ON, at block 1506, an object from the object file 120 is parsed, where the object is corresponding to computer instructions that are enclosed in a macro 104 based on a compile time condition 202. The compile time condition 202 that encloses the macro can be the one specified/defined in the command 320. (e.g., MYDEF).
At block 1508, the linker 115 determines if the object identified was included in the executable file 125, or if it was removed prior to generating the executable file 125. Here, “object” can be a source code file 106, for example, “c.c.” If the object has been removed, at block 1510, the development tool iterates over all records (in the macro information 412) of that object, which have the same conditions, i.e., MacroEnclosed=ON, and object removed. For each of these records, the development tool 112 sets the ObjectLinkedValid=OFF, at block 1512. For example, in the scenario of
Alternatively, if the object has not been removed (1508), the development tool parses and reads a function section, at block 1514. Here, a function section is a set of computer instructions that are designated as a “function” in computing programming language. The development tool 112 determines whether the function section is unused, and removed prior to generating the executable file 125, at block 1516. For example, the function section may be unused and removed if that function is never used in the rest of the computer program 106. Alternatively, or in addition, the function section may be unused and removed if the entire function is enclosed in a compile time condition 202 that is not ON at time of compiling. Alternatively, or in addition, the function can be removed because the computer instructions inside the function are enclosed in a compile time condition 202 that is not ON, and hence during optimization, the linker removes that function. In the example of
In the case the function is unused and removed, the development tool 112 traverses the macro information 412 to identify other records/entries corresponding to that function with MacroEnclosed=ON, at block 1518. For each of these entries, the FuncSectionLinkedValid is set to OFF, at block 1520. In the example of
The method 1500 is completed when all the objects and functions in the object file 120 are parsed and the macro information 412 updated as described. In this manner, the development tool can add/update entries/records to the macro information 412, and further use the records/entries in the macro information 412 to identify parts of the computer program 106 that are not being included in the executable file 125.
If, for a record in the macro information, the ObjectLinkedValid=OFF, the filename associated with that record is assigned as an InvalidObjFile, at blocks 1704, 1714. All the records in the macro information 412 that are associated with the same filename are skipped from further processing, at blocks 1716, 1718. In some embodiments, the records associated with the same filename are marked invalid.
In this manner, the method 1700 can isolate the records in the macro information 412 that are corresponding to valid computer instructions.
Embodiments of the present invention provide technical solutions to analyze/isolate the unneeded files/functions in porting large-scale project in an efficient and improved manner compared to existing solutions. embodiments of the present invention, accordingly, increase the efficiency of keeping large-scale projects current with upstream changes and branches that may include code changes made in an open source community. One or more embodiments of the present invention facilitate finding if the code update in upstream branches is needed to be included in a ported version. If it is not required for the target computing platform 130, the updates need not be analyzed and debugged. Further, one or more embodiments of the present invention facilitate editor/user interfaces of software development tools to provide highly readable and more friendly views of large-scale enterprise projects by marking sections of the computer program based on techniques described herein.
Additionally, the technical solutions described herein provide a practical application to support source code macro analysis by identifying and using macro information, which includes determining MacroEnclosed, CurrentMacroValue, Preprocesstype, and EarlierAssignedMacroValue, among other parameters as part of a record for each macro and compile time condition. In one or more embodiments of the present invention, a preprocessor collects and generates the macro information records for all macros in a computer program, and identifies computer instructions that are enclosed or unenclosed based on the macro definition. A compiler and/or linker analyzes the macro information to detect macro definition conflicts by comparing MacroEnclosed status and CurrentMacroValue of the user-specified or default specified type macro. The tools then search records in the macro information to determine the corresponding definition of macros which make possible impact. Further, the linker supports the macro redefinition path across compiling units, e.g., files, by locating the records of macro information with the status of macroEnclosed and the value of Preprocesstype, determining the valid redefinition after comparing AssignedMacroValue and EarlierAssignedMacroValue.
The technical solutions described herein provide an improvement to computing technology, and particularly debugging. In one or more embodiments of the present invention, technical solutions herein facilitate to analyze/figure out the root cause of macro conflict which causes one or more computer instructions to not be compiled into object file as expected and give macro redefinition warning across compiling units, e.g., files. The technical solutions herein also increase the efficiency of the root cause locating using the macro information. The technical solutions herein also improve identifying macro redefinition for developers, especially for large enterprise opensource projects with complicated macros used. The technical solutions facilitate an editor/GUI to provide readable and more user-friendly views of the macros and compile time conditions that cause conflicts during compilation.
The technical solutions described herein can be, or can be part of compilers and IDEs, like ECLIPSE®, VISUAL STUDIO®, etc. It is understood that although examples herein are described using a particular computer programming language, the technical solutions herein are not limited to any particular computer programming language.
It is to be understood that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.
Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.
Characteristics are as follows:
On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.
Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).
Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).
Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service.
Service Models are as follows:
Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.
Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.
Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).
Deployment Models are as follows:
Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.
Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.
Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.
Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).
A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure that includes a network of interconnected nodes.
Referring now to
Referring now to
Hardware and software layer 60 includes hardware and software components. Examples of hardware components include: mainframes 61; RISC (Reduced Instruction Set Computer) architecture based servers 62; servers 63; blade servers 64; storage devices 65; and networks and networking components 66. In some embodiments, software components include network application server software 67 and database software 68.
Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 71; virtual storage 72; virtual networks 73, including virtual private networks; virtual applications and operating systems 74; and virtual clients 75.
In one example, management layer 80 may provide the functions described below. Resource provisioning 81 provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and Pricing 82 provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may include application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal 83 provides access to the cloud computing environment for consumers and system administrators. Service level management 84 provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment 85 provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.
Workloads layer 90 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation 91; software development and lifecycle management 92; virtual classroom education delivery 93; data analytics processing 94; transaction processing 95; and computer program processing and analyzing 96.
Turning now to
As shown in
The computer system 2300 comprises an input/output (I/O) adapter 2306 and a communications adapter 2307 coupled to the system bus 2302. The I/O adapter 2306 may be a small computer system interface (SCSI) adapter that communicates with a hard disk 2308 and/or any other similar component. The I/O adapter 2306 and the hard disk 2308 are collectively referred to herein as a mass storage 2310.
Software 2311 for execution on the computer system 2300 may be stored in the mass storage 2310. The mass storage 2310 is an example of a tangible storage medium readable by the processors 2301, where the software 2311 is stored as instructions for execution by the processors 2301 to cause the computer system 2300 to operate, such as is described herein below with respect to the various Figures. Examples of computer program product and the execution of such instruction is discussed herein in more detail. The communications adapter 2307 interconnects the system bus 2302 with a network 2312, which may be an outside network, enabling the computer system 2300 to communicate with other such systems. In one embodiment, a portion of the system memory 2303 and the mass storage 2310 collectively store an operating system, which may be any appropriate operating system, such as the z/OS or AIX operating system from IBM Corporation, to coordinate the functions of the various components shown in
Additional input/output devices are shown as connected to the system bus 2302 via a display adapter 2315 and an interface adapter 2316 and. In one embodiment, the adapters 2306, 2307, 2315, and 2316 may be connected to one or more I/O buses that are connected to the system bus 2302 via an intermediate bus bridge (not shown). A display 2319 (e.g., a screen or a display monitor) is connected to the system bus 2302 by a display adapter 2315, which may include a graphics controller to improve the performance of graphics intensive applications and a video controller. A keyboard 2321, a mouse 2322, a speaker 2323, etc. can be interconnected to the system bus 2302 via the interface adapter 2316, which may include, for example, a Super I/O chip integrating multiple device adapters into a single integrated circuit. Suitable I/O buses for connecting peripheral devices such as hard disk controllers, network adapters, and graphics adapters typically include common protocols, such as the Peripheral Component Interconnect (PCI). Thus, as configured in
In some embodiments, the communications adapter 2307 can transmit data using any suitable interface or protocol, such as the internet small computer system interface, among others. The network 2312 may be a cellular network, a radio network, a wide area network (WAN), a local area network (LAN), or the Internet, among others. An external computing device may connect to the computer system 2300 through the network 2312. In some examples, an external computing device may be an external webserver or a cloud computing node.
It is to be understood that the block diagram of
The present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration. The computer program product may include a computer-readable storage medium (or media) having computer-readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer-readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer-readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer-readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer-readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer-readable program instructions described herein can be downloaded to respective computing/processing devices from a computer-readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium within the respective computing/processing device.
Computer-readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source-code or object code written in any combination of one or more programming languages, including an object-oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer-readable program instruction by utilizing state information of the computer-readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer-readable program instructions may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments described herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5946488 | Tanguay et al. | Aug 1999 | A |
| 6003143 | Kim et al. | Dec 1999 | A |
| 7337438 | Dobbins | Feb 2008 | B1 |
| 7571431 | Hampapuram et al. | Aug 2009 | B2 |
| 7810080 | Plum | Oct 2010 | B2 |
| 9378014 | Wilson et al. | Jun 2016 | B2 |
| 9569184 | Tejani et al. | Feb 2017 | B2 |
| 10802825 | Guan et al. | Oct 2020 | B2 |
| 20030033588 | Alexander | Feb 2003 | A1 |
| 20030105620 | Bowen | Jun 2003 | A1 |
| 20040193957 | Swoboda et al. | Sep 2004 | A1 |
| 20070011669 | Varma et al. | Jan 2007 | A1 |
| 20130139132 | Kass et al. | May 2013 | A1 |
| 20140189662 | Mameri et al. | Jul 2014 | A1 |
| 20150033202 | Wilson et al. | Jan 2015 | A1 |
| 20150058832 | Gonion | Feb 2015 | A1 |
| 20160062753 | Champagne | Mar 2016 | A1 |
| 20170161062 | Banerjee et al. | Jun 2017 | A1 |
| 20170192758 | Apte et al. | Jul 2017 | A1 |
| 20170344349 | He | Nov 2017 | A1 |
| 20200192662 | Hu | Jun 2020 | A1 |
| 20200371906 | Tertzakian | Nov 2020 | A1 |
| 20220206769 | Johnson et al. | Jun 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 101968767 | Feb 2011 | CN |
| 2003005959 | Jan 2003 | JP |
| Entry |
|---|
| Title: Variability-aware parsing in the presence of lexical macros and conditional compilation, author: C Kästner, published on 2011. |
| Title: An empirical analysis of C preprocessor use, author: MD Ernst, published on 2002. |
| Anonymous, “Method to Enable Macros Debugging,” IP.com Prior Art Database Technical Disclosure, IPCOM000202015D, Dec. 1, 2010, pp. 1-6. |
| Chiueh et al., “RAD: A Compile-Time Solution to Buffer Overflow Attacks,” IEEE 2001, 9 pages. |
| Graebner et al., “Generating SAS Source Code with SAS Macros,” Pharmaceutical Research Associates, Inc. ; Coders' Corner; URL: https://support.sas.com/resources/papers/proceedings/proceedings/sugi23/Coders/p81.pdf Retrieved: Jul. 2021; pp. 1-2. |
| Huang et al., “Checking Source Code Validity at Time of Code Update,” U.S. Appl. No. 17/498,138, filed Oct. 11, 2021. |
| Huang et al., “Identifying Computer Instructions Enclosed by Macros and Conflicting Macros at Build Time,” U.S. Appl. No. 17/498,141, filed Oct. 11, 2021. |
| BIBM: List of IBM Patents or Patent Applications Treated as Related (Appendix P); Date Filed: Sep. 14, 2022; 2 pages. |
| Lindlan et al., “A Tool Framework for Static and Dynamic Analysis of Object-Oriented Software with Templates,” IEEE/ACMSC2000 Conference, 11 pages. |
| Overbey et al., “A Foundation for Refactoring C with Macros,” In Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering (FSE 2014), Nov. 16-21, 2014, pp. 75-85. |
| Woods, “A Framework for the Assessment of Knowledge Transfer in Software Development Organization,” Massachusetts Institute of Technology, May 2001, 85 pages. |
| Braz et al., A Change-Centric Approach to Compile Configurable Systems with #ifdefs, ACM SIGPLAN Notices, Association for Computing Machinery, vol. 52, No. 3, Oct. 2016, pp. 109-119. |
| Dévai et al., “Service Layer for IDE Integration of C/C++ Preprocessor Related Analysis,” Computational Science and its Applications, Lecture Notes in Computer Science, 2015, 16 pages. |
| International Search Report and Written Opinion; dated Jan. 25, 2023; Application No. PCT/EP2022/077948 Filed: Oct. 7, 2022; 17 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20230114540 A1 | Apr 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17498138 | Oct 2021 | US |
| Child | 17931678 | US |
