summaryrefslogtreecommitdiffstats
path: root/clang/test/Index/code-complete-errors.c
Commit message (Collapse)AuthorAgeFilesLines
* Speed up code-completion by skipping function bodies.Argyrios Kyrtzidis2011-01-031-25/+0
| | | | | | | | | | | | | | When we are in code-completion mode, skip parsing of all function bodies except the one where the code-completion point resides. For big .cpp files like 'SemaExpr.cpp' the improvement makes a huge difference, in some cases cutting down code-completion time -62% ! We don't get diagnostics for the bodies though, so modify the code-completion tests that check for errors. See rdar://8814203. llvm-svn: 122765
* Extend the libclang diagnostic API to provide information about theDouglas Gregor2010-11-191-2/+4
| | | | | | option name, category ID, and category name corresponding to a diagnostic. llvm-svn: 119802
* ntroduce clang_getSpellingLocation() into libclang, to provide theDouglas Gregor2010-11-091-1/+8
| | | | | | | | | | | | | | location where we're spelling a token even within a macro. clang_getInstantiationLocation() tells where we instantiated the macro. I'm still not thrilled with the CXSourceLocation/CXSourceRange APIs, since they gloss over macro-instantiation information. Take 2: this time, adjusted tests appropriately and used a "simple" approach to the spelling location. llvm-svn: 118495
* Revert r118492, which didn't update all of its tests accordinglyDouglas Gregor2010-11-091-8/+1
| | | | llvm-svn: 118494
* Introduce clang_getSpellingLocation() into libclang, to provide theDouglas Gregor2010-11-091-1/+8
| | | | | | | | | | | location where we're spelling a token even within a macro. clang_getInstantiationLocation() tells where we instantiated the macro. I'm still not thrilled with the CXSourceLocation/CXSourceRange APIs, since they gloss over macro-instantiation information. llvm-svn: 118492
* Make the "extra ';' inside a struct or union" diagnostic moreDouglas Gregor2010-06-161-1/+1
| | | | | | precise. Fixes PR7336. llvm-svn: 106170
* De-XFAIL some win32 tests that are now passingDouglas Gregor2010-02-211-1/+0
| | | | llvm-svn: 96759
* XFAIL some of the c-index-test tests on Windows, where they are failing ↵Douglas Gregor2010-02-191-0/+1
| | | | | | inexplicably llvm-svn: 96644
* Re-apply my diagnostics-capture patch for CIndex, with some tweaks toDouglas Gregor2010-02-181-1/+1
| | | | | | try to address the msvc failures. llvm-svn: 96624
* Revert my CIndex diagnostic changes (r96603, 96606, 96607), which wereDouglas Gregor2010-02-181-1/+1
| | | | | | breaking the msvc9 builder for unknown reasons. llvm-svn: 96618
* Introduce CIndex API functions for displaying a diagnostic, with someDouglas Gregor2010-02-181-1/+1
| | | | | | | | | | | knobs to control formatting. Eventually, I'd like to merge the implementation of this code with the TextDiagnosticPrinter, so that it's easy for CIndex clients to produce beautiful diagnostics like the clang compiler does. Use this new function to display diagnostics within c-index-test. llvm-svn: 96603
* c-index-test: Unify syntax for printing extents. Yes, there were 4.Daniel Dunbar2010-02-141-3/+3
| | | | llvm-svn: 96158
* When printing diagnostics in c-index-test, also print source rangesDouglas Gregor2010-01-291-6/+6
| | | | | | | | and fix-it information, so we can see everything in one place. Along the way, fix a few bugs with deserialization and query of diagnostics in CIndex. llvm-svn: 94768
* Introduce serialization and deserialization of diagnostic informationDouglas Gregor2010-01-281-0/+16
so that CIndex can report diagnostics through the normal mechanisms even when executing Clang in a separate process. This applies both when performing code completion and when using ASTs as an intermediary for clang_createTranslationUnitFromSourceFile(). The serialized format is not perfect at the moment, because it does not encapsulate macro-instantiation information. Instead, it maps all source locations back to the instantiation location. However, it does maintain source-range and fix-it information. To get perfect fidelity from the serialized format would require serializing a large chunk of the source manager; at present, it isn't clear if this code will live long enough for that to matter. llvm-svn: 94740
OpenPOWER on IntegriCloud