https://bugs.kde.org/show_bug.cgi?id=456948
Bug ID: 456948
Summary: Unrecognized instruction (AVX2) in Intel oneAPI MPI
2021.6 library
Product: valgrind
Version: 3.19.0
Platform: RedHat RPMs
OS: Other
Status: REPORTED
Severity: critical
Priority: NOR
Component: memcheck
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Hi,
with the new Intel oneAPI MPI library 2021.6 (release mode) we run into the
following problem:
vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0xAE 0x3B 0x49 0x81 0xC6
0x0 0xFC 0xFF
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F
vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0
==2714078== valgrind: Unrecognised instruction at address 0xf24853f.
==2714078== at 0xF24853F: I_MPI_memcpy_multipage_flush_src_avx2 (in
/net/aws1de027/data/repo_cache/mature/intelmpi_rt/2021.6.0/LINUX64_217/lib/libmpi.so.12)
==2714078== by 0xF707593: ??? (in
/net/aws1de027/data/repo_cache/mature/intelmpi_rt/2021.6.0/LINUX64_217/lib/libmpi.so.12)
==2714078== by 0xF7036F5: ??? (in
/net/aws1de027/data/repo_cache/mature/intelmpi_rt/2021.6.0/LINUX64_217/lib/libmpi.so.12)
==2714078== by 0xF700DFC: ??? (in
/net/aws1de027/data/repo_cache/mature/intelmpi_rt/2021.6.0/LINUX64_217/lib/libmpi.so.12)
==2714078== by 0xF034940: MPID_Progress_wait (in
/net/aws1de027/data/repo_cache/mature/intelmpi_rt/2021.6.0/LINUX64_217/lib/libmpi.so.12)
==2714078== by 0xF5C8B7D: MPIR_Wait_impl (in
/net/aws1de027/data/repo_cache/mature/intelmpi_rt/2021.6.0/LINUX64_217/lib/libmpi.so.12)
==2714078== by 0xF4CA613: PMPI_Recv (in
/net/aws1de027/data/repo_cache/mature/intelmpi_rt/2021.6.0/LINUX64_217/lib/libmpi.so.12)
....
==2714078== Your program just tried to execute an instruction that Valgrind
==2714078== did not recognise. There are two possible reasons for this.
==2714078== 1. Your program has a bug and erroneously jumped to a non-code
==2714078== location. If you are running Memcheck and you just saw a
==2714078== warning about a bad jump, it's probably your program's fault.
==2714078== 2. The instruction is legitimate but Valgrind doesn't handle it,
==2714078== i.e. it's Valgrind's fault. If you think this is the case or
==2714078== you are not sure, please let us know and we'll try to fix it.
==2714078== Either way, Valgrind will now raise a SIGILL signal which will
==2714078== probably kill your program.
Platform and valgrind version
RHEL7.9 (devtoolset 7)
valgrind 3.19
Best regards
Frank
--
You are receiving this mail because:
You are watching all bug changes.
