Robbie Williamson

> Hi, we build regression models for all Raspberry Pi devices ARM processors we have (RPi zero to 4) with a very small margin of error. We'll be publishing the...

Support submitted in this PR: https://github.com/intel/hyperscan/pull/287

FYI, we have been informed that the project maintainers have >"no plan to give multi-arch support for Hyperscan" and will >"keep Hyperscan as x86 only and deliver continuous designs and...

Arm has invested in adding aarch64 support with x86-specific code abstracted away and arch specific code put into separate headers in src/util/arch/. This way, maintaining arch-specific code of hyperscan and/or...

aarch64 support exists here: https://github.com/VectorCamp/vectorscan

> > > @daveMmd On native x86 processors with AVX (for example) the usage of the SIMD Everywhere header-only library is optimized out by the compiler into the existing direct...

@Yikun I believe the answer is still the same from last year (https://github.com/intel/hyperscan/issues/197#issuecomment-551367396). I am curious, what is your interest in having aarch64 support for hyperscan? If there is enough...

FYI, there is an Arm sponsored effort (see below) now to port and optimize hyperscan for Arm. The work as only just begun, but the end goal is to work...

For those interested, the first PR has been submitted that separates the architecture specific code to pave the way for adding aarch64 support....and any other future architectural specific code. https://github.com/intel/hyperscan/pull/272

FYI - aarch64 port has been completed here: - https://github.com/VectorCamp/hyperscan/tree/feature/add-arm-support with further NEON SIMD optimizations to come. PR will be submitted soon.