https://bugs.kde.org/show_bug.cgi?id=496972
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=496972
--- Comment #6 from Paul Floyd ---
No the i386 errors are unrelated. It's a bug in sljit (the jitter used by
pcre2). This patch fixes it:
https://github.com/zherczeg/sljit/commit/db3ca5014f0ae524785be05f071addc45a3442e0
If I correctly initialize 'info
https://bugs.kde.org/show_bug.cgi?id=496972
--- Comment #5 from Paul Floyd ---
I don't know if the i386 issue is the same thing.
The code is doing a 'cpuid' and then checking what is in eax. I can't see
anything wrong particularly. The pcre2 code looks similar to
none/tests/x86/cpuid and I see t
https://bugs.kde.org/show_bug.cgi?id=496972
--- Comment #4 from Paul Floyd ---
On FreeBSD i386
==33163== Conditional jump or move depends on uninitialised value(s)
==33163==at 0xEB46A34: get_cpu_features (sljitNativeX86_common.c:512)
==33163==by 0xEB46978: init_compiler (sljitNativeX86_c
https://bugs.kde.org/show_bug.cgi?id=496972
--- Comment #3 from Paul Floyd ---
Started with arm (Raspberry Pi OS). No problem there. (Don't know if pcre2 uses
jitting on that platform).
No problem on arm64 either (Ubuntu and FreeBSD).
So just amd64.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=496972
Paul Floyd changed:
What|Removed |Added
OS|FreeBSD |All
Platform|FreeBSD Ports
