Paolo Bonzini wrote:
> On 06/15/2011 09:12 PM, Jim Meyering wrote:
>> However, backreferences force these tools to skip the DFA-based
>> optimization and resort to running the regexp code. In that case,
>> there is a dichotomy. Adding a backreference to a range-including
>> regexp would have the
Paul Eggert wrote:
> * lib/nanosleep.c (my_usleep): Don't assume signed integer
> arithmetic wraps around on overflow.
> ---
> ChangeLog |4
> lib/nanosleep.c |5 ++---
> 2 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/ChangeLog b/ChangeLog
> index 8e39acf..846
On 06/16/2011 09:06 PM, Aharon Robbins wrote:
I have already corresponded with Chet. He plans to add a shell option
to enable RRI, and we can hope that at some point, it might become the
default. So that has already been started.
I'd do the other way round---make it the default, and add a shell
On 06/15/2011 09:12 PM, Jim Meyering wrote:
However, backreferences force these tools to skip the DFA-based
optimization and resort to running the regexp code. In that case,
there is a dichotomy. Adding a backreference to a range-including
regexp would have the surprising consequence of changin
On 06/16/2011 10:44 AM, Jim Meyering wrote:
> To make this proposed change go through, that configure-time option would
> have to be eliminated, so that we always build with the gnulib-provided
> regex code. Of course, if glibc ever changes, we can detect that and
> automatically prefer it w
