bug#34053: [PATCH] grep: fix slow for multiple word matching

2019-12-19 Thread Jim Meyering
On Thu, Dec 19, 2019 at 7:06 AM Norihiro Tanaka wrote: > On Wed, 18 Dec 2019 18:55:01 -0800 > Jim Meyering wrote: ... > > I have revised the wording in the commit message. Please ACK that. The > > only other change was in formatting, to split a line that went one > > byte past the 80-column maxim

bug#34053: [PATCH] grep: fix slow for multiple word matching

2019-12-19 Thread Norihiro Tanaka
On Wed, 18 Dec 2019 18:55:01 -0800 Jim Meyering wrote: > On Tue, Nov 26, 2019 at 2:38 PM Norihiro Tanaka wrote: > > On Sun, 13 Jan 2019 08:45:47 +0900 > > Norihiro Tanaka wrote: > > > grep uses KWset matcher for multiple word matching. It is very slow when > > > most of the parts matched to

bug#34053: [PATCH] grep: fix slow for multiple word matching

2019-12-18 Thread Jim Meyering
On Tue, Nov 26, 2019 at 2:38 PM Norihiro Tanaka wrote: > On Sun, 13 Jan 2019 08:45:47 +0900 > Norihiro Tanaka wrote: > > grep uses KWset matcher for multiple word matching. It is very slow when > > most of the parts matched to a pattern are not words. So, if a part firstly > > matched to patter

bug#34053: [PATCH] grep: fix slow for multiple word matching

2019-11-26 Thread Norihiro Tanaka
On Sun, 13 Jan 2019 08:45:47 +0900 Norihiro Tanaka wrote: > Hi, > > grep uses KWset matcher for multiple word matching. It is very slow when > most of the parts matched to a pattern are not words. So, if a part firstly > matched to pattern is not a word, use the grep matcher to match for its

bug#34053: [PATCH] grep: fix slow for multiple word matching

2019-01-12 Thread Norihiro Tanaka
Hi, grep uses KWset matcher for multiple word matching. It is very slow when most of the parts matched to a pattern are not words. So, if a part firstly matched to pattern is not a word, use the grep matcher to match for its line. By the way, if START_PTR is set, grep matcher uses regex matcher