https://bugs.kde.org/show_bug.cgi?id=476465
--- Comment #5 from Arne Juul <ar...@vespa.ai> ---
on RHEL8 (or almalinux 8.9 in my case) this is easily triggered by installing
gcc-toolset-13 and compiling this C++ program:
#include <stdlib.h>
const char * my_getenv_once() {
static const char * value = getenv("MYVALUE");
return value;
}
int main(int argc, char **argv) {
return (my_getenv_once() ? 0 : 1);
}
$ rpm -q gcc-toolset-13-gcc-c++
gcc-toolset-13-gcc-c++-13.1.1-4.3.el8.aarch64
$ /opt/rh/gcc-toolset-13/root/usr/bin/c++ -g -O2 -march=armv8.2-a+rcpc
mytest.cpp -o mytest
$ /usr/bin/valgrind ./mytest
==210903== Memcheck, a memory error detector
==210903== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==210903== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==210903== Command: ./mytest
==210903==
ARM64 front end: load_store
disInstr(arm64): unhandled instruction 0xF8BFC260
disInstr(arm64): 1111'1000 1011'1111 1100'0010 0110'0000
==210903== valgrind: Unrecognised instruction at address 0x4101e4.
==210903== at 0x4101E4: my_getenv_once() (myfun.cpp:3)
==210903== by 0x4100AB: main (myfun.cpp:7)
--
You are receiving this mail because:
You are watching all bug changes.
