Closed tekkenly closed 2 years ago
hi @tekkenly armv7 support is still not decided, I have enough armv7 hardware here so it's possible it will happen, but at the moment focus is on armv8 hardware.
You can temporarily compile and use x86 source code on armv7 through sse2neon (https://github.com/DLTcollab/sse2neon), and all test cases have passed successfully on my android device. It should be noted that the thumb instruction should be turned off, otherwise it will cause SIGBUS
I will not add yet another emulation library as a dependency to Vectorscan, Arm support is already included anyway. Arm 32-bit support is probably not going to happen soon, but it's on the horizon. It will however stay on Linux/arm and not Android.
Of course, compiling via sse2neon is only a temporary solution until vectorscan supports armv7. In fact, on the armv7 platform, it seems that the char of all platforms is an unsigned type, the only difference between android and pc is that the char of arm64 is also an unsigned type
if it's only that difference, it's makes it easier to include the change, but still it will be an unsupported platform, we do not have the resources to support Android as well.
@tekkenly we have decided we will not support add support for armv7 and Android to Vectorscan, we would accept PRs that do not break support on other platforms and don't increase maintainance burden, or otherwise we would discuss how this effort could be funded. But for the time being, I'm afraid this will have to be closed as wontfix.
I'm trying to build using armv7 gcc, found these errors. looks like some api are only available under armv8. Is it possible to make them armv7 compatible?