Searched refs:range (Results 1 – 5 of 5) sorted by relevance
| /posix/ |
| A D | regex.c | 53 # define re_search(bufp, string, size, startpos, range, regs) \ argument
54 __re_search (bufp, string, size, startpos, range, regs)
58 # define re_search_2(bufp, st1, s1, st2, s2, startpos, range, regs, stop) \ argument
59 __re_search_2 (bufp, st1, s1, st2, s2, startpos, range, regs, stop)
|
| A D | regexec.c | 42 Idx start, regoff_t range,
47 regoff_t range, Idx stop,
288 Idx start, regoff_t range, struct re_registers *regs) in weak_alias()
311 const char *string2, Idx length2, Idx start, regoff_t range, in weak_alias()
315 start, range, regs, stop, false); in weak_alias()
324 regoff_t range, struct re_registers *regs, in weak_alias()
357 rval = re_search_stub (bufp, str, len, start, range, stop, regs, in weak_alias()
370 Idx start, regoff_t range, Idx stop, struct re_registers *regs, in re_search_stub() argument
379 Idx last_start = start + range; in re_search_stub()
385 || (0 <= range && last_start < start))) in re_search_stub()
[all …]
|
| A D | tst-fnmatch.input | 37 # > fall within the range based on that collating sequence, regardless
40 # > The current standard leaves unspecified the behavior of a range
42 # > conforming applications should avoid range expressions outside the
44 # > matchers to interpret range expressions using native order, CEO,
49 # > handled in range expressions. These ambiguities had led to multiple
|
| A D | PTESTS | 4 # outside the plain ASCII range have a risk of being mangled by modern
|
| A D | tst-regex.input | 824 * posix/fnmatch.c: Fix completely broken range matching.
5449 * elf/dl-minimal.c (__strtol_internal): Correct range check. Fix
|
Completed in 26 milliseconds