bcm5719-llvm/clang/INPUTS, branch meklort-10.0.1Project Ortega BCM5719 LLVMhttps://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.12012-09-27T10:16:10+00:00Revert 'Fix a typo 'iff' => 'if''. iff is an abreviation of if and only if. See: http://en.wikipedia.org/wiki/If_and_only_if Commit 1647662012-09-27T10:16:10+00:00Sylvestre Ledrusylvestre@debian.org2012-09-27T10:16:10+00:00urn:sha1:33b5baf189bc2d866d69c1c81908d2b37dce79ad
llvm-svn: 164769
Fix a typo 'iff' => 'if'2012-09-27T09:57:10+00:00Sylvestre Ledrusylvestre@debian.org2012-09-27T09:57:10+00:00urn:sha1:a876013dc91bbd6bf4fe37c0d4cc7d1d5f5f4184
llvm-svn: 164766
all-std-headers.cpp: Include the C++11 headers when building with clang2012-04-13T03:39:16+00:00Richard Smithrichard-llvm@metafoo.co.uk2012-04-13T03:39:16+00:00urn:sha1:0a465bb28ed82433e2bf92ad8a17b463ce343127
in -std=gnu++11 mode.
llvm-svn: 154654
For PR11916: Add support for g++'s __int128 keyword. Unlike __int128_t, this is2012-04-04T06:24:32+00:00Richard Smithrichard-llvm@metafoo.co.uk2012-04-04T06:24:32+00:00urn:sha1:f016bbcc610ba2d468b2966fd77831415c23149c
a type specifier and can be combined with unsigned. This allows libstdc++4.7 to
be used with clang in c++98 mode.
Several other changes are still required for libstdc++4.7 to work with clang in
c++11 mode.
llvm-svn: 153999
Extend all-std-headers.cpp to include C++11 headers when building in C++11 mode.2012-02-14T23:06:14+00:00Richard Smithrichard-llvm@metafoo.co.uk2012-02-14T23:06:14+00:00urn:sha1:9bd64f90e2429ee631075af38f382cb9244f8818
Conditionally include headers which older STL implementations don't provide.
llvm-svn: 150526
Enhance the CFG construction to detect no-return destructors for2011-09-13T06:09:01+00:00Chandler Carruthchandlerc@gmail.com2011-09-13T06:09:01+00:00urn:sha1:ad74725ab5d71295d2babeb6fef0d4cb4110c9a1
temporary objects and local variables. When detected, these split the
block, marking the new one as having only the exit block as a successor.
This prevents a large number of false positives in warnings sensitive to
no-return constructs such as -Wreturn-type, and fixes the remainder of
PR10063 along with several variations of this bug that had not been
reported. The test cases are extended across the board to cover these
patterns.
This also checks in a stress test for these types of CFGs. The stress
test declares some 32k variables, a mixture of no-return and normal
destructors. Previously, this resulted in roughly 2500 CFG blocks, but
didn't model any of the no-return destructors. With this patch, it
results in over 33k blocks, many of them now unreachable.
The nice thing about how the analyzer is set up? This causes *no*
regression in performance of building the CFG. It actually in some cases
makes it faster, as best I can benchmark. The analysis for -Wreturn-type
(and any other that cares about no-return code paths) is technically
slower now as it has to look at many more candidate blocks, but it
computes the correct answer. I have more test cases to follow, I think
they all work now. Also I have further work that should dramatically
simplify analyses in the presence of no-return.
llvm-svn: 139586
Add several CFG-stress-testing input source files. These use the2011-07-08T11:20:51+00:00Chandler Carruthchandlerc@gmail.com2011-07-08T11:20:51+00:00urn:sha1:d280754094a883a72988c3bd8bd51c5892452345
preprocessor to build up very large CFGs in various shapes that can
produce different algorithmic behavior in CFG-walking code.
llvm-svn: 134698
Add an input file that includes all standard C++ headers2009-09-29T03:26:11+00:00Douglas Gregordgregor@apple.com2009-09-29T03:26:11+00:00urn:sha1:4d46522df1d03248f6567d539719cd3290eb2391
llvm-svn: 83042
added to wrong directory2009-01-26T04:36:31+00:00Chris Lattnersabre@nondot.org2009-01-26T04:36:31+00:00urn:sha1:d6d0619fb408e4211161adef4819490f25948e16
llvm-svn: 62997
add an evil macro expansion perf test from Neil.2007-07-21T04:54:14+00:00Chris Lattnersabre@nondot.org2007-07-21T04:54:14+00:00urn:sha1:bb26836c3523a9f32c0d2239be54aee9c74e4b3c
llvm-svn: 40138