This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Another RFC: regex in libiberty
- To: hjl at lucon dot org
- Subject: Re: Another RFC: regex in libiberty
- From: "Eli Zaretskii" <eliz at is dot elta dot co dot il>
- Date: Fri, 08 Jun 2001 20:26:00 +0300
- CC: zackw at stanford dot edu, dj at redhat dot com, gcc at gcc dot gnu dot org, gdb at sources dot redhat dot com, binutils at sources dot redhat dot com, cygwin at sources dot redhat dot com
- References: <9003-Fri08Jun2001100651+0300-eliz@is.elta.co.il> <20010608095932.S979@stanford.edu> <20010608100532.B5728@lucon.org>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Fri, 8 Jun 2001 10:05:32 -0700
> From: "H . J . Lu" <hjl@lucon.org>
>
> On Fri, Jun 08, 2001 at 09:59:32AM -0700, Zack Weinberg wrote:
> >
> > The regex.c that came with GDB 4.18, which I think is the one that got
> > spread around widely, had a bug in its implementation of the POSIX
> > regcomp/regexec interface, which caused a major performance hit. That
> > bug has been fixed in GNU libc for a long time. When I replaced
> > fixincludes' copy of regex.c with a more recent version from glibc,
> > fixincludes was sped up by a factor of nine. That same bug affects
> > Sed 3.02 - replace the regex.c it ships with with the one from glibc
> > 2.2.x and I bet you'll see better performance.
> >
>
> I have been telling people that you should use regex.c in glibc if
> all possible if you are using gnu-regex. Every package which uses
> gnu-regex should have a configuration option not to use the included
> gnu-regex.
Sed does have such an option (I used it to build the binary with
Spencer's regex which is the standard regex included in the DJGPP
library).
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple