Using the Auto Repair by Compiler

Supported OSs and GCC Versions

See Table 1.

• The GCC versions listed are the default GCC versions supported by the OSs. If the GCC version of the server has been upgraded, compatibility issues may occur.
• The supported GCC versions are official GCC branches. Do not use the GCC for openEuler versions.

Environment Configuration

Before using this function, you need to configure the environment as follows:

1. Download required software packages.
   • GCC source code: https://gcc.gnu.org/ (Download the source code of the corresponding version from the official GCC website.)
   • GCC repair tool patch: https://github.com/kunpengcompute/devkitdriver/tree/main/gccchecker (for Debian and RHEL OSs)
   • Memory consistency repair component: Obtain /devkitplugins/affinity/tools/weakconsistency/gccchecker/gcctool.tar.gz in the DevKit installation directory.
2. Install the memory consistency repair component.
   1. Decompress the installation package.

      1	tar xf gcctool.tar.gz

      After the decompression, check that the following files exist in the gcctool/bin directory:

      gcctool, gcctool-bin, and libstdc++.so.6

   2. Configure environment variables.

      Place gcctool in the installation directory and configure environment variables.

      1	export PATH=/path/to/gcctool/bin:$PATH

3. Apply the GCC patch.
   

   If "'patch' command not found" is displayed, run the following command to install the patch:

   Debian OSs:

   1	apt install patch

   RHEL OSs:

   1	yum install patch

   1 2	cd /gcc/source/root/dir patch -p1 < /path/to/gcc/patch/file

4. Compile GCC.

   For details about how to compile the GCC source code, see the official GCC documents. The patch does not affect the GCC dependency components and the compilation process. If you have any GCC compilation problem, visit the GNU community.

Tool Usage

After the environment is set up, perform the following steps to use the tool:

1. Set the optimization mode of the memory consistency repair component.

   1	export HW_DEBUG=[ 0 | 1 | 2 ]

   You can set the repair optimization mode through the environment variable. The default mode is 0.

   • 0: disables the memory consistency repair function.
   • 1: uses component optimization rules. This setting helps minimize the performance loss.
   • 2: uses the most secure repair policy. This setting compromises the performance a lot.

   

   The default mode 0 indicates that no repair operation is performed.

   If you want to enable this function, change it to another mode.

2. (Optional) Define the range of source code that can be automatically fixed.
   1. You can customize the source code repair range by file or function. After the allowlist is configured, the repair component repairs only the content in the list. The allowlist must meet the following requirements:
      • The file list starts with files:. Each file occupies one line.
      • The file path must be an absolute path.
      • Only C, C++, and Fortran files are supported. Pure assembly files are not supported.
      • The function list starts with functions:. Each function occupies one line.
      • C/C++ common functions are supported. Templates or functions with the abi_tag attribute are not supported.

      Allowlist example:

      1 2 3 4 5 6 7 8 9 10 11 12 13

      files: /path/to/file/a /path/to/./file/b /path/to/../file/c /path/to/file/d functions: func_a func_b() func_c(int xxx) int func_d() classA::func_e ns::classB::func_f() std::string nsA::nsB::classC::func_g(int xxx)

   2. The repair component obtains the path of the allowlist.

      You can set an environment variable to specify the path of the allowlist. The path is not specified by default.

      export AUTOFIXLIST=/path/to/allowlist

3. Compile software.

   The compilation process remains unchanged.

   

   Remove the -pipe compilation option if it is used in the previous compilation. This does not affect the result of the previous compilation.