Documentation
Rate This Document
Findability
Accuracy
Completeness
Readability
SubmitClose

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 page is displayed.
    3. In the upper right corner of the page, click Download Report. Then click Download Report (.csv) or Download Report (.html) to download the analysis report.

Viewing a Downloaded Analysis Report

The following uses a CSV report as an example. Figure 1 shows the basic information in an analysis report.

Figure 1 Basic information in an analysis report
Table 1 Parameters in an analysis 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: level of the file modification.
  • Reason: why the file must be modified.

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:

1
2
3
4
5
6
7
 
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

  1. Click Source Code Porting in the navigation pane on the left. Historical reports are listed.
  2. 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.
  3. In the displayed dialog box, click OK.
Parent topic: Source Code Porting