bcm5719-llvm - Project Ortega BCM5719 LLVM

	Commit message (Collapse)	Author	Age	Files	Lines
*	Use wider type for overflow check on LLP64 platforms like Win64, found by ↵	Reid Kleckner	2015-02-26	1	-2/+2
\| \| \| \| \| \|	clang-cl -Wtautological llvm-svn: 230684
*	Avoid integer overflows around realloc calls resulting in potential	Joerg Sonnenberger	2015-02-07	1	-0/+21
\| \| \| \| \| \| \|	heap. Problem identified by Guido Vranken. Changes differ from original OpenBSD sources by not depending on non-portable reallocarray. llvm-svn: 228507
*	Fix known typos	Alp Toker	2014-01-24	1	-3/+3
\| \| \| \| \| \| \|	Sweep the codebase for common typos. Includes some changes to visible function names that were misspelt. llvm-svn: 200018
*	Add backreference matching capabilities to Support/Regex, with	Eli Bendersky	2012-11-28	1	-1/+29
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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 llvm-svn: 168802
*	lib/Support/regcomp.c: Fix cygwin warning.	NAKAMURA Takumi	2011-03-08	1	-1/+1
\| \| \| \|	llvm-svn: 127241
*	Fix may-be-used-uninitialized warning.	Daniel Dunbar	2009-09-08	1	-2/+2
\| \| \| \|	llvm-svn: 81223
*	More MSVC warning fixes:	Benjamin Kramer	2009-09-06	1	-0/+1
\| \| \| \| \| \| \|	1. DUPMAX is defined in regcomp.c, no need to redefine it in regutils. 2. MSVC doesn't like snprintf, use _snprintf instead. llvm-svn: 81114
*	Remove splint hints to silence warnings from ICC and MSVC.	Benjamin Kramer	2009-09-06	1	-2/+2
\| \| \| \|	llvm-svn: 81108
*	Fix some possible-use-of-uninitialized warnings.	Daniel Dunbar	2009-08-30	1	-2/+2
\| \| \| \|	llvm-svn: 80515
*	Add regular expression matching support, based on OpenBSD regexec()/regcomp()	Torok Edwin	2009-08-30	1	-0/+1524
	implementation. llvm-svn: 80493