Opened 5 years ago

Closed 5 years ago

#4393 closed task (fixed)


Reported by: Bruce Dubbs Owned by: Douglas R. Reno
Priority: normal Milestone: 8.4
Component: Book Version: SVN
Severity: normal Keywords:


New minor version.

Change History (4)

comment:1 by Bruce Dubbs, 5 years ago


  • Noteworthy changes in release 3.2 (2018-12-20) [stable]

Changes in behavior

The --files-without-match (-L) option now causes grep to succeed when a file is listed, instead of when a line is selected. This resembles what git-grep does.

Bug fixes

The --recursive (-r) option no longer fails on MS-Windows. [bug introduced in grep 2.11]


An over-30x performance improvement when many 'or'd expressions share a common prefix, thanks to improvements in gnulib's dfa.c, by Norihiro Tanaka. See gnulib commits v0.1-2110-ge648401be, v0.1-2111-g4299106ce, v0.1-2117-g617a60974

An additional 3-23% speed-up when searching large files, via increased initial buffer size.

grep now diagnoses stack overflow. Before grep-2.6, the included regexp code would detect it. Since 2.6, grep defaulted to using glibc's regexp, which lost that capability.

comment:2 by Bruce Dubbs, 5 years ago

Summary: grep-3.2grep-3.3
  • Noteworthy changes in release 3.3 (2018-12-20) [stable]

Bug fixes

Some uses of \b in the C locale and with the DFA matcher would fail, e.g., the following would print nothing (it should print the input line):

echo 123-x|LC_ALL=C grep '.\bx'

Using a multibyte locale, using certain regexp constructs (some ranges, backreferences), or forcing use of the PCRE matcher via --perl-regexp (-P) would avoid the bug. [bug introduced in grep 2.3]

comment:3 by Douglas R. Reno, 5 years ago

Owner: changed from lfs-book to Douglas R. Reno
Status: newassigned

comment:4 by Douglas R. Reno, 5 years ago

Resolution: fixed
Status: assignedclosed

Fixed at r11495

Note: See TracTickets for help on using tickets.