https://bugs.kde.org/show_bug.cgi?id=372794
--- Comment #7 from Claus Strasburger ---
Indeed, my tests are happy.
You guys are awesome! Thanks for all the hard work.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372794
--- Comment #6 from Julian Seward ---
> all the instructions that "gcc-5.4 -mfpu=neon-fp-armv8".
+= "generates."
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372794
--- Comment #5 from Julian Seward ---
(In reply to Claus Strasburger from comment #4)
> more -- this one is 0xFEBB0B40, VRINTM.f64), in code generated with
> -mcpu=cortex-a53 -mfpu=neon-fp-armv8 (for the Raspberry Pi 3, gcc 4.9.2)
>
> Should I open new
https://bugs.kde.org/show_bug.cgi?id=372794
--- Comment #4 from Claus Strasburger ---
Thanks! I can verify that gets me past the OpenSSL setup.
I'm finding another unhandled instruction (and I'm guessing there will be more
-- this one is 0xFEBB0B40, VRINTM.f64), in code generated with
-mcpu=corte
https://bugs.kde.org/show_bug.cgi?id=372794
Julian Seward changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=372794
--- Comment #2 from Claus Strasburger ---
Okay, I used LD_DEBUG=files to subtract the base address of libcrypto, and got
414b0 (x->). which seems to be the return of OPENSSL_cpuid_setup (??)
414a4: ebfffa93bl 3fef8 <__sigsetjmp@plt
https://bugs.kde.org/show_bug.cgi?id=372794
--- Comment #1 from Julian Seward ---
Ach, the logic there that verifies whether the instruction decode is
valid, is wrong. Try this:
change
// Paranoia ..
vassert(szBlg2 <= 3);
if (szBlg2 < 3) { vassert(tt2 == 16/*invalid*/); }
https://bugs.kde.org/show_bug.cgi?id=372794
Claus Strasburger changed:
What|Removed |Added
CC||c+...@cfs.im
--
You are receiving this mai
