- Feb 25, 2011
-
-
Douglas Gregor authored
llvm-svn: 126461
-
Douglas Gregor authored
llvm-svn: 126460
-
- Feb 23, 2011
-
-
NAKAMURA Takumi authored
llvm-svn: 126310
-
- Feb 20, 2011
-
-
Oscar Fuentes authored
Requires CMake 2.8.3 or newer. llvm-svn: 126094
-
- Feb 18, 2011
-
-
Daniel Dunbar authored
LLVM_INCLUDE_TESTS:=OFF, which may no longer be necessary for all I know. llvm-svn: 125985
-
Daniel Dunbar authored
Without this I get: -- -- Generating done CMake Error: Unknown Target referenced : check.deps CMake Error: Target: check-all depends on unknown target: check.deps -- llvm-svn: 125976
-
- Feb 16, 2011
-
-
NAKAMURA Takumi authored
llvm-svn: 125646
-
- Feb 15, 2011
-
-
Peter Collingbourne authored
llvm-svn: 125588
-
Jeffrey Yasskin authored
llvm-svn: 125561
-
- Feb 14, 2011
-
-
Peter Collingbourne authored
FP_CONTRACT pragmas. Patch originally by ARM. llvm-svn: 125475
-
- Feb 05, 2011
-
-
Oscar Fuentes authored
Untested, but should work :) llvm-svn: 124975
-
Oscar Fuentes authored
This may not work on build platforms that place the binaries on special folders ($build_dir/bin/Release/) such as the VS IDE and XCode. For fixing this it is necessary to add a lit.py configuration option for saying where the Clang binaries are, and apply to that path the same magit that is used with the path to the LLVM tools binary directory. Doing this requires a bit of autoconf work. llvm-svn: 124969
-
- Feb 03, 2011
-
-
NAKAMURA Takumi authored
llvm-svn: 124787
-
- Dec 10, 2010
-
-
NAKAMURA Takumi authored
llvm-svn: 121458
-
- Dec 01, 2010
-
-
Peter Collingbourne authored
llvm-svn: 120545
-
- Nov 29, 2010
-
-
NAKAMURA Takumi authored
llvm-svn: 120280
-
- Nov 11, 2010
-
-
NAKAMURA Takumi authored
test/CMakeLists.txt: Use ${LLVM_LIT_ARGS} and remove redundant arguments "-sv" and "--no-progress-bar". llvm-svn: 118777
-
- Jul 30, 2010
-
-
Daniel Dunbar authored
llvm-svn: 109816
-
- Mar 09, 2010
-
-
Ted Kremenek authored
llvm-svn: 98008
-
- Jan 26, 2010
-
-
Chandler Carruth authored
llvm-svn: 94522
-
- Dec 12, 2009
-
-
Daniel Dunbar authored
- tools/driver will be renamed to tools/clang at some point. llvm-svn: 91195
-
- Nov 22, 2009
-
-
Daniel Dunbar authored
llvm-svn: 89625
-
- Nov 08, 2009
-
-
Daniel Dunbar authored
llvm-svn: 86456
-
Daniel Dunbar authored
the 'build_config' value in at runtime using the new lit runtime user parameter feature. This simplifies things and drops a dependency on 'sed', FWIW. llvm-svn: 86421
-
- Nov 05, 2009
-
-
Daniel Dunbar authored
can always find the main clang site config (when invoked via CMake/Makefiles, at least). llvm-svn: 86139
-
- Nov 03, 2009
-
-
Daniel Dunbar authored
llvm-svn: 85881
-
- Oct 16, 2009
-
-
Douglas Gregor authored
only supporting a single stat cache. The immediate benefit of this change is that we can now generate a PCH/AST file when including another PCH file; in the future, the chain of stat caches will likely be useful with multiple levels of PCH files. llvm-svn: 84263
-
- Sep 26, 2009
-
-
Daniel Dunbar authored
llvm-svn: 82853
-
- Sep 24, 2009
-
-
Daniel Dunbar authored
visible in the log. llvm-svn: 82688
-
- Sep 22, 2009
-
-
Daniel Dunbar authored
-fsyntax-only'ing tests. llvm-svn: 82541
-
- Sep 20, 2009
-
-
Daniel Dunbar authored
llvm-svn: 82401
-
- Sep 17, 2009
-
-
Douglas Gregor authored
essence, code completion is triggered by a magic "code completion" token produced by the lexer [*], which the parser recognizes at certain points in the grammar. The parser then calls into the Action object with the appropriate CodeCompletionXXX action. Sema implements the CodeCompletionXXX callbacks by performing minimal translation, then forwarding them to a CodeCompletionConsumer subclass, which uses the results of semantic analysis to provide code-completion results. At present, only a single, "printing" code completion consumer is available, for regression testing and debugging. However, the design is meant to permit other code-completion consumers. This initial commit contains two code-completion actions: one for member access, e.g., "x." or "p->", and one for nested-name-specifiers, e.g., "std::". More code-completion actions will follow, along with improved gathering of code-completion results for the various contexts. [*] In the current -code-completion-dump testing/debugging mode, the file is truncated at the completion point and EOF is translated into "code completion". llvm-svn: 82166
-
Daniel Dunbar authored
- Move CMake to using the new test runner. - Switch Makefiles to use the lit.site.cfg.in template. - Remove explicit --path arguments, instead this gets written into the site configuration. This means running lit from the command line should use the exact same configuration as is used in 'make test', assuming it can find the site configuration file. You still need to run 'make test' (or the cmake build target equivalent) at least once. llvm-svn: 82160
-
Douglas Gregor authored
llvm-svn: 82086
-
- Jul 31, 2009
-
-
Daniel Dunbar authored
- MultiTestRunner will eventually be renamed to 'lit', for LLVM integrated tester/testing. This has the pros of being pronouncable and short. - "Project" level configuration lives in 'lit.cfg', which is also what lit uses to find the root testing directory in some cases. This can be overridden for use in project files which want to precisely specify where things are. - TestRunner.py is not longer able to be invoked directly. - Moved some code to Util.py. - Introduced a configuration object. - Cleaned up --help, removed a few not-very-useful options. - Tried not to break anything that works. :) llvm-svn: 77665
-
- Jul 27, 2009
-
-
Douglas Gregor authored
llvm-svn: 77223
-
- Jul 02, 2009
-
-
Douglas Gregor authored
declaration in the AST. The new ASTContext::getCommentForDecl function searches for a comment that is attached to the given declaration, and returns that comment, which may be composed of several comment blocks. Comments are always available in an AST. However, to avoid harming performance, we don't actually parse the comments. Rather, we keep the source ranges of all of the comments within a large, sorted vector, then lazily extract comments via a binary search in that vector only when needed (which never occurs in a "normal" compile). Comments are written to a precompiled header/AST file as a blob of source ranges. That blob is only lazily loaded when one requests a comment for a declaration (this never occurs in a "normal" compile). The indexer testbed now supports comment extraction. When the -point-at location points to a declaration with a Doxygen-style comment, the indexer testbed prints the associated comment block(s). See test/Index/comments.c for an example. Some notes: - We don't actually attempt to parse the comment blocks themselves, beyond identifying them as Doxygen comment blocks to associate them with a declaration. - We won't find comment blocks that aren't adjacent to the declaration, because we start our search based on the location of the declaration. - We don't go through the necessary hops to find, for example, whether some redeclaration of a declaration has comments when our current declaration does not. Similarly, we don't attempt to associate a \param Foo marker in a function body comment with the parameter named Foo (although that is certainly possible). - Verification of my "no performance impact" claims is still "to be done". llvm-svn: 74704
-
- Jun 18, 2009
-
-
Douglas Gregor authored
llvm-svn: 73658
-
- Jun 16, 2009
-
-
Douglas Gregor authored
InitializeAllAsmPrinters LLVM headers. Also includes some minor fixes for the CMake-based build with Xcode. llvm-svn: 73544
-
- Jun 06, 2009
-
-
Douglas Gregor authored
llvm-svn: 72977
-