Managing Analysis Reports

Downloading an Analysis Report

After an analysis task is created and the analysis is complete, you can download the analysis 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.
2. Locate the report to be downloaded.
3. Click next to the task name and click Download Report (.csv) or Download Report (.html) to download the analysis 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 details page is displayed.
3. Click Download Report (.csv) or Download Report (.html) to download the analysis report.

Viewing a Downloaded Analysis Report

Figure 1 shows the basic information in a downloaded report.

Figure 1 Basic information in an analysis report

**Table 1** Parameters in an analysis report
Parameter		Description
Scanned time		Time when the code was scanned.
Configuration	Task name	Name of the source code porting task.
	Scanned time	Time when the code was scanned.
	Source Code File Path	Directory where the scanned source code is stored.
	Target OS	Target OS.
	Target OS Kernel Version	Kernel version of the target OS.
	Compiler Version	Version of the compiler.
	Build Tool	Build tool.
	Software make command	Compile command.
	Interpreted(Python,Java,Scala)	Indicates whether the analysis object includes an interpreted language file. True: yes False: no
	Go	Indicates whether the analysis object includes a Go language file. True: yes False: no
	Custom x86 Macros	Custom x86 macros.
Summary	Adaptable for Compatibility: x, To be Modified: x, Total Dependencies: x	Number of files compatible with the Kunpeng platform, number of files to be modified, and number of dependency library files.
	Source Need Migrated	Indicates whether the source code needs to be ported. Yes No
	Scanned xx C/C++/Fortran files, xx Makefile/CMakeLists.txt/Automake related files, total xx files need to be migrated.	Total number of C/C++/Fortran files, number of Makefile /CMakeLists.txt/Automake related files, and number of files to be ported.
	Total xx lines C/C++/Makefile/CMakeLists.txt/Automake code and xx lines embedding ASM code need to be migrated.	Total lines of source code and lines of inline assembly code to be ported.
	Scanned xx pure assembly files, xx pure assembly files to be migrated.	Total number of pure assembly files, number of pure assembly files to be ported, and lines of assembly code to be ported.
	Scanned x Go files, total x Go files xx lines need to be migrated.	Total number of Go files, number of Go files to be ported, and lines of code to be ported.
	Scanned xx python files, total xx files xx lines need to be migrated.	Total number of Python files, number of Python files to be ported, and lines of Python code to be ported.
	Scanned xx java files, total xx files xx lines need to be migrated.	Total number of Java files, number of Java files to be ported, and lines of Java code to be ported.
	Scanned xx scala files, total xx files xx lines need to be migrated.	Total number of Scala files, number of Scala files to be ported, and lines of Scala code to be ported.
	Estimated transplant workload: xx person/months.(C/C++/Fortran/Go, 500 Line/PM; ASM, 250Line/PM)	Estimated manpower (x person months) for source code porting. Baseline workload: 1 person month = 500 lines of C, C++, Fortran, or Go source code or 250 lines of assembly code
Architecture-related Dependencies		Detailed information about the dependency library files scanned: File Name File Type Analysis Results Handling Suggestions URL
Source files scan details are as follows:		Details of the source code analysis report: filename: full path of the file scanned. filetype: type of the file scanned. line number: line number of a function in the file. rows: total number of rows of a function in the file. category: keyword type. keyword suggestion: porting suggestion. description: description of the keyword usage. modification_level: level of the modification. reason: reason for the operation.

Keyword types:

Intrinsics: intrinsic inline function
CompilerMacro: compiler macro
Attribute: compiler attribute
CompilerBuiltin: compiler built-in function
CompilerOption: compiler option
BuiltinAssembles: built-in assembly
Libs: dynamic link libraries
CompilerOptionSpecial: special compiler option
ModuleFunction: module function
PureAssembles: pure assembly file
AutomakeFile: automake file
InvalidCategory: invalid porting option type
AarchSpecific: specific to the AArch platform
FortranCompilerOption: GFortran compilation option
FortranBuiltin: Fortran built-in function
FortranGrammar: Fortran syntax
PrecompiledMacro: precompiled macro

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.
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