History log of /external/llvm/lib/Support/regcomp.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
36b56886974eae4f9c5ebc96befd3e7bfe5de338 24-Apr-2014 Stephen Hines <srhines@google.com> Update to LLVM 3.5a.

Change-Id: Ifadecab779f128e62e430c2b4f6ddd84953ed617
/external/llvm/lib/Support/regcomp.c
6b731486d4460e5f1088a6066c0081af048c1e45 28-Nov-2012 Eli Bendersky <eliben@google.com> Add backreference matching capabilities to Support/Regex, with
appropriate unit tests. This change in itself is not expected to
affect any functionality at this point, but it will serve as a
stepping stone to improve FileCheck's variable matching capabilities.

Luckily, our regex implementation already supports backreferences,
although a bit of hacking is required to enable it. It supports both
Basic Regular Expressions (BREs) and Extended Regular Expressions
(EREs), without supporting backrefs for EREs, following POSIX strictly
in this respect. And EREs is what we actually use (rightly). This is
contrary to many implementations (including the default on Linux) of
POSIX regexes, that do allow backrefs in EREs.

Adding backref support to our EREs is a very simple change in the
regcomp parsing code. I fail to think of significant cases where it
would clash with existing things, and can bring more versatility to
the regexes we write. There's always the danger of a backref in a
specially crafted regex causing exponential matching times, but since
we mainly use them for testing purposes I don't think it's a big
problem. [it can also be placed behind a flag specific to FileCheck,
if needed].

For more details, see:

* http://lists.cs.uiuc.edu/pipermail/llvmdev/2012-November/055840.html
* http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20121126/156878.html



git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@168802 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/lib/Support/regcomp.c
c61ac5120ddb5b58693aff42d43cc8e23b7bd0c2 08-Mar-2011 NAKAMURA Takumi <geek4civic@gmail.com> lib/Support/regcomp.c: Fix cygwin warning.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@127241 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/lib/Support/regcomp.c
ee7110f0478cc90ffa419759e21557ed8d669562 08-Sep-2009 Daniel Dunbar <daniel@zuster.org> Fix may-be-used-uninitialized warning.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@81223 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/lib/Support/regcomp.c
8b3594afdb402e088ac1b891930c599e58992afa 06-Sep-2009 Benjamin Kramer <benny.kra@googlemail.com> More MSVC warning fixes:
1. DUPMAX is defined in regcomp.c, no need to redefine it in regutils.
2. MSVC doesn't like snprintf, use _snprintf instead.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@81114 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/lib/Support/regcomp.c
5b7c3567a16340153f9f2074199ff4877e0c283d 06-Sep-2009 Benjamin Kramer <benny.kra@googlemail.com> Remove splint hints to silence warnings from ICC and MSVC.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@81108 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/lib/Support/regcomp.c
12420d3a641cc3734a128f21c909d35c4b62f43a 30-Aug-2009 Daniel Dunbar <daniel@zuster.org> Fix some possible-use-of-uninitialized warnings.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@80515 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/lib/Support/regcomp.c
ce0c81e7dd321e9f94f628daa5528f56cab0ab88 30-Aug-2009 Torok Edwin <edwintorok@gmail.com> Add regular expression matching support, based on OpenBSD regexec()/regcomp()
implementation.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@80493 91177308-0d34-0410-b5e6-96231b3b80d8
/external/llvm/lib/Support/regcomp.c