Managing a Migration Report

Downloading a Migration Port

After creating a migration task, you can download the migration report in either of the following ways:

Downloading it in the historical report list
1. Click Source Code Porting in the navigation pane on the left. Historical reports are listed.
  - Fuzzy search by task name is supported.
  - You can click to select a report display mode: either tiled or monthly.
  - You can click on the right of a task name to rename the corresponding historical report.
  - Click on the right of a task name to delete a specified historical report, or click on the right of source code porting to delete all historical reports. Deleted data cannot be recovered. Exercise caution when performing this operation.
2. Locate the report to be downloaded.
3. Click next to the historical report name to download the report.
Downloading it on the report details page
1. Click Source Code Porting in the navigation pane on the left.
2. In the historical report list, click the report name of the analysis task. The report page is displayed.
3. Click Download Report in the upper right corner of the page to download the migration report.

Viewing a Downloaded Migration Report

The following describes how to view a CSV report on architecture source code porting. Figure 1 describes the basic information about a downloaded report.

Figure 1 Basic information in a report

**Table 1** Parameters in a report
Parameter	Description
Report Generated	Time when the report is generated.
Configuration	Task name, report generation time, source file storage path, target OS, target OS kernel version, compiler version, build tool, compile command, whether an interpretative language or Go language is included, and user-defined x86 macro.
File Scan Statistics	Number of scanned files and the number of files to be ported.
Dependency File Statistics	Number of architecture-related files on which the source package depends.
Source File Statistics	Number of scanned files, number of files to be modified, number of lines of code to be modified, and total number of rule and suggestion items.
Architecture-Related Dependencies	Details about the dependency files related to the architecture. File name: dependency file name. File type: dependency file type. Analysis result: dependency file analysis result. Handling suggestion: suggestion for handling the file to be modified. URL: link for downloading the files available on the Kunpeng platform.
Source File Scan Details	Details of the source code analysis report: File name: full path to the file to be scanned. File type: type of the file to be scanned. Lines (start line, end line): line numbers of the function in the file. Lines: total number of rows of a function in the file. Category: keyword type. Keyword: keyword name. Suggestion: porting suggestion or tip. Description: keyword usage description. Modification Level: For details, see Source Code Porting Modification Levels. Reason: why the file must be modified.

Keyword types:

INVALID_CATEGORY: invalid porting option type
INTRINSICS_INCLUDE: # intrinsics inline function in the header file
INTRINSICS: intrinsic inline function
COMPILER_MACRO: compiler macro
ATTRIBUTE: compiler attribute
COMPILER_BUILTIN: compiler built-in function
COMPILER_OPTION: compiler option
BUILTIN_ASSEMBLES: built-in assembly
LIBS: dynamic link libraries
COMPILER_OPTION_SPECIAL: special compiler option
MODULE_FUNCTION: module function
AARCH_SPECIFIC: specific to the AArch platform (the value of keep-going is used to determine whether to end the scan earlier than expected)
PURE_ASSEMBLES: pure assembly file
AUTOMAKE_FILE: Automake file
FORTRAN_COMPILER_OPTION: GFortran compilation option
FORTRAN_BUILTIN: Fortran built-in function
FORTRAN_GRAMMAR: Fortran syntax
PRECOMPILED_MACRO: precompiled macro
PYTHON_LIBRARY: SO files detected from the Python file
PYTHON_LOAD_LIBRARY: lines of the SO files detected from the Python file
JAVA_LIBRARY: SO files detected from the Java file
JAVA_LOAD_LIBRARY: lines of the SO files detected from the Java file
SCALA_LIBRARY: SO files detected from the Scala file
SCALA_LOAD_LIBRARY: lines of the SO files detected from the Scala file
FORTRAN_MODULE_FILE: .mod file compiled from the Fortran module file
MIX_FUNCTION_NOT_MATCH: mismatch between the intermodulation parameters and return values of the C and Fortran functions
INTRINSICS_LIBRARY: SO link library of intrinsic functions added to build file prompts
TEE_UNSUPPORTED_API: POSIX APIs not supported by TEEs
JAVA_MATH_LIBRARY: location of the math library detected in the Java file

The description of the module function is as follows:

       
            current usage:
add_library(test1 STATIC attr_gcc5.1.c builtin_gcc5.1.c )
The general signature is:
    add_library(<name> [STATIC | SHARED | MODULE]
                [EXCLUDE_FROM_ALL]
                [source1] [source2 ...])
For details: https://cmake.org/cmake/help/v3.13/command/add_library.html

current usage: function usage in the current file
The general signature is: usage of the official general function
For details: link to the official help document of the module function

Deleting an Analysis Report

Click Source Code Porting in the navigation pane on the left. Historical reports are listed.
In the Historical Reports area, locate the report to be deleted and click .
- A maximum of 50 reports can be stored. You can click next to a function name to delete all related historical reports.
- After a report is deleted, the analysis data in the report cannot be restored. Exercise caution when performing this operation.
In the displayed dialog box, click OK.

Parent topic: Source Code Porting