[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gawk] 4.1.3->4.1.4 = Linux-libre's deblob-check grows huge and

From: Andrew J. Schorr
Subject: Re: [bug-gawk] 4.1.3->4.1.4 = Linux-libre's deblob-check grows huge and takes forever
Date: Thu, 13 Jul 2017 22:12:03 -0400
User-agent: Mutt/1.5.21 (2010-09-15)

On Thu, Jul 13, 2017 at 09:17:23PM -0400, Andrew J. Schorr wrote:
> I'm double-checking, but the "git bisect" output says:
> 92ec6835548d3612bd8f0e6a2b05adf4afb1c581 is the first bad commit
> commit 92ec6835548d3612bd8f0e6a2b05adf4afb1c581
> Author: Arnold D. Robbins <address@hidden>
> Date:   Sun Jul 24 21:44:27 2016 +0300
>     Use dfa even in multibyte locales.
> :100644 100644 54bd8682476371039888beac851abc40b34b843d 
> ddf4469ae5a19bc6b0524a5e2aa5ad6d277f0213 M      ChangeLog
> :100644 100644 0a156ffc3912822b09dfcf5877a6717f81fe5df5 
> 5049bca6c369dc3b473e5e678af120af20337391 M      re.c

And yes, the attached patch seems to fix the performance regression.
But I don't understand the deeper issues here about why this change was
made in the first place. I imagine that there are some cases where this
was helping performance...


Attachment: research.patch
Description: Text document

reply via email to

[Prev in Thread] Current Thread [Next in Thread]