[pcre-dev] [Bug 2030] Exact match mode

https://bugs.exim.org/show_bug.cgi?id=2030 Philip Hazel changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

Re: [pcre-dev] [Bug 2030] Exact match mode

In case of anchored matches, there is no need to scan the input for possible starting characters. Several other simplifications (optimizations) are possible as well. So the generated code is different. You can compile the pattern twice though and use the appropriate one. Regards, Zoltan

[pcre-dev] [Bug 2030] Exact match mode

https://bugs.exim.org/show_bug.cgi?id=2030 --- Comment #4 from Giuseppe D'Angelo --- Many thanks for the insight :) Out of curiosity what is that makes an anchored match NOT use the JIT when passed at match time rather than compile time? -- You are receiving this mail

[pcre-dev] [Bug 2030] Exact match mode

https://bugs.exim.org/show_bug.cgi?id=2030 --- Comment #3 from Philip Hazel --- No, you are right. I had thought about this some more myself, and came to the same conclusion. I will add a new option (called PCRE2_ENDANCHORED unless I can think of something better) that

[pcre-dev] [Bug 2030] Exact match mode

https://bugs.exim.org/show_bug.cgi?id=2030 --- Comment #2 from Giuseppe D'Angelo --- Hi, no need to hurry, it's just a suggestion... Regarding your approach of anchoring the match: the problem I see with it is that it may simply fail depending on the nature of the pattern

[pcre-dev] [Bug 2030] Exact match mode

https://bugs.exim.org/show_bug.cgi?id=2030 --- Comment #1 from Philip Hazel --- Thank you for your suggestion. Unfortunately, it is too late for 10.23, for which a Release Candidate is currently available for testing. However, I'm not sure if the feature you ask for is