[valgrind] [Bug 478624] Valgrind incompatibility with binutils-2.42 on x86 with new nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)

2024-02-01 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=478624

Tom Hughes  changed:

   What|Removed |Added

 CC||sch...@linux-m68k.org

--- Comment #4 from Tom Hughes  ---
*** Bug 480680 has been marked as a duplicate of this bug. ***

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

[valgrind] [Bug 478624] Valgrind incompatibility with binutils-2.42 on x86 with new nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)

2024-01-22 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=478624

Mark Wielaard  changed:

   What|Removed |Added

 CC||m...@klomp.org
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #3 from Mark Wielaard  ---
Gentoo, Debian and Fedora already pulled in this patch.
Now also added to VALGRIND_3_22_BRANCH:

commit 41ff9aa49f6c54c66d0e6b37f265fd9cb0176057
Author: Paul Floyd 
Date:   Sun Dec 17 14:18:51 2023 +0100

Bug 478624 - Valgrind incompatibility with binutils-2.42 on x86 with new
nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)

It was a bit of a struggle to get the testcase to build
with both clang and gcc (oddly enough gcc was more difficult) so
I just resorted to using .byte arrays.

(cherry picked from commit d35005cef8ad8207542738812705ceabf137d7e0)

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

[valgrind] [Bug 478624] Valgrind incompatibility with binutils-2.42 on x86 with new nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)

2023-12-17 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=478624

--- Comment #2 from Paul Floyd  ---
Should be fixed with this. Can someone check with the latest binutils?

commit d35005cef8ad8207542738812705ceabf137d7e0 (HEAD -> master, origin/master,
origin/HEAD, gnu_binutils_nop)
Author: Paul Floyd 
Date:   Sun Dec 17 14:18:51 2023 +0100

    Bug 478624 - Valgrind incompatibility with binutils-2.42 on x86 with new
nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)

It was a bit of a struggle to get the testcase to build
with both clang and gcc (oddly enough gcc was more difficult) so
I just resorted to using .byte arrays.

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

[valgrind] [Bug 478624] Valgrind incompatibility with binutils-2.42 on x86 with new nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)

2023-12-17 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=478624

Paul Floyd  changed:

   What|Removed |Added

 CC||pjfl...@wanadoo.fr

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

[valgrind] [Bug 478624] Valgrind incompatibility with binutils-2.42 on x86 with new nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)

2023-12-16 Thread Sam James
https://bugs.kde.org/show_bug.cgi?id=478624

Sam James  changed:

   What|Removed |Added

   See Also||http://bugs.debian.org/1057
   ||693

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

[valgrind] [Bug 478624] Valgrind incompatibility with binutils-2.42 on x86 with new nop patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)

2023-12-16 Thread Sam James
https://bugs.kde.org/show_bug.cgi?id=478624

Sam James  changed:

   What|Removed |Added

Summary|Valgrind incompatibility|Valgrind incompatibility
   |with binutils-2.42 on x86   |with binutils-2.42 on x86
   ||with new nop patterns
   ||(unhandled instruction
   ||bytes: 0x2E 0x8D 0xB4 0x26)

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

[valgrind] [Bug 478624] Valgrind incompatibility with binutils-2.42 on x86

2023-12-16 Thread Sam James
https://bugs.kde.org/show_bug.cgi?id=478624

--- Comment #1 from Sam James  ---
 For a testcase we probably should just have a simple assembly/byte
sequence of all the "nops" used in
https://sourceware.org/cgit/binutils-gdb/tree/gas/config/tc-i386.c#n1256

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