Re: memmem test faiure on IRIX

2008-01-11 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 1/11/2008 5:14 PM: | | The reason is that test-memmem on this machine takes about 13 seconds | without time limitation, whereas test-strstr needs about 3 seconds. So | it's needed to increase these allowed times. memmem i

memmem test faiure on IRIX

2008-01-11 Thread Bruno Haible
On IRIX 6.5, I got this: $ make check Making check in gllib make check-am Making check in glm4 Making check in gltests make check-recursive make check-TESTS sh[9]: 34324 Alarm call FAIL: test-memmem PASS: test-stdbool PASS: test-stdint PASS: test-string PASS: test-strstr

Re: strstr speedup

2008-01-11 Thread Bruno Haible
Eric Blake wrote: > --- a/doc/functions/strstr.texi > +++ b/doc/functions/strstr.texi > @@ -4,10 +4,14 @@ >   >  POSIX specification: @url{http://www.opengroup.org/susv3xsh/strstr.html} >   > -Gnulib module: --- > +Gnulib module: strstr >   >  Portability problems fixed by Gnulib: > [EMAIL PROTECTE

Re: git methodology

2008-01-11 Thread Benoit Sigoure
On Jan 11, 2008, at 12:16 PM, Bruno Haible wrote: you will create a new repository. For this purpose, you can have a "gnulib-clean" reposity that only ever contains unmodified gnulib; copying this repository (with "cp -a") is faster than doing a "gnulib clone" across the network. You can

Re: strstr speedup

2008-01-11 Thread Bruno Haible
Eric Blake wrote: > | should I go ahead and prepare a patch for strcasestr, c-strcasestr, and > | memcasecmp to utilize str-two-way.h? Yes for strcasestr and c-strcasestr. > How's this for strcasestr? Glibc's strcasestr is quadratic (no surprise > there, given our track record); cygwin 1.5.x doe

Re: git methodology

2008-01-11 Thread Bruno Haible
Paul Eggert wrote: > > Then the two "git stash" commands were unnecessary; all that's needed is > > > > $ git pull > > # fix conflicts then "git commit" of the merged files > > I vaguely recall that when I've done that in the past, I installed > unnecessary gunk into the savannah rep

Re: Recommended headers include order

2008-01-11 Thread Bruno Haible
Jim Meyering wrote: > That was necessary when -ansi would make gcc > fail to recognize __attribute__. That's what my memory said as well. But I tested gcc 2.95.3, 3.1, 3.2, 3.3, 3.4, 4.0, 4.1, 4.2, and through the posted test program I verified that they recognize and evaluate __attribute__ also w