New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hyperscan: replace with vectorscan
#310772
Comments
In my experience Vectorscan is binary compatible with Hyperscan's current version, so switching shouldn't be a problem. Although adding ARM support to software built on top of it may require some fine tuning of CMake flags to work. On x86, Vectorscan will have the same performance characteristics as well. I have no experience with the Chimera module though. On the other hand I don't know if we need to be proactive about this. Existing versions of Hyperscan package will continue to work. So at least there is no time pressure. |
Relevant fedora issue: https://bugzilla.redhat.com/show_bug.cgi?id=2263601 Debian has packages for hyperscan (since at least debian 10) and vectorscan (since debian 12), but they currently only have packages depending on hyperscan and nothing depending on vectorscan. Reverse dependencies for libhyperscan5 and libvectorscan5 in debian:sid
|
Note that we're talking about an imperative FHS distro here; if the so names are the same, one package could simply be substituted with the other as an alternate implementation.
|
Issue description
Apparently, the great minds at Intel felt the need to turn a regex library proprietary: https://www.phoronix.com/news/Intel-Hyperscan-Now-Proprietary
Shall we replace it with
vectorscan
(already packaged) like Fedora intends to? It claims to be API-compatible, is committed to FOSS and has cross-platform support (ARM for instance).Leveraging this could also make some packages compatible cross-platform and/or enable hyperscan configuration for more platforms.
cc @avnik @fpletz @globin @nlewo @tnias @vlaci @0x4A6F @fabaff @magenbluten (maintainers of hyperscan/vectorscan and dependant packages)
The text was updated successfully, but these errors were encountered: