aboutsummaryrefslogtreecommitdiffstats
path: root/main/musl/0003-fix-at-the-start-of-a-complete-BRE.patch
diff options
context:
space:
mode:
Diffstat (limited to 'main/musl/0003-fix-at-the-start-of-a-complete-BRE.patch')
-rw-r--r--main/musl/0003-fix-at-the-start-of-a-complete-BRE.patch34
1 files changed, 0 insertions, 34 deletions
diff --git a/main/musl/0003-fix-at-the-start-of-a-complete-BRE.patch b/main/musl/0003-fix-at-the-start-of-a-complete-BRE.patch
deleted file mode 100644
index dac819d007..0000000000
--- a/main/musl/0003-fix-at-the-start-of-a-complete-BRE.patch
+++ /dev/null
@@ -1,34 +0,0 @@
-From 29b13575376509bb21539711f30c1deaf0823033 Mon Sep 17 00:00:00 2001
-From: Szabolcs Nagy <nsz@port70.net>
-Date: Mon, 29 Feb 2016 16:36:25 +0000
-Subject: [PATCH] fix ^* at the start of a complete BRE
-
-This is a workaround to treat * as literal * at the start of a BRE.
-
-Ideally ^ would be treated as an anchor at the start of any BRE
-subexpression and similarly $ would be an anchor at the end of any
-subexpression. This is not required by the standard and hard to do
-with the current code, but it's the existing practice. If it is
-changed, * should be treated as literal after such anchor as well.
----
- src/regex/regcomp.c | 4 ++++
- 1 file changed, 4 insertions(+)
-
-diff --git a/src/regex/regcomp.c b/src/regex/regcomp.c
-index 7a2864c..5fad98b 100644
---- a/src/regex/regcomp.c
-+++ b/src/regex/regcomp.c
-@@ -994,6 +994,10 @@ static reg_errcode_t tre_parse(tre_parse_ctx_t *ctx)
- if (*s=='\\')
- s++;
-
-+ /* handle ^* at the start of a complete BRE. */
-+ if (!ere && s==ctx->re+1 && s[-1]=='^')
-+ break;
-+
- /* extension: multiple consecutive *+?{,} is unspecified,
- but (a+)+ has to be supported so accepting a++ makes
- sense, note however that the RE_DUP_MAX limit can be
---
-2.7.2
-