Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: hjl@lucon.org
Cc: zackw@stanford.edu, dj@redhat.com, gcc@gcc.gnu.org,
	gdb@sources.redhat.com, binutils@sources.redhat.com,
	cygwin@sources.redhat.com
Subject: Re: Another RFC: regex in libiberty
Date: Fri, 08 Jun 2001 10:31:00 -0000	[thread overview]
Message-ID: <4098-Fri08Jun2001202600+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <20010608100532.B5728@lucon.org>

> 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).


  reply	other threads:[~2001-06-08 10:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Daniel>
     [not found] ` <Vogel's>
     [not found]   ` <message>
     [not found]     ` <of>
     [not found]       ` <Mon,>
     [not found]         ` <01>
     [not found]           ` <Nov>
     [not found]             ` <1999>
     [not found]               ` <14:25:01>
     [not found]                 ` <+0100>
     [not found]                   ` <381D94AD.B37EC167@grafzahl.de>
1999-11-08  8:54                     ` go32-nat.c compilation problem Pierre Muller
     [not found]       ` <Fri,>
     [not found]         ` <08>
     [not found]           ` <Jun>
     [not found]             ` <2001>
     [not found]               ` <10:06:51>
     [not found]                 ` <+0300>
2001-06-07 18:27                   ` Another RFC: regex in libiberty DJ Delorie
2001-06-07 18:31                     ` Ian Lance Taylor
2001-06-07 18:33                       ` DJ Delorie
2001-06-07 18:43                         ` Ian Lance Taylor
2001-06-08  0:11                     ` Eli Zaretskii
2001-06-08  9:18                       ` Mark Mitchell
2001-06-08  9:59                       ` Zack Weinberg
2001-06-08 10:05                         ` H . J . Lu
2001-06-08 10:31                           ` Eli Zaretskii [this message]
2001-06-08 10:39                             ` H . J . Lu
2001-06-08 10:37                         ` Eli Zaretskii
2001-06-11 22:49                       ` Jim Blandy
2001-06-11 23:51                         ` Randall R Schulz
2001-06-12  6:48                         ` Jim Blandy
2001-06-08  1:15                     ` Pierre Muller
2001-06-08  1:36                       ` About struct bpp_transfer_params ±èµæÁß
2001-06-08  7:43                         ` Fernando Nasser
2001-06-09 13:34                     ` Another RFC: regex in libiberty Andrew Cagney
     [not found] <Eli>

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4098-Fri08Jun2001202600+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=binutils@sources.redhat.com \
    --cc=cygwin@sources.redhat.com \
    --cc=dj@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=hjl@lucon.org \
    --cc=zackw@stanford.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox