[valgrind] [Bug 451837] When profiling this specific executable, valgrind fails to break down 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 into 2 separate instructions

2024-02-24 Thread Gabriel Ravier
https://bugs.kde.org/show_bug.cgi?id=451837 Gabriel Ravier changed: What|Removed |Added CC||gabrav...@gmail.com -- You are receiving

[valgrind] [Bug 451837] When profiling this specific executable, valgrind fails to break down 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 into 2 separate instructions

2022-06-14 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=451837 Tom Hughes changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED

[valgrind] [Bug 451837] When profiling this specific executable, valgrind fails to break down 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 into 2 separate instructions

2022-03-28 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=451837 --- Comment #6 from Tom Hughes --- That looks the same to me if you ignore the extra bytes. The valgrind decoder doesn't know how long the instruction is (because it doesn't understand it) so it just dumps enough bytes to guarantee getting the whole

[valgrind] [Bug 451837] When profiling this specific executable, valgrind fails to break down 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 into 2 separate instructions

2022-03-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451837 --- Comment #5 from ytr...@sdf-eu.org --- Except it doesn t (I m having real avx512 hardware I can provide for testing) because Valgrind is disassembling the instruction incorrectly. 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 instead of 0x62 0xF1

[valgrind] [Bug 451837] When profiling this specific executable, valgrind fails to break down 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 into 2 separate instructions

2022-03-28 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=451837 --- Comment #4 from Tom Hughes --- I meant "without valgrind" there of course... -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 451837] When profiling this specific executable, valgrind fails to break down 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 into 2 separate instructions

2022-03-28 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=451837 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #3 from Tom Hughes

[valgrind] [Bug 451837] When profiling this specific executable, valgrind fails to break down 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 into 2 separate instructions

2022-03-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451837 --- Comment #2 from ytr...@sdf-eu.org --- The binary runs correctly without Valdrind, so are you sure about avx512? The instruction looks like 256 bits. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 451837] When profiling this specific executable, valgrind fails to break down 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 into 2 separate instructions

2022-03-28 Thread Josef Weidendorfer
https://bugs.kde.org/show_bug.cgi?id=451837 Josef Weidendorfer changed: What|Removed |Added Assignee|josef.weidendor...@gmx.de |jsew...@acm.org

[valgrind] [Bug 451837] When profiling this specific executable, valgrind fails to break down 0x62 0xF1 0x7F 0x28 0x7F 0x2 0xF 0x87 0x95 0xA1 into 2 separate instructions

2022-03-23 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451837 ytr...@sdf-eu.org changed: What|Removed |Added CC||ytr...@sdf-eu.org -- You are receiving