https://bugs.kde.org/show_bug.cgi?id=456948
--- Comment #12 from f.roe...@magmasoft.de ---
Hi,
Just as an Info:
Luckily one can overcome the behavior of the mpi library with a environment
variable I_MPI_SHM=bdw_sse or I_MPI_SHM=bdw_avx2 for non avx512 memcopy.
I found out searching google
https://bugs.kde.org/show_bug.cgi?id=456948
--- Comment #11 from Tom Hughes ---
That is exactly what we do and why Mark said your program should be checking
the CPU capabilities.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=456948
--- Comment #10 from Mark Wielaard ---
(In reply to f.roe...@magmasoft.de from comment #9)
> Thank you for your answer. The problem occurs in the Intel 2021.6 MPI
> library. As far as I understand it runs this code path when cpuid returns
> positive if
https://bugs.kde.org/show_bug.cgi?id=456948
--- Comment #9 from f.roe...@magmasoft.de ---
Hi,
Thank you for your answer. The problem occurs in the Intel 2021.6 MPI library.
As far as I understand it runs this code path when cpuid returns positive if
avx512 is available. Could valgrind emulate
https://bugs.kde.org/show_bug.cgi?id=456948
--- Comment #8 from Mark Wielaard ---
(In reply to f.roe...@magmasoft.de from comment #6)
> Is this also a forbidden instruction?
> vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7C 0x48 0x10 0x2
> 0x49 0x81 0xC0 0x0
> vex amd64->IR: REX=0
https://bugs.kde.org/show_bug.cgi?id=456948
Tom Hughes changed:
What|Removed |Added
CC||t...@compton.nu
--- Comment #7 from Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=456948
--- Comment #6 from f.roe...@magmasoft.de ---
Is this also a forbidden instruction?
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7C 0x48 0x10 0x2 0x49
0x81 0xC0 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:
https://bugs.kde.org/show_bug.cgi?id=456948
--- Comment #5 from f.roe...@magmasoft.de ---
I found a solution : )
https://github.com/pmem/valgrind/tree/pmem-3.19
With this version we can use valgrind with new Intel MPI 2021.6
Best regards
Frank
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=456948
--- Comment #4 from Mark Wielaard ---
(In reply to f.roe...@magmasoft.de from comment #3)
> Thank you for your answer, is there a possible workaround to get valgrind
> running?
> Is there a time schedule for a new valgrind build which fixes this issue?
https://bugs.kde.org/show_bug.cgi?id=456948
--- Comment #3 from f.roe...@magmasoft.de ---
Thank you for your answer, is there a possible workaround to get valgrind
running?
Is there a time schedule for a new valgrind build which fixes this issue?
Best regards
Frank
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=456948
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=456948
Mark Wielaard changed:
What|Removed |Added
Summary|Unrecognized instruction|Unrecognized instruction
12 matches
Mail list logo
