https://bugs.kde.org/show_bug.cgi?id=476465
--- Comment #8 from Romain Geissler ---
Hi,
On this patch implementing only LDAPR, is it going to be pushed in the repo or
we are waiting for a patch implementing all 3 variants ?
Cheers,
Romain
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=476465
--- Comment #7 from Arne Juul ---
>From the ARM docs all the still-missing instructions are only available with
extra feature flags FEAT_LRCPC2 or FEAT_LRCPC3, so they are probably not as
important. Someone familiar with how the "normal" load/store
https://bugs.kde.org/show_bug.cgi?id=476465
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=476465
--- Comment #5 from Arne Juul ---
on RHEL8 (or almalinux 8.9 in my case) this is easily triggered by installing
gcc-toolset-13 and compiling this C++ program:
#include
const char * my_getenv_once() {
static const char * value = getenv("MYVALUE");
https://bugs.kde.org/show_bug.cgi?id=476465
--- Comment #4 from Arne Juul ---
after upgrading to GCC 13 we're seeing that the compiler generates LDAPR
instructions
for simple code when "RCpc" extension is enabled, as described here:
https://bugs.kde.org/show_bug.cgi?id=476465
Arne Juul changed:
What|Removed |Added
CC||ar...@vespa.ai
--- Comment #3 from Arne Juul ---
https://bugs.kde.org/show_bug.cgi?id=476465
Romain Geissler changed:
What|Removed |Added
CC||romain.geiss...@amadeus.com
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=476465
--- Comment #1 from landfillbab...@gmail.com ---
i should have set the severity higher since it renders it unusable for
dynamically linked binaries on my device
--
You are receiving this mail because:
You are watching all bug changes.
