You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of digging into this issue I looked to see how this may be broken on other distributions, and noticed that debian takes a different approach, instead of using auto, they do this:
#enable JIT only on architectures that support it (see pcre2jit.3)
ifneq ($(filter amd64 armel armhf arm64 i386 mips mipsel mips64el powerpc ppc64 ppc64el riscv64 s390x, $(DEB_HOST_ARCH)),)
deb_maint_conf_args +=--enable-jit
else
deb_maint_conf_args +=--disable-jit
endif
So I'm not sure if the preferred approach here would be to include the upstream patch, or use the more explicit --enable-jit option on supported platforms.
Describe the bug
A bug in pcre2 configure scripts cause the JIT not to be enabled. This makes apps that use pcre2 heavily, like suricata, extremely slow.
Steps To Reproduce
Steps to reproduce the behavior:
or
Expected behavior
JIT should be enabled
Additional context
This was fixed upstream 6 days ago:
PCRE2Project/pcre2@ab7f871
As part of digging into this issue I looked to see how this may be broken on other distributions, and noticed that debian takes a different approach, instead of using
auto
, they do this:So I'm not sure if the preferred approach here would be to include the upstream patch, or use the more explicit
--enable-jit
option on supported platforms.Notify maintainers
@ttuegel
Add a 👍 reaction to issues you find important.
The text was updated successfully, but these errors were encountered: