https://bugs.kde.org/show_bug.cgi?id=502830
--- Comment #4 from Bo <b...@hhlx.net> --- (In reply to Mark Wielaard from comment #3) > (In reply to Bo from comment #2) > > Regarding your question about Neoverse N2, can you confirm if Valgrind > > supports it? > > I found on the official site that "ARM64/Linux: > (In reply to Paul Floyd > > from comment #1) > > > Does it work the the minimal options to compile and link the exe? > > > > > > It looks like the problem is in ld.so. Otherwise I doubt that we support > > > neoverse-n2. > > > > I tried the following options, but I encountered the same issues: > > 1. --sysroot=/PATH/TO/sysroots > > 2. -mcpu=neoverse-n2 --sysroot=/PATH/TO/sysroots > > supported for ARMv8." > > However, I'm unsure about ARMv9 (Neoverse N2). > > No, valgrind doesn't support ARMv9. It supports ARMv8.1 (and some 8.2 and > 8.3) instructions. > You should figure out what the actual instruction is that needs support: > > disInstr(arm64): unhandled instruction 0xD65F0BFF > disInstr(arm64): 1101'0110 0101'1111 0000'1011 1111'1111 > ==1223== valgrind: Unrecognised instruction at address 0x4014be8. > ==1223== at 0x4014BE8: _dl_sysdep_parse_arguments (dl-sysdep.c:97) > > Probably easiest to disassemble ld.so and look what the instruction is at > that address/line. > > Also please try dropping -mcpu=neoverse-n2 from your glibc/ld.so build and > see if that works. Thanks for the reply. I believe I found the reason: the instruction causing the issue is "retaa", which is an instruction introduced in ARMv8.3-A. -- You are receiving this mail because: You are watching all bug changes.
