https://bugs.kde.org/show_bug.cgi?id=383010

--- Comment #51 from Tanya <tatyana.a.mine...@intel.com> ---
Hello,

Attached updated AVX-512 patch for KNL and SkyLake.
It is based on the GIT master from Feb. 20 (commit
1c9a0bf58a47e855e6e5bf78a30bcee0af835804)

Attached files
~~~~~~~~~~~~~~
- AVX-512_KNL_SKX_p1_main.patch - Main AVX-512 Valgrind patch
- AVX-512_KNL_SKX_p2_data.patch - Files, automatically generated by a script.
These files are required for the build
- AVX-512_KNL_SKX_p3_test.patch - AVX-512 regression tests
- AVX-512_KNL_SKX_p4_filegen.patch - Generator of Valgrind AVX-512 .c files
from a file with instruction descriptions. Not required for build or usage;
useful for adding new instructions or modifying AVX-512 behaviour

Functionality
~~~~~~~~~~~~~
- No known regressions on AVX2 machines
- Nulgrind is functional (no known failures of small AVX-512 applications) on
KNL and SkyLake
- Memcheck does not crash on AVX-512 code; the analysis might still be
incorrect

Limitations
~~~~~~~~~~~
- Needs GCC version 8 or newer
- Cannot emulate AVX-512 code on AVX-2 or older machine (some AVX-512
instructions are emulated through intrinsics)

Build and test
~~~~~~~~~~~~~~
Clone Valgrind master:
> git clone https://sourceware.org/git/valgrind.git
> cd valgrind
Apply the patch:
> git apply AVX-512_KNL_SKX_p1_main.patch
> git apply AVX-512_KNL_SKX_p2_data.patch
> git apply AVX-512_KNL_SKX_p3_test.patch
Optional development tool, not required for the build process:
> git apply AVX-512_KNL_SKX_p4_filegen.patch

Build:

Please check that GCC version is 8 or higher.
> ./autogen.sh
> ./configure --prefix=<install-path>
On AVX-512 machine, verify that AVX-512 version will be built: open config.log
and check that "BUILD_AVX512_TESTS_TRUE=''" and "CFLAGS=' -DAVX_512'" lines
exist.
> make install

Quick test:
<install-path>/bin/valgrind ls

Invoke a script to generate reference AVX-512 tests results (they are not
provided with the patch because file size exceeds limit set by bugtracker):
> ./scripts/generate_test_results.sh
Run regression tests:
> make regtest

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to