Closed wagnerch closed 2 years ago
As far as I can tell, there's a run-time test for whether to use a NEON implementation of a function or not, so readelf will be a bit misleading in such cases. Running the binaries from libdeflate-tools seems to work on a pi zero.
Chromium is a separate issue, it's build specifically for armv7. There are some patches needed to armv6 support and I can take a look at bringing those back when there's more time. Given how poorly it runs with limited RAM, it might not be worth the effort.
libgcrypt seems to be used by a lot of programs. If it didn't work on armv6, I think there is no way it wouldn't have been spotted earlier, so I'm certain it's also using run-time cpu detection.
Raspbian packages go through an armv7 contamination check and AIUI packages need to be checked and whitelisted before they can end up in their repo.
@XECDesign Yeah, your right I went through the implementation in both libraries and they do appear to do this at runtime. libdeflate is using attributes to call out armv8+crc versions of crc32, but it compiles 2 functions and selects them at runtime. So I think both are false flags, apologies for the distraction.
No worries, it doesn't hurt to be cautious about these things.
This doesn't affect me since I have Pi4's, but thought I would pass it on if you guys want to keep supporting the older devices. This is likely the cause of the Chromium issues on Pi0 & Pi1.
libgcrypt20 is a dependency for Chromium.