GNU bug report logs - #21700
new snapshot available: grep-2.21.78-7da30

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 21700 in the body.
You can then email your comments to 21700 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: bug-grep <at> gnu.org
Cc: TP coordinator <coordinator <at> translationproject.org>,
 platform-testers <at> gnu.org
Subject: new snapshot available: grep-2.21.78-7da30
Date: Sat, 17 Oct 2015 22:26:07 -0700

I want to release grep-2.22 in just a couple of days.
This release is motivated largely by the discovery that there has
been a bug in versions 2.19, 2.20 and 2.21 that made grep mistakenly
print some lines that did not match. However, there have also been
several other bug fixes and notable performance improvements.

Any testing you can do would be most welcome.
Feedback, even the report that you "built and passed tests on XYZ,"
would be appreciated.

grep snapshot:
  http://meyering.net/grep/grep-ss.tar.xz      1.3 MB
  http://meyering.net/grep/grep-ss.tar.xz.sig
  http://meyering.net/grep/grep-2.21.78-7da30.tar.xz

Here is the current summary from NEWS.  More detail after that.
=====================================

** Improvements

  When building grep, 'configure' now uses PCRE's pkg-config module for
  configuration information, rather than attempting to guess it by hand.

** Bug fixes

  A DFA matcher bug made this command mistakenly print its input line:
    echo axb | grep -E '^x|x$'
  Likewise for this equivalent command:
    echo axb | grep -e '^x' -e 'x$'
  [bug introduced in grep-2.19 ]

  grep no longer reads from uninitialized memory or from beyond the end
  of the heap-allocated input buffer.  This fix addressed CVE-2015-1345.

  With -z, '.' and '[^x]' in a pattern now consistently match newline.
  Previously, they sometimes matched newline, and sometimes did not.
  [bug introduced in grep-2.4]

  When the JIT stack is exhausted, grep -P now grows the stack rather
  than reporting an internal PCRE error.

  'grep -D skip PATTERN FILE' no longer hangs if FILE is a fifo.
  [bug introduced in grep-2.12]

  --exclude and related options are now matched against entire
  command-line arguments, not against command-line components.
  [bug introduced in grep-2.6]

  Performance has improved for patterns containing very long strings,
  and for grep -Fw in unibyte locales.
=====================================

Changes in grep since v2.21:

Jim Meyering (27):
      maint: post-release administrivia
      maint: correct for four Author: name misspellings
      maint: fix a new "make syntax-check" failure
      maint: update copyright year ranges to include 2015
      gnulib: update to latest
      grep: avoid false-positive UMR
      tests: add support for ASAN memory poisoning
      maint: convert "goto" to "continue" and remove now-spurious label
      maint: reference CVE-2015-1345 from NEWS
      maint: use ASAN-poisoning more carefully
      maint: sort test names in tests/Makefile.am and add syntax-check rule
      maint: reword a diagnostic not to trigger leading capital check
      maint: update bootstrap from gnulib
      maint: alphabetize anonymous enum member names
      maint: unify three argv-processing calls
      tests/case-fold-backref: factor test
      maint: dfa: used unsigned types where appropriate
      tests: avoid FS-dependent false-positive failure
      tests: fix mis-applied patch.
      tests: add a test for the performance fix
      tests: new function to measure elapsed user time
      tests: long-pattern-perf: measure user time, not elapsed
      tests: mb-non-UTF8-performance: use new function
      doc: NEWS: mention a bug fix
      maint: use single quote rather than UTF-8 multi-byte version
      build: avoid spurious bootstrap failure involving pkg.m4
      gnulib: update to latest; also bootstrap and tests/init.sh

Norihiro Tanaka (17):
      dfa: avoid invalid match or infinite loop in unused matching mode
      dfa: simplify dfaexec
      build: avoid build failure with --enable-gcc-warnings and no PCRE
      dfa: make find_pred return NULL for an invalid predicate
      dfa: build struct dfamust on demand
      dfa: speed up handling of long pattern
      tests: sjis-mb: accept two more locales
      dfa: DEBUG: print detail of DFA states
      dfa: avoid execution for a pattern including an unsupported expression
      dfa: remove word delimiter support for multibyte locales
      dfa: remove unused multibyte support
      grep: remove fgrep code for case insensitive match
      grep: avoid use of uninitialized variable
      dfa: fix off-by-one error
      dfa: fix bug in alternate of sub-patterns that differ only in constraints
      grep: improve performance of grep -Fw
      grep: use grep matcher for grep -Fw when unibyte

Paul Eggert (32):
      tests: port fmbtest to CentOS 6 and earlier
      doc: document binary-data heuristic better
      Grow the JIT stack if it becomes exhausted
      Cover the non-INSTALL case
      doc: clarify how -a matches
      doc: give a script wrapper example
      egrep, fgrep: just use what's in PATH
      grep: output "." file name in diagnostic
      build: use pkg-config (if available) to configure libpcre
      build: remove typo and don't bother with /usr/include/pcre
      build: improve pkg-config doc and error handling
      test: tighten tests for bracket exprs
      grep: minor tweaks
      grep: don't hang on command-line fifo if -D skip
      grep: don't mishandle left context in -P
      grep: simplify print_line_middle slightly
      grep: -z '.' now consistently matches newline
      grep: -z '[^x]' now consistently matches newline
      dfa: '.' and '[^x]' now consistently match newline
      build: update gnulib submodule to latest
      maint: ignore gendocs_template_min
      grep: use recent gnulib syntax bits
      tests: fix $? typo in null-byte
      grep: fix bug with --exclude-dir and command line
      dfa: optimize [x-x]
      build: update gnulib submodule to latest
      Add test for pop_fail_stack bug
      tests: add test case for Bug#21670
      dfa: make the executable a bit smaller
      grep: use memchr/memrchar
      grep: simplify previous change
      maint: add news item

Santiago Ruano Rincón (1):
      doc: document grep-2.11 change in behavior of -r, --recursive

Yuliy Pisetsky (1):
      grep -F: fix a heap buffer (read) overrun


Changes in gnulib since v2.21:

* gnulib 46d015f...37c054a (333):
  > maint.mk: _gl_TS_function_match: fix "extern" name extracting regexp
  > maint.mk: sc_tight_scope: factor and support OS X
  > ChangeLog: fix typo: s/cound/count/
  > safe-alloc-tests: fix typo in license header
  > copy-file: fix mem leak in error case
  > localename: control langinfo.h inclusion
  > update from texinfo
  > binary-io, math, pthread, sys_socket, u64, unistd: port to strict C
  > accept4-tests: fix to avoid non portable flags
  > update from texinfo
  > update from texinfo
  > gnulib-tool: fix tests of 'extensions' module
  > unicase/locale-language: fix typo in utf-8 cookie
  > autoupdate
  > xalloc: do not worry about GCC 5 warning on 32 bit
  > xalloc: avoid GCC 5.1 warning on 32 bit
  > uniname/uniname-tests: avoid compiler warnings
  > autoupdate
  > mountlist: clean up of variable duplication
  > c-ctype: do not worry about EBCDIC + char signed
  > c-ctype: port better to z/OS EBCDIC
  > gnulib-common.m4: fix gl_PROG_AR_RANLIB/AM_PROG_AR clash
  > sockets: MS Windows initalization fixes
  > gc: fix detection of installed libgcrypt version
  > c-ctype: rewrite to use inline functions
  > fnmatch: add one more coding cookie
  > maint: add coding cookies to non-ASCII sources
  > gitlog-to-changelog: trim only trailing whitespaces
  > Test that c_iscntrl agrees with iscntrl, etc.
  > c-ctype: improve c_isascii testing
  > Fix ChangeLog typo
  > savewd: remove SAVEWD_CHDIR_READABLE
  > Update ChangeLog to match previous patch.
  > c-ctype: support EBCDIC-style c_isascii
  > c-ctype: assume EBCDIC 1047 for c_iscntrl
  > * modules/c-ctype (Depends-on): Add verify.
  > c-ctype: port better to EBCDIC
  > nanosleep: fix return code for interrupted replacement
  > autoupdate
  > Diagnose ERE '()|\1'
  > Revert previous patch, as it did not fix the bug after all.
  > regex: fix dangling-backreference bug
  > regex: merge patches from libc
  > autoupdate
  > autoupdate
  > autoupdate
  > autoupdate
  > ceill: detect buggy OpenBSD implementation
  > mountlist: add me_mntroot field on Linux machines
  > doc: Describe to use multiple instances of gnulib
  > autoupdate
  > autoupdate
  > base32: mark function as __attribute__ const
  > autoupdate
  > autoupdate
  > gnulib-tool: don't transform binary files with sed
  > autoupdate
  > autoupdate
  > autoupdate
  > autoupdate
  > gperf: respect silent rules
  > Improve port of stdalign to C++11
  > pmccabe2html: fix gawk regex escaping
  > update from texinfo
  > time_rz: port to pedantic memcpy
  > autoupdate
  > time_rz: port better to MinGW
  > time: port __need_time_t to MinGW
  > strftime: fix newly-introduced bug on Solaris
  > test-strftime: test for Solaris bug
  > time_rz: port to Solaris etc.
  > time_rz: now LGPL
  > time_rz: make a constant 'const'
  > time_rz: fix off-by-one typo
  > autoupdate
  > fprintftime, strftime: use timezone_t args
  > time_rz: new module
  > flexmember: license is now unlimited
  > autoupdate
  > maint: update copyright paper procedures
  > autoupdate
  > autoupdate
  > localename: fix link error on Illumos
  > unistr/uN-strtok-tests: avoid a trivial leak
  > acl-permissions: Document FreeBSD ACL_TYPE_NFS4 acls
  > acl-permissions: Fix on FreeBSD
  > file-has-acl, acl-permissions: fix some more HP-UX typos
  > file-has-acl, acl-permissions: fix HP-UX typos
  > regex: match current GNU grep behavior
  > set-permissions.c: adjust acl_from_mode's cpp guard
  > autoupdate
  > tests: restrict shells to those that support 'local'
  > fix mistakes in ChangeLog entries
  > unistr/uN-strtok: handle multibyte delimiters
  > update-copyright: fix test failure with perl >= 5.22
  > u{16,32}-strstr-tests: relax timeout condition
  > gnulib-common.m4: change the ARFLAGS default to 'cr'
  > update from texinfo
  > autoupdate
  > selinux-h: avoid double free after *getfilecon()
  > fix pty related tests issues on Windows
  > acl: fix definition of acl_from_mode on FreeBSD
  > readutmp: port to FreeBSD >= 9
  > mgetgroups: port to strict OS X
  > mgetgroups: fix port to strict OS X
  > linkat: fix invalid definition of LINKAT_SYMLINK_NOTSUP on OS X
  > mgetgroups: port to strict OS X
  > mountlist: avoid an unused-label warning on OS X
  > error.c: correct printf-style format: %d -> %u
  > fts: avoid reading beyond the heap allocation
  > savedir: avoid undefined behavior in qsort call
  > userspec: avoid undefined behavior in gettext call
  > update from texinfo
  > gitlog-to-changelog: improve gitmerge.el commits
  > wchar: fix MinGW compilation warnings
  > uniname/uniname-tests: use pristine data files
  > linked-list, linkedhash-list: avoid compiler warnings
  > libunistring: bump minimum version to 0.9.6
  > uniname/uniname: update to Unicode 8.0.0
  > * lib/gen-uni-tables.c: Style fixes.
  > libunistring: update to Unicode 8.0.0
  > gnu-web-doc-update: add --mirror to remove stale files
  > * lib/set-permissions.c: Spelling fix.
  > update from texinfo
  > acl-permissions: pacify -Wsuggest-attribute=const
  > fsync: document AIX misbehavior
  > acl-permissions: more porting to AIX
  > stdio: Don't redefine gets when using C++
  > acl-permissions: add a cast to port to older AIX
  > acl-permissions: port to older AIX, C89 HP-UX
  > update from texinfo
  > vasprintf-posix: avoid compiling vasnprintf where possible
  > file-has-acl: fix build on Mac OS X 10
  > prefix-gnulib-mk: remove no longer needed special case
  > acl: don't depend on the deprecated qacl module
  > gnulib-tool: concatenate lib_SOURCES to a single line
  > pthread_sigmask: discount system version if a simple macro
  > readlinkat: avoid OS X 10.10 trailing slash bug
  > acl-permissions: Fix build on Mac OS X and older AIX (Bug#20681)
  > acl-permissions: Fix build on Solaris and Cygwin
  > linkat: avoid OS X 10.10 trailing slash with symlink bug
  > unlinkat: handle ignoring of ".." on Darwin 14
  > qacl: split into qcopy-acl and qset-acl
  > gitlog-to-changelog: new option --ignore-line
  > qacl: Reimplement qset_acl and qcopy_acl (Bug#20666)
  > file-has-acl: Split feature tests again (Bug#20667)
  > string: fix build failure on BSD/OSX with FORTIFY_SOURCE
  > stdio: limit __gnu_printf__ witness to gcc 4.4+
  > error: use correct printf attributes on mingw
  > update from texinfo
  > inttypes: force correct mingw PRIdMAX even without <stdio.h>
  > stdio: fix probe on mingw under gcc 5.1
  > autoupdate
  > gitlog-to-changelog: parse "Tiny-change"
  > update from texinfo
  > doc: document glibc posix_fallocate() issues
  > gendocs.sh: document new htmlarg default
  > extern-inline: no need for workaround in GCC 5.1
  > update from texinfo
  > eealloc, pagealign_alloc, xalloc: avoid clang warnings
  > tests: pacify GCC 5.1's stricter printf checking
  > fts: port to GCC 5.1 with --enable-gcc-warnings
  > file-has-acl: port to CentOS 6
  > file-has-acl: always return false when ACLs aren't supported
  > gettext: propagate po/Makefile.in.in too
  > file-has-acl: new module, split from acl
  > manywarnings: add GCC 5.1 warnings
  > autoupdate
  > doc: update FDL template to match FDL examples.
  > lstat: fix cross-compilation 'ln -s' problem
  > gendocs.sh: default to a common CSS style sheet for HTML output
  > gnulib-tool: output bold attribute more portably
  > qacl: Simplify HP-UX acl_nontrivial check
  > acl: On Linux, check for acls without libacl
  > acl, qacl: split off shared functions into separate object file
  > git-version-gen: revert "detect untagged revisions"
  > tempname: avoid unused parameter warnings
  > git-version-gen: detect untagged revisions
  > fseeko: fix build failure on NetBSD >= 6
  > gitlog-to-changelog: port to MS-Windows
  > gendocs: new option --tex for texi2dvi options
  > sync gettext .m4 files from gettext
  > uniname/uniname-tests: fix failure due to alias
  > hash: remove deprecated hash_insert0 function
  > mountlist: remove dependency on libmount
  > stddef: port to pre-C11 GCC on x86
  > quotearg-simple-tests: add missing gl_FUNC_MMAP_ANON dependency
  > yesno: make EOL optional in ENABLE_NLS case also
  > fdopendir-tests: test it does not close its arg
  > gitlog-to-changelog: trim trailing white space
  > gitlog-to-changelog: new option --ignore-matching
  > fdopendir: port better to MinGW
  > fdopendir: fix typo in comment
  > error: document all entry points provided
  > autoupdate
  > autoupdate
  > autoupdate
  > vasnprintf: pacify clang 3.5.0
  > glob, etc.: port to MSVC v18 on MS-Windows 8.1
  > poll: port to MSVC v18 on MS-Windows 8.1
  > tests: support stderr verification with returns_()
  > passfd: avoid valgrind uninitalised data warning
  > uniwbrk/u32-wordbreaks-tests: fix copyright
  > dup2: doc and test for Android bug
  > Replace dup2() on Android
  > Android doesn't define RLIM_SAVED_*
  > autoupdate
  > vasnprintf-posix-tests: use consistent test
  > printf, isinf, etc.: noncanonical != NaN
  > fts: remove redundant close() (trivial)
  > getdtablesize: port better for Android
  > poll: fixes for large fds
  > fcntl: Fix cross compiling
  > dup2, fcntl: cross-compiler better for Android
  > getopt: give accurate ambiguity diagnostic on mem exhaustion
  > getopt: don't crash on memory exhaustion
  > tempname: allow compilation with C++ (trivial)
  > dup2, fcntl: port to AIX
  > getdtablesize, dup2, fcntl: port to Android
  > localename: Implement gl_locale_name_thread_unsafe for Android
  > More changelog fixes
  > fts: avoid crash when a cycle is added while traversing
  > uniname/uniname: support character alias
  > Fix ChangeLog botches in my recent commits
  > duplocale: Fix Android build of duplocale-tests
  > signal_h: Fix Android build
  > net_if: Handle content-free <net/if.h> system headers
  > linkat_nofollow: Add fallback case for cross compiling
  > euidaccess: Fix Android build
  > getugroups: Fix Android build
  > localename: Fix Android build
  > getdtablesize: Fix Android build
  > Assume unbroken ungetc() on Android
  > Fix FILE struct compatibility with Android API level >= 21
  > tests: avoid recent -Werror=unused-variable regression in test-locale
  > maint: various whitespace cleanups in tempname
  > tests: provide returns_() to simplify exit status checking
  > mountlist: only use libmount when specified
  > uniname/unimame-tests: don't link with -lunistring
  > fstrcmp: don't assume strlen < INT_MAX
  > diffseq: prefer ptrdiff_t to ssize_t
  > xalloc: fix typo that suppressed warnings
  > full-read: fix license notice typo
  > crypto/gc: fix a -Wswitch warning
  > autoupdate
  > update from texinfo
  > tempname: new try_tempname function
  > gnulib-tool: fix handling of patch(1) diagnostics
  > bootstrap: exit immediately upon gnulib-tool failure
  > symlinkat: include all required header files
  > update from texinfo
  > update from texinfo
  > update from texinfo
  > localename: support Solaris 12 and illumos
  > locale: fix tests on illumos
  > unictype: avoid undefined left-shift behavior
  > libunistring: bump version of unitypes dependants
  > unictype/category-none: fix link with libunistring
  > unitypes: fix build with installed libunistring
  > time: port to MinGW32 3.21
  > update-copyright: apply to self
  > libunistring: update to Unicode 7.0.0
  > libunistring: update to Unicode 6.3.0
  > libunistring: update to Unicode 6.2.0
  > libunistring: update to Unicode 6.1.0
  > uniwbrk/u32-wordbreaks-tests: add conformance test
  > uniwbrk: ignore Extended/Format characters at BOL
  > test-strstr.c: avoid a trivial leak
  > update-copyright: recognize groff's \(co marker
  > maint.mk: fix compatibility with OS X nm
  > localcharset: improve charset detection on OS/2
  > count-leading-zeros: use 64-bit intrinsics on 32-bit Windows
  > count-leading-zeros: fix pragma typos
  > autoupdate
  > count-leading-zeros: avoid 64-bit intrinsics on 32-bit Windows
  > uniname/uniname: update to Unicode 7.0.0
  > doc: update INSTALL from autoconf
  > stdio: fix use of PRIdMAX on modern mingw
  > Fix check for pthreads.h pollution on Mingw64
  > lib-symbol-versions: cache script check
  > maint: fix grammar nits in propername
  > gendocs: Update bug-report address and URLs to Gnulib's.
  > gendocs: Add 'doc/gendocs_template_min'.
  > gendocs: Change maintainer.
  > gendocs: copyright date and version fix
  > derived INSTALL
  > revert copyright updates in slaved files
  > version-etc: new year
  > autoupdate
  > autoupdate
  > xstrtol: ensure errno is reset
  > utimens: fix dependency typo
  > autoupdate
  > docs: mention why libgen.h is bad
  > autoupdate
  > assure: new module
  > autoupdate
  > stdalign: port better to HP compilers
  > stdalign: work around Apple GCC 4.0 bug
  > gendocs.sh and templates now maintained in gnulib
  > getcwd: fix test failure on OS X 10.9
  > parse-datetime: avoid a compiler warning with byacc
  > unicase/locale-language-tests: fix LOCALE_FR test
  > autoupdate
  > update from texinfo
  > stddef: support C11's max_align_t
  > unistd: fix iOS check conditional
  > posixtm: avoid compiler warning in a better way
  > relocatable: support UNIXROOT in relocate() on EMX
  > freopen: workaround freopen() on OS/2 kLIBC
  > get_shared_library_fullname: port to EMX
  > find_executable: port to EMX
  > sched: check struct sched_param in spawn.h as well
  > support GNU format printf and scanf on mingw
  > bootstrap: Allow perl modules in $buildreq
  > apply _GL_ATTRIBUTE_PURE to some inline functions
  > vasnprintf: fix potential incorrect errno
  > vasnprintf: fix potential use after free
  > autoupdate
  > filevercmp, posixtm: avoid compiler warnings with -O3
  > Fix LDBL80_WORDS macro on big endian platforms.
  > autoupdate
  > git-version-gen: do not print new line characters
  > gnulib-tool: recognize x:* as an absolute path
  > argp: avoid extraneous translation and mem leak with empty pre doc
  > autoupdate
  > doc: mention that _BSD_SOURCE is deprecated for _DEFAULT_SOURCE
  > uniname/uniname-tests: skip if system's libunistring is used
  > printf: fix configure check on big endian systems
  > pipe-filter-gi, pipe-filter-ii: port to AIX
  > gitlog-to-changelog: add --until
  > update from texinfo
  > extern-inline: update commentary about GCC bugs

Message #8 received at 21700 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: 21700 <at> debbugs.gnu.org
Cc: Jim Meyering <jim <at> meyering.net>
Subject: Re: bug#21700: new snapshot available: grep-2.21.78-7da30
Date: Sat, 17 Oct 2015 23:34:16 -0700

I ran into a problem with this release on Solaris 10 with Sun C 5.13:

  CC       fts.o
"fts.c", line 1915: warning: type of struct member "__b" can not be derived fro\
m structure with flexible array member
"fts.c", line 1915: warning: type of struct member "__b" can not be derived fro\
m structure with flexible array member

This is due to the use of Gnulib alignof to calculate the alignment of a struct 
with a flexible array member; the Gnulib implementation doesn't support this on 
C99 (it violates a C99 constraint).  I'll look into a workaround within fts.

I did manage a build on AIX with xlc; works OK.

Message #11 received at 21700 <at> debbugs.gnu.org (full text, mbox):

From: Aaron Davies <aaron.davies <at> gmail.com>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: "21700 <at> debbugs.gnu.org" <21700 <at> debbugs.gnu.org>
Subject: Re: bug#21700: new snapshot available: grep-2.21.78-7da30
Date: Sun, 18 Oct 2015 10:51:19 -0400

I ran into this trying to build current coreutils on Solaris with sun studio 11

the workaround I found was to use sun studio 12

Sent from my iPhone

> On Oct 18, 2015, at 2:34 AM, Paul Eggert <eggert <at> cs.ucla.edu> wrote:
> 
> I ran into a problem with this release on Solaris 10 with Sun C 5.13:
> 
>  CC       fts.o
> "fts.c", line 1915: warning: type of struct member "__b" can not be derived fro\
> m structure with flexible array member
> "fts.c", line 1915: warning: type of struct member "__b" can not be derived fro\
> m structure with flexible array member
> 
> This is due to the use of Gnulib alignof to calculate the alignment of a struct with a flexible array member; the Gnulib implementation doesn't support this on C99 (it violates a C99 constraint).  I'll look into a workaround within fts.
> 
> I did manage a build on AIX with xlc; works OK.
> 
> 
> 

Message #14 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Gary Johnson <garyjohn <at> spocom.com>
To: bug-grep <at> gnu.org
Subject: Re: bug#21700: new snapshot available: grep-2.21.78-7da30
Date: Sun, 18 Oct 2015 01:51:52 -0700

On 2015-10-17, Jim Meyering wrote:
> I want to release grep-2.22 in just a couple of days.
> This release is motivated largely by the discovery that there has
> been a bug in versions 2.19, 2.20 and 2.21 that made grep mistakenly
> print some lines that did not match. However, there have also been
> several other bug fixes and notable performance improvements.
> 
> Any testing you can do would be most welcome.
> Feedback, even the report that you "built and passed tests on XYZ,"
> would be appreciated.
> 
> grep snapshot:
>   http://meyering.net/grep/grep-ss.tar.xz      1.3 MB
>   http://meyering.net/grep/grep-ss.tar.xz.sig
>   http://meyering.net/grep/grep-2.21.78-7da30.tar.xz

I built the snapshot on two systems, a fairly old one running Ubuntu
10.04.4 and a newer one running an up-to-date Linux Mint 17.2.
'make check' reported the same two failures on both:

    XFAIL: backref-alt
    XFAIL: triple-backref

Regards,
Gary

Message #17 received at 21700 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Aaron Davies <aaron.davies <at> gmail.com>
Cc: Pádraig Brady <P <at> draigBrady.com>,
 Gnulib bugs <bug-gnulib <at> gnu.org>,
 "21700 <at> debbugs.gnu.org" <21700 <at> debbugs.gnu.org>
Subject: Re: bug#21700: new snapshot available: grep-2.21.78-7da30
Date: Sun, 18 Oct 2015 10:10:36 -0700

[Message part 1 (text/plain, inline)]

Aaron Davies wrote:
> I ran into this trying to build current coreutils on Solaris with sun studio 11
>
> the workaround I found was to use sun studio 12

I'm also using Sun Studio 12. That being said, I now see that I was using Sun C 
5.9 (Patch 124867-12 2009/11/22), which is the original Sun Studio 12. I earlier 
reported that I was using Sun C 5.13, i.e., Oracle Solaris Studio 12.4, but I 
was mistaken. Oracle's compiler versioning is complicated; see 
<http://www.oracle.com/technetwork/server-storage/solarisstudio/training/index-jsp-141991.html>.

I just now looked at the C11 standard, and it prohibits Pádraig's 2015-06-25 
change to fts.c that uses alignof on a structure with a flexible array member. 
And I now see that IBM's xlc compiler also complains about this. though I didn't 
notice this earlier.

Although the C11 prohibition is arbitrary and perhaps not even intended, it's in 
the standard, and we should fix fts.c to conform. I installed the attached patch 
into gnulib, and this will be merged into grep the next time we update its 
gnulib version. I can see one more gnulib fix that's also needed for grep, and 
plan to follow up shortly.

[0001-fts-port-to-C11-alignof.patch (text/plain, attachment)]

Message #20 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: bug-grep <at> gnu.org
Cc: 21700 <at> debbugs.gnu.org
Subject: Re: bug#21700: new snapshot available: grep-2.21.78-7da30
Date: Sun, 18 Oct 2015 14:41:42 -0700

> I built the snapshot on two systems, a fairly old one running Ubuntu
> 10.04.4 and a newer one running an up-to-date Linux Mint 17.2.
> 'make check' reported the same two failures on both:
>
>    XFAIL: backref-alt
>    XFAIL: triple-backref

Thanks for building and reporting.
Each of those "XFAIL"s indicates an expected failure, so that is the
expected test result, for now.

Message #26 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Gary Johnson <garyjohn <at> spocom.com>
To: bug-grep <at> gnu.org
Subject: Re: bug#21700: new snapshot available: grep-2.21.78-7da30
Date: Wed, 21 Oct 2015 13:09:14 -0700

On 2015-10-18, Jim Meyering wrote:
> > I built the snapshot on two systems, a fairly old one running Ubuntu
> > 10.04.4 and a newer one running an up-to-date Linux Mint 17.2.
> > 'make check' reported the same two failures on both:
> >
> >    XFAIL: backref-alt
> >    XFAIL: triple-backref
> 
> Thanks for building and reporting.
> Each of those "XFAIL"s indicates an expected failure, so that is the
> expected test result, for now.

OK, thanks.

I also built the snapshot successfully on a Fedora 17 system that I
use for real work.  I just ran a performance test, FWIW.  I searched
recursively in our source hierarchy of 6044 regular files and 1102
directories for a simple string.

    time grep -Rin mystring src > /dev/null

Here are the results, averaged over three trials each, not including
any slow times clearly due to updating caches.

            2.12    2.21    2.21.78-7da30
            -----   -----   -----
    real    18.0s   1.08s   2.36s
    user    17.8s   0.96s   2.24s
    sys     0.12s   0.11s   0.10s

Version 2.12 was /bin/grep.  The other two versions I built myself.

Regards,
Gary

Message #29 received at 21700 <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: bug-grep <at> gnu.org
Cc: 21700 <at> debbugs.gnu.org
Subject: Re: bug#21700: new snapshot available: grep-2.21.78-7da30
Date: Wed, 21 Oct 2015 14:37:35 -0700

On Wed, Oct 21, 2015 at 1:09 PM, Gary Johnson <garyjohn <at> spocom.com> wrote:
> On 2015-10-18, Jim Meyering wrote:
>> > I built the snapshot on two systems, a fairly old one running Ubuntu
>> > 10.04.4 and a newer one running an up-to-date Linux Mint 17.2.
>> > 'make check' reported the same two failures on both:
>> >
>> >    XFAIL: backref-alt
>> >    XFAIL: triple-backref
>>
>> Thanks for building and reporting.
>> Each of those "XFAIL"s indicates an expected failure, so that is the
>> expected test result, for now.
>
> OK, thanks.
>
> I also built the snapshot successfully on a Fedora 17 system that I
> use for real work.  I just ran a performance test, FWIW.  I searched
> recursively in our source hierarchy of 6044 regular files and 1102
> directories for a simple string.
>
>     time grep -Rin mystring src > /dev/null
>
> Here are the results, averaged over three trials each, not including
> any slow times clearly due to updating caches.
>
>             2.12    2.21    2.21.78-7da30
>             -----   -----   -----
>     real    18.0s   1.08s   2.36s
>     user    17.8s   0.96s   2.24s
>     sys     0.12s   0.11s   0.10s
>
> Version 2.12 was /bin/grep.  The other two versions I built myself.

Thank you for the timings. Next time, please include the following:
  - CPU type/speed
  - file system type (and SSD or spinning rust)
  - OS version
  - options with which you configured/built grep
  - your current locale

While you see a performance degradation going from 2.21 to the
first 2.22 release candidate, I see the opposite trend, albeit barely
measurable:

Searching the following hierarchies, I see a consistent 1% improvement
going from 2.21 to 2.22 on an Intel(R) Core(TM) i7-4770S CPU @ 3.10GHz.
The files I searched were on an ext4 file system residing on an SSD
(OCZ-VERTEX3).
This system is using fedora rawhide.

$ find [a-g]* -type f|wc -l
335065
$ find [a-g]* -type d|wc -l
9667
$ du -shc [a-g]*
25M     autoconf
125M    automake
129M    bison
74M     cppi
437M    cu
103M    diffutils
732M    emacs
2.3G    gcc
345M    glibc
252M    gnulib
187M    grep
90M     gzip
4.7G    total

Both grep binaries were compiled with gcc-6.0.something (built from git)
using ./configure --enable-gcc-warnings && make

Here are best-of-3 timings running this command:

  env LC_ALL=en_US.UTF-8 time grep -ri mystring [a-g]* > /dev/null

grep-2.21: 8.05user 1.10system 0:09.17elapsed 99%CPU
(0avgtext+0avgdata 32876maxresident)k
0inputs+0outputs (0major+9986minor)pagefaults 0swaps

grep-2.22: 8.04user 1.04system 0:09.10elapsed 99%CPU
(0avgtext+0avgdata 32940maxresident)k
0inputs+0outputs (0major+9988minor)pagefaults 0swaps

It is critical to mention the locale you use.
As you see above, I explicitly set LC_ALL=en_US.UTF-8.
Note that when I switch to LC_ALL=C, it halves those times,
although the ~1% win with 2.22 still remains

Would you please compile 2.21 yourself, too? Otherwise, the timing may
be biased by the fact that distribution-provided binaries are often
better optimized than those one gets when building from sources with
the default options. If we can identify a modern system for which
there is anywhere near a 2x performance regression, I would be very
interested to learn more.

Message #32 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Norihiro Tanaka <noritnk <at> kcn.ne.jp>
To: bug-grep <at> gnu.org
Subject: Re: bug#21700: new snapshot available: grep-2.21.78-7da30
Date: Thu, 22 Oct 2015 08:41:59 +0900

On Wed, 21 Oct 2015 13:09:14 -0700
Gary Johnson <garyjohn <at> spocom.com> wrote:

> I also built the snapshot successfully on a Fedora 17 system that I
> use for real work.  I just ran a performance test, FWIW.  I searched
> recursively in our source hierarchy of 6044 regular files and 1102
> directories for a simple string.
> 
>     time grep -Rin mystring src > /dev/null
> 
> Here are the results, averaged over three trials each, not including
> any slow times clearly due to updating caches.
> 
>             2.12    2.21    2.21.78-7da30
>             -----   -----   -----
>     real    18.0s   1.08s   2.36s
>     user    17.8s   0.96s   2.24s
>     sys     0.12s   0.11s   0.10s
> 
> Version 2.12 was /bin/grep.  The other two versions I built myself.
> 
> Regards,
> Gary

If they are measured for first scan, could you retry second or later
scans, i.e. all input files is on memory?  I think physical read time
for disk should be eliminated.

Thanks,
Norihiro

Message #35 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Gary Johnson <garyjohn <at> spocom.com>
To: bug-grep <at> gnu.org
Subject: Re: bug#21700: new snapshot available: grep-2.21.78-7da30
Date: Wed, 21 Oct 2015 17:44:24 -0700

On 2015-10-22, Norihiro Tanaka wrote:
> On Wed, 21 Oct 2015 13:09:14 -0700
> Gary Johnson wrote:
> 
> > I also built the snapshot successfully on a Fedora 17 system that I
> > use for real work.  I just ran a performance test, FWIW.  I searched
> > recursively in our source hierarchy of 6044 regular files and 1102
> > directories for a simple string.
> > 
> >     time grep -Rin mystring src > /dev/null
> > 
> > Here are the results, averaged over three trials each, not including
> > any slow times clearly due to updating caches.
> > 
> >             2.12    2.21    2.21.78-7da30
> >             -----   -----   -----
> >     real    18.0s   1.08s   2.36s
> >     user    17.8s   0.96s   2.24s
> >     sys     0.12s   0.11s   0.10s
> > 
> > Version 2.12 was /bin/grep.  The other two versions I built myself.
> > 
> > Regards,
> > Gary
> 
> If they are measured for first scan, could you retry second or later
> scans, i.e. all input files is on memory?  I think physical read time
> for disk should be eliminated.

I did.  That's what I meant by "not including any slow times clearly
due to updating caches."  Sorry I wasn't more clear.

The system has 12 GB of RAM.  I'll provide more information, as
requested previously, when I get a little more time.

Regards,
Gary

Message #41 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Gary Johnson <garyjohn <at> spocom.com>
To: bug-grep <at> gnu.org
Subject: Re: bug#21700: new snapshot available: grep-2.21.78-7da30
Date: Thu, 22 Oct 2015 16:49:34 -0700

On 2015-10-21, Jim Meyering wrote:
> On Wed, Oct 21, 2015 at 1:09 PM, Gary Johnson wrote:
> > On 2015-10-18, Jim Meyering wrote:
> >> > I built the snapshot on two systems, a fairly old one running Ubuntu
> >> > 10.04.4 and a newer one running an up-to-date Linux Mint 17.2.
> >> > 'make check' reported the same two failures on both:
> >> >
> >> >    XFAIL: backref-alt
> >> >    XFAIL: triple-backref
> >>
> >> Thanks for building and reporting.
> >> Each of those "XFAIL"s indicates an expected failure, so that is the
> >> expected test result, for now.
> >
> > OK, thanks.
> >
> > I also built the snapshot successfully on a Fedora 17 system that I
> > use for real work.  I just ran a performance test, FWIW.  I searched
> > recursively in our source hierarchy of 6044 regular files and 1102
> > directories for a simple string.
> >
> >     time grep -Rin mystring src > /dev/null
> >
> > Here are the results, averaged over three trials each, not including
> > any slow times clearly due to updating caches.
> >
> >             2.12    2.21    2.21.78-7da30
> >             -----   -----   -----
> >     real    18.0s   1.08s   2.36s
> >     user    17.8s   0.96s   2.24s
> >     sys     0.12s   0.11s   0.10s
> >
> > Version 2.12 was /bin/grep.  The other two versions I built myself.
> 
> Thank you for the timings. Next time, please include the following:

This is kind of long, so I'll summarize here.  The relatively poor
performance I observed of grep-2.21.78 appears to have been due to
my having built it in an environment tainted with CFLAGS from the
build of another project.  A clean build of grep-2.21.78 resulted in
performance only slightly worse than grep-2.21.

>   - CPU type/speed

From lshw (probably more than you wanted):

     *-cpu:0
          description: CPU
          product: Quad-Core Xeon 5xxx
          vendor: Intel Corp.
          physical id: 5
          bus info: cpu <at> 0
          version: Intel(R) Xeon(R) CPU E5506 @ 2.13GHz
          slot: CPU0 PROCESSOR
          size: 1596MHz
          capacity: 2128MHz
          width: 64 bits
          clock: 505MHz
          capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp constant_tsc arch_perf
mon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm tpr_shadow vnmi flexpriority ept vpid cpufreq
          configuration: cores=4 enabledcores=4 threads=4
        *-cache:0
             description: L1 cache
             physical id: 7
             slot: L1 Cache
             size: 256KiB
             capacity: 256KiB
             capabilities: burst internal write-through unified
        *-cache:1
             description: L2 cache
             physical id: 8
             slot: L2 Cache
             size: 1MiB
             capacity: 1MiB
             capabilities: burst internal write-back unified
        *-cache:2
             description: L3 cache
             physical id: 9
             slot: L3 Cache
             size: 4MiB
             capacity: 4MiB
             capabilities: burst internal write-back unified
     *-cpu:1
          description: CPU
          product: Quad-Core Xeon 5xxx
          vendor: Intel Corp.
          physical id: 6
          bus info: cpu <at> 1
          version: Intel(R) Xeon(R) CPU E5506 @ 2.13GHz
          slot: CPU1 PROCESSOR
          size: 1596MHz
          capacity: 2128MHz
          width: 64 bits
          clock: 505MHz
          capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 popcnt lahf_lm tpr_shadow vnmi flexpriority ept vpid cpufreq
          configuration: cores=4 enabledcores=4 threads=4
        *-cache:0
             description: L1 cache
             physical id: a
             slot: L1 Cache
             size: 256KiB
             capacity: 256KiB
             capabilities: burst internal write-through unified
        *-cache:1
             description: L2 cache
             physical id: b
             slot: L2 Cache
             size: 1MiB
             capacity: 1MiB
             capabilities: burst internal write-back unified
        *-cache:2
             description: L3 cache
             physical id: c
             slot: L3 Cache
             size: 4MiB
             capacity: 4MiB
             capabilities: burst internal write-back unified

>   - file system type (and SSD or spinning rust)

Type: ext4
Size: 1.1 TB
Spinning rust

The file system resides on an LVM logical volume composed of two
physical volumes.  One physical volume is on a Seagate ST3250318AS
and the other is on a Western Digital WDC WD1002FAEX-0.  I didn't
build the system, so I don't know very much about this.

>   - OS version

Fedora 17
Kernel: 3.3.4-5.fc17.x86_64

>   - options with which you configured/built grep

Version 2.21:
    ./configure --prefix=$HOME/src/grep-2.21
    make

Version 2.21.78-7da30:
    ./configure --prefix=$HOME/src/grep-2.21.78
    make

gcc is:
    gcc (GCC) 4.7.0 20120507 (Red Hat 4.7.0-5)

>   - your current locale

LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE=C
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

> While you see a performance degradation going from 2.21 to the
> first 2.22 release candidate, I see the opposite trend, albeit barely
> measurable:
> 
> Searching the following hierarchies, I see a consistent 1% improvement
> going from 2.21 to 2.22 on an Intel(R) Core(TM) i7-4770S CPU @ 3.10GHz.
> The files I searched were on an ext4 file system residing on an SSD
> (OCZ-VERTEX3).
> This system is using fedora rawhide.
> 
> $ find [a-g]* -type f|wc -l
> 335065
> $ find [a-g]* -type d|wc -l
> 9667
> $ du -shc [a-g]*
> 25M     autoconf
> 125M    automake
> 129M    bison
> 74M     cppi
> 437M    cu
> 103M    diffutils
> 732M    emacs
> 2.3G    gcc
> 345M    glibc
> 252M    gnulib
> 187M    grep
> 90M     gzip
> 4.7G    total
> 
> Both grep binaries were compiled with gcc-6.0.something (built from git)
> using ./configure --enable-gcc-warnings && make
> 
> Here are best-of-3 timings running this command:
> 
>   env LC_ALL=en_US.UTF-8 time grep -ri mystring [a-g]* > /dev/null
> 
> grep-2.21: 8.05user 1.10system 0:09.17elapsed 99%CPU
> (0avgtext+0avgdata 32876maxresident)k
> 0inputs+0outputs (0major+9986minor)pagefaults 0swaps
> 
> grep-2.22: 8.04user 1.04system 0:09.10elapsed 99%CPU
> (0avgtext+0avgdata 32940maxresident)k
> 0inputs+0outputs (0major+9988minor)pagefaults 0swaps
> 
> It is critical to mention the locale you use.
> As you see above, I explicitly set LC_ALL=en_US.UTF-8.
> Note that when I switch to LC_ALL=C, it halves those times,
> although the ~1% win with 2.22 still remains
> 
> Would you please compile 2.21 yourself, too? Otherwise, the timing may
> be biased by the fact that distribution-provided binaries are often
> better optimized than those one gets when building from sources with
> the default options. If we can identify a modern system for which
> there is anywhere near a 2x performance regression, I would be very
> interested to learn more.

Version 2.21 is one I compiled myself.  The distribution-provided
version is 2.12.

Your comments encouraged me to pay more attention to what I was
doing.  I compared the config.log files from the grep-2.21 and
grep-2.21.78-7da30 directories and noticed that the environments and
results were slightly different.  I noticed that CFLAGS had been set
to "-g -DFEAT_CONCEAL" for a Vim build and had been used when I
built grep-2.21.78.  Also, I had built grep-2.21 back in February
and couldn't be sure that nothing relevant had changed on the system
since then.

So I opened a new xterm window, created two new build directories
and untarred, configured and made both grep versions from scratch.
New measurements showed no difference between the two 2.21 builds,
but a significant improvement in the 2.21.78 times.  Here are the
new results.  The times of successive runs were very close, so I
just chose a representative example of each.  In short, 2.21.78
appears _slightly_ slower than 2.21, but not enough (for me) to
worry about.

====================================================================

$ time ~/grep-2.21-new/bin/grep -ri mystring src > /dev/null

real    0m0.814s
user    0m0.725s
sys     0m0.081s

$ time LC_ALL=en_US.UTF-8 ~/grep-2.21-new/bin/grep -ri mystring src > /dev/null

real    0m0.817s
user    0m0.720s
sys     0m0.090s

$ time LC_ALL=C ~/grep-2.21-new/bin/grep -ri mystring src > /dev/null

real    0m0.350s
user    0m0.252s
sys     0m0.094s

====================================================================

$ time ~/grep-2.21.78-new/bin/grep -ri mystring src > /dev/null

real    0m0.849s
user    0m0.756s
sys     0m0.086s

$ time LC_ALL=en_US.UTF-8 ~/grep-2.21.78-new/bin/grep -ri mystring src > /dev/null

real    0m0.849s
user    0m0.751s
sys     0m0.090s

$ time LC_ALL=C ~/grep-2.21.78-new/bin/grep -ri mystring src > /dev/null

real    0m0.354s
user    0m0.267s
sys     0m0.082s

====================================================================

I'm sorry for wasting your time on a wild goose chase.  (But my new
grep works better now!)

Regards,
Gary

Message #44 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: bug-grep <at> gnu.org
Cc: 21700 <at> debbugs.gnu.org
Subject: Re: bug#21700: new snapshot available: grep-2.21.78-7da30
Date: Thu, 22 Oct 2015 21:41:11 -0700

On Thu, Oct 22, 2015 at 4:49 PM, Gary Johnson <garyjohn <at> spocom.com> wrote:
> [...]  In short, 2.21.78
> appears _slightly_ slower than 2.21, but not enough (for me) to
> worry about.

Thanks for confirming that your performance regression is so small.

Message #50 received at 21700 <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: 21700 <at> debbugs.gnu.org
Subject: Re: bug#21700: new snapshot available: grep-2.21.78-7da30
Date: Sat, 24 Oct 2015 18:34:43 -0700

[Message part 1 (text/plain, inline)]

On Sat, Oct 17, 2015 at 10:26 PM, Jim Meyering <jim <at> meyering.net> wrote:
> I want to release grep-2.22 in just a couple of days.
> This release is motivated largely by the discovery that there has
> been a bug in versions 2.19, 2.20 and 2.21 that made grep mistakenly
> print some lines that did not match. However, there have also been
> several other bug fixes and notable performance improvements.
>
> Any testing you can do would be most welcome.
> Feedback, even the report that you "built and passed tests on XYZ,"
> would be appreciated.

I'm about to push the following three small patches and make another
test release, hoping a few more people will run tests. So far, very
few people have actually run tests, if the replies to this
announcement are any indication. Let's be optimistic and presume that
many have built and run the tests, but didn't bother to write in
because all of the test passed.

[0001-tests-avoid-spurious-failure-on-OpenBSD-5.8.patch (text/x-patch, attachment)]

[0002-maint-NEWS-correct-amend.patch (text/x-patch, attachment)]

[0003-gnulib-update-to-latest-for-portability-fixes.patch (text/x-patch, attachment)]

Message #53 received at 21700 <at> debbugs.gnu.org (full text, mbox):

From: Shlomi Fish <shlomif <at> shlomifish.org>
To: Jim Meyering <jim <at> meyering.net>
Cc: 21700 <at> debbugs.gnu.org
Subject: Re: bug#21700: new snapshot available: grep-2.21.78-7da30
Date: Sun, 25 Oct 2015 08:38:30 +0200

Hi Jim,

On Sat, 24 Oct 2015 18:34:43 -0700
Jim Meyering <jim <at> meyering.net> wrote:

> On Sat, Oct 17, 2015 at 10:26 PM, Jim Meyering <jim <at> meyering.net> wrote:
> > I want to release grep-2.22 in just a couple of days.
> > This release is motivated largely by the discovery that there has
> > been a bug in versions 2.19, 2.20 and 2.21 that made grep mistakenly
> > print some lines that did not match. However, there have also been
> > several other bug fixes and notable performance improvements.
> >
> > Any testing you can do would be most welcome.
> > Feedback, even the report that you "built and passed tests on XYZ,"
> > would be appreciated.  
> 
> I'm about to push the following three small patches and make another
> test release, hoping a few more people will run tests. So far, very
> few people have actually run tests, if the replies to this
> announcement are any indication. Let's be optimistic and presume that
> many have built and run the tests, but didn't bother to write in
> because all of the test passed.

How can I get the sources to this test snapshot along with all the patches? Can
you provide a reproduction recipe?

Regards,

	Shlomi Fish

-- 
-----------------------------------------------------------------
Shlomi Fish       http://www.shlomifish.org/
Summer Glau Facts - http://shlom.in/sglau-facts

Major Kira: Well, duh! The prophets spoke of several of The Invisible’s
children and their whereabouts.
Jadzia: Major, you and I will need to talk someday about that “duh”.
    — http://www.shlomifish.org/humour/Star-Trek/We-the-Living-Dead/

Please reply to list if it's a mailing list post - http://shlom.in/reply .

Message #56 received at 21700 <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: 21700 <at> debbugs.gnu.org
Subject: Re: bug#21700: new snapshot available: grep-2.21.78-7da30
Date: Sun, 25 Oct 2015 09:27:14 -0700

On Sat, Oct 24, 2015 at 11:38 PM, Shlomi Fish <shlomif <at> shlomifish.org> wrote:
> Hi Jim,
>
> On Sat, 24 Oct 2015 18:34:43 -0700
> Jim Meyering <jim <at> meyering.net> wrote:
>
>> On Sat, Oct 17, 2015 at 10:26 PM, Jim Meyering <jim <at> meyering.net> wrote:
>> > I want to release grep-2.22 in just a couple of days.
>> > This release is motivated largely by the discovery that there has
>> > been a bug in versions 2.19, 2.20 and 2.21 that made grep mistakenly
>> > print some lines that did not match. However, there have also been
>> > several other bug fixes and notable performance improvements.
>> >
>> > Any testing you can do would be most welcome.
>> > Feedback, even the report that you "built and passed tests on XYZ,"
>> > would be appreciated.
>>
>> I'm about to push the following three small patches and make another
>> test release, hoping a few more people will run tests. So far, very
>> few people have actually run tests, if the replies to this
>> announcement are any indication. Let's be optimistic and presume that
>> many have built and run the tests, but didn't bother to write in
>> because all of the test passed.
>
> How can I get the sources to this test snapshot along with all the patches? Can
> you provide a reproduction recipe?

I've just posted links to new tarballs.
To build from git-cloned sources, follow these instructions:
http://git.savannah.gnu.org/cgit/grep.git/tree/README-hacking

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.