https://bugs.kde.org/show_bug.cgi?id=442168
--- Comment #7 from Xavier Roche <xavier.ro...@algolia.com> --- (In reply to Julian Seward from comment #4) > (In reply to Xavier Roche from comment #2) > > > The difference between the correctly executed code under valgrind and the > > faulty one: > > > - movsd %xmm0, (%rsp) # 8-byte Spill > > + vmovsd %xmm0, (%rsp) # 8-byte Spill > > Can you give some more information about why you think the change from > movsd to vmovsd causes the error? Also, which one gives correct execution > and which doesn't? The correct one is movsd; the faulty one is vmovsd. This only happens with clang-12 [12.0.0-3ubuntu1~20.04.3] (not clang-11) and only when running valgrind. g++-10 (Ubuntu 10.3.0-1ubuntu1~20.04) does not trigger the problem either. So this is a specific clang-12 issue. As for the reason, I'm not fluent enough on x86-64 assembly to make any educated guess unfortunately. This might have nothing to do with vmovsd -- You are receiving this mail because: You are watching all bug changes.