microsoft
/
clang
зеркало из https://github.com/microsoft/clang.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
19 028 коммитов 3 Ветки 0 Теги 180 MiB
C++ 70.2%
C 22.4%
Objective-C 3.5%
HTML 1.2%
Objective-C++ 0.9%
Разное 1.4%
Перейти к файлу
Ted Kremenek d0ed448120 Add a stop gap to Sema::CorrectTypo() to correct only up to 20 typos. 
This is to address a serious performance problem observed when running
'clang -fsyntax-only' on really broken source files.  In one case,
repeatedly calling CorrectTypo() caused one source file to be rejected
after 2 minutes instead of 1 second.

This patch causes typo correction to take neglible time on that file
while still providing correction results for the first 20 cases.  I
felt this was a reasonable number for moderately broken source files.

I don't claim this is the best solution.  Comments welcome.  It is
necessary for us to address this issue because it is a serious
performance problem.


git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@95049 91177308-0d34-0410-b5e6-96231b3b80d8
 		2010-02-02 02:07:01 +00:00
INPUTS Add an input file that includes all standard C++ headers 2009-09-29 03:26:11 +00:00
bindings/python cindex/Python: Turn off showing IDs by default, they are really slow to compute 2010-01-31 00:41:15 +00:00
clang.xcodeproj Combine AsmStmt::setOutputsAndInputs and AsmStmt::setClobbers. 2010-01-30 19:34:25 +00:00
docs Clarify the documentation of ext_vector, and add a small example. Hopefully 2010-01-27 01:22:36 +00:00
examples -fno-rtti is now the default. 2010-01-24 20:43:31 +00:00
include Implement PR6180, substantially improving the diagnostics we get from 2010-02-02 01:23:29 +00:00
lib Add a stop gap to Sema::CorrectTypo() to correct only up to 20 typos. 2010-02-02 02:07:01 +00:00
test Fix bug in GRExprEngine::VisitSizeOfAlignOfExpr() where we do not add 2010-02-02 02:01:51 +00:00
tools In C++, an initializer on a variable doesn't necessarily mean it's the definition. With that in mind, rename getDefinition to getAnyInitializer (to distinguish it from getInit) and reimplement it in terms of isThisDeclarationADefinition. Update all code to use this new function. 2010-02-01 20:16:42 +00:00
utils Extern darwin-clang_rt.c test to also test targetting ARM ({armv6, armv7} x 2010-01-23 00:26:38 +00:00
www add another example. 2010-02-02 01:35:23 +00:00
CMakeLists.txt Add optional CMake build for Clang examples, patch by Kovarththanan Rajaratnam. 2009-11-17 09:32:51 +00:00
INSTALL.txt Add minimal INSTALL.txt 2009-09-13 02:21:31 +00:00
LICENSE.TXT 2010 is here. 2010-01-09 18:40:42 +00:00
Makefile Improve updating of test/Makefile for out-of-dir builds. 2009-12-21 23:28:06 +00:00
ModuleInfo.txt Move the ModuleInfo.txt file. 2007-07-11 17:03:27 +00:00
NOTES.txt Remove clang-cc tool, it has joined in unholy union with clang. 2009-12-12 00:56:47 +00:00
README.txt rewrite readme. 2009-09-13 17:23:57 +00:00
TODO.txt switch -Werror/-Wfatal-errors error conditions to use diagnostics instead 2009-12-23 18:53:37 +00:00
VER Collapse more clang version numbers down into fewer places. 2009-09-16 01:26:05 +00:00

README.txt 

//===----------------------------------------------------------------------===//
// C Language Family Front-end
//===----------------------------------------------------------------------===//

Welcome to Clang.  This is a compiler front-end for the C family of languages
(C, C++, Objective-C, and Objective-C++) which is built as part of the LLVM
compiler intrastructure project.

Unlike many other compiler frontends, Clang is useful for a number of things
beyond just compiling code: we intend for Clang to be host to a number of
different source level tools.  One example of this is the Clang Static Analyzer.

If you're interested in more (including how to build Clang) it is best to read
the relevant web sites.  Here are some pointers:

Information on Clang:              http://clang.llvm.org/
Building and using Clang:          http://clang.llvm.org/get_started.html
Clang Static Analyzer:             http://clang-analyzer.llvm.org/
Information on the LLVM project:   http://llvm.org/

If you have questions or comments about Clang, a great place to discuss them is
on the Clang development mailing list:
  http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev

If you find a bug in Clang, please file it in the LLVM bug tracker:
  http://llvm.org/bugs/