This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: [PATCH] fix the last sed testsuite XFAIL
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Paolo Bonzini <bonzini at gnu dot org>
- Cc: libc-alpha at sources dot redhat dot com
- Date: Sat, 13 Dec 2003 23:15:19 +0100
- Subject: Re: [PATCH] fix the last sed testsuite XFAIL
- References: <002e01c3c1cf$d374e3f0$85df1d97@philo>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Sun, Dec 14, 2003 at 12:19:35AM +0100, Paolo Bonzini wrote:
> This is against my other patch, but should apply cleanly even without it.
> I'll send a testcase on Monday. Interestingly, Perl and PCRE behave like
> the current glibc implementation, so this may trigger a fake failure in the
> new PCRE-based tests that Jakub wrote.
Does this fix also the:
; XXX FIXME the following 4 tests fail ATM
;a(b|c?)+d abcd 0 4 2 3
;a(b|((c)*))+d abcd 0 4 2 3 2 3 2 3
;a(b+|((c)*))+d abd 0 3 1 2 -1 -1 -1 -1
;a(b+|((c)*))+d abcd 0 4 2 3 2 3 2 3
; XXX FIXME the following 3 tests fail ATM
;a(b|((c)*))*d abcd 0 4 2 3 2 3 2 3
;a(b+|((c)*))*d abd 0 3 1 2 -1 -1 -1 -1
;a(b+|((c)*))*d abcd 0 4 2 3 2 3 2 3
failures in BOOST.tests or do you fix just the OP_DUP_NUM case?
Jakub