[Bug 1029190] New: Support for package variants according to the evaluation of bigger regular expressions
http://bugzilla.suse.com/show_bug.cgi?id=1029190 Bug ID: 1029190 Summary: Support for package variants according to the evaluation of bigger regular expressions Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: All Status: NEW Severity: Enhancement Priority: P5 - None Component: Development Assignee: bnc-team-screening@forge.provo.novell.com Reporter: Markus.Elfring@web.de QA Contact: qa-bugs@suse.de CC: astieger@suse.com Found By: --- Blocker: --- I noticed that the parameter “--with-link-size=2” is used so far in a package specification. https://build.opensuse.org/package/view_file/openSUSE:Factory/pcre2/pcre2.sp... This setting limits the size of regular expressions. I would like to work with bigger search patterns occasionally. So I suggest to generate also variants for this software with an internal link size of 3 (and 4) for the data processing with 8 and 16 bit characters. See also: Selection of system properties for the regular expressions engine at run time https://bugs.exim.org/show_bug.cgi?id=1922 By the way: How do you think about to use the specifications “LDFLAGS“ und “%{?_smp_mflags}“ as parameters for the script “%configure“ there? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1029190
Andreas Stieger
http://bugzilla.suse.com/show_bug.cgi?id=1029190
http://bugzilla.suse.com/show_bug.cgi?id=1029190#c1
Andreas Stieger
In the 8-bit library, the default maximum compiled pattern size is around 64K bytes. You can increase this by adding --with-link-size=3 to the "configure" command. PCRE2 then uses three bytes instead of two for offsets to different parts of the compiled pattern. In the 16-bit library, --with-link-size=3 is the same as --with-link-size=4, which (in both libraries) uses four-byte offsets. Increasing the internal link size reduces performance in the 8-bit and 16-bit libraries. In the 32-bit library, the link size setting is ignored, as 4-byte offsets are always used.
So it is a performance trade-off. Which application needs patterns in excess of 64k please? What prevents you from linking against the 32 bit library in the first place? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1029190
http://bugzilla.suse.com/show_bug.cgi?id=1029190#c2
Markus Elfring
So it is a performance trade-off.
Yes. - I am looking for another configuration variant because of this detail when I am building this software from the source files not only for myself.
Which application needs patterns in excess of 64k please?
A bit of background can be also found in my bug report “Advanced data processing for an alternation with a lot of key words”. https://bugs.exim.org/show_bug.cgi?id=1916
What prevents you from linking against the 32 bit library in the first place?
Nothing directly. - But there are further constraints to consider for modules in other programming languages if you would like to follow a change request like “Support for PCRE2”. https://github.com/mmottl/pcre-ocaml/issues/10 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1029190
https://bugzilla.suse.com/show_bug.cgi?id=1029190#c14
Jason Sikes
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com