I am sorry I forgot to reply. Philip guess was right, JIT can only use
64K machine stack, and itcannot compile the pattern if it runs out of
it. The exact rules are not documented since they maychange any time
when new optimizations are introduced (e.g. a capturing bracket may use
2 or 3mac
Hi,
I am sorry I forgot to reply. Philip guess was right, JIT can only use 64K
machine stack, and it cannot compile the pattern if it runs out of it. The
exact rules are not documented since they may change any time when new
optimizations are introduced (e.g. a capturing bracket may use 2 or 3
On 2015-10-25 17:53, ph10 wrote:
On Tue, 20 Oct 2015, ND wrote:
This pattern is 8426 times repeated '.*a'
> Why there is no '(JIT)' in answer. Why JIT don't work for this pattern?
I'm guessing, but I suspect the pattern is just too big. If you run it
under pcretest with the -i option you get:
On Tue, 20 Oct 2015, ND wrote:
> This pattern is 8426 times repeated '.*a'
> Why there is no '(JIT)' in answer. Why JIT don't work for this pattern?
I'm guessing, but I suspect the pattern is just too big. If you run it
under pcretest with the -i option you get:
Capturing subpattern count = 0
O
https://bugs.exim.org/show_bug.cgi?id=1705
--- Comment #4 from Philip Hazel ---
You are right. There is no way to exclude \C from PCRE1, either at build time
or at pcre_compile() time.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lis
https://bugs.exim.org/show_bug.cgi?id=1704
Philip Hazel changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.exim.org/show_bug.cgi?id=1703
Philip Hazel changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
