summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdlib/l64a.c
diff options
context:
space:
mode:
authorpfg <pfg@FreeBSD.org>2016-06-24 02:24:34 +0000
committerpfg <pfg@FreeBSD.org>2016-06-24 02:24:34 +0000
commit33e55d7e3fd8a63e84f2d3cc5a0e3834a98dd86f (patch)
tree39088ff1700d95a9713154b77b4299f1cd2feafa /lib/libc/stdlib/l64a.c
parentc45c824e6b4172efa131a7166214ec7a14ff5168 (diff)
downloadFreeBSD-src-33e55d7e3fd8a63e84f2d3cc5a0e3834a98dd86f.zip
FreeBSD-src-33e55d7e3fd8a63e84f2d3cc5a0e3834a98dd86f.tar.gz
MFC r300683:
libc: regexec(3) adjustment. Change the behavior of when REG_STARTEND is combined with REG_NOTBOL. From the original posting[1]: "Enable the assumption that pmatch[0].rm_so is a continuation offset to a string and allows us to do a proper assessment of the character in regards to it's word position ('^' or '\<'), without risking going into unallocated memory." This change makes us similar to how glibc handles REG_STARTEND | REG_NOTBOL, and is closely related to a soon-to-land fix to sed. Special thanks to Martijn van Duren and Ingo Schwarze for working out some consistent behaviour. Differential Revision: https://reviews.freebsd.org/D6257 Taken from: openbsd-tech 2016-05-24 [1] (Martijn van Duren)
Diffstat (limited to 'lib/libc/stdlib/l64a.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud