| /external/clang/tools/driver/ |
| D | cc1_main.cpp | 68 std::unique_ptr<CompilerInstance> Clang(new CompilerInstance()); in cc1_main() local
72 auto PCHOps = Clang->getPCHContainerOperations(); in cc1_main()
93 Clang->getInvocation(), Argv.begin(), Argv.end(), Diags); in cc1_main()
96 if (Clang->getHeaderSearchOpts().UseBuiltinIncludes && in cc1_main()
97 Clang->getHeaderSearchOpts().ResourceDir.empty()) in cc1_main()
98 Clang->getHeaderSearchOpts().ResourceDir = in cc1_main()
102 Clang->createDiagnostics(); in cc1_main()
103 if (!Clang->hasDiagnostics()) in cc1_main()
109 static_cast<void*>(&Clang->getDiagnostics())); in cc1_main()
111 DiagsBuffer->FlushDiagnostics(Clang->getDiagnostics()); in cc1_main()
[all …]
|
| /external/clang/lib/Frontend/ |
| D | ChainedIncludesSource.cpp | 150 std::unique_ptr<CompilerInstance> Clang( in createChainedIncludesSource() local
152 Clang->setInvocation(CInvok.release()); in createChainedIncludesSource()
153 Clang->setDiagnostics(Diags.get()); in createChainedIncludesSource()
154 Clang->setTarget(TargetInfo::CreateTargetInfo( in createChainedIncludesSource()
155 Clang->getDiagnostics(), Clang->getInvocation().TargetOpts)); in createChainedIncludesSource()
156 Clang->createFileManager(); in createChainedIncludesSource()
157 Clang->createSourceManager(Clang->getFileManager()); in createChainedIncludesSource()
158 Clang->createPreprocessor(TU_Prefix); in createChainedIncludesSource()
159 Clang->getDiagnosticClient().BeginSourceFile(Clang->getLangOpts(), in createChainedIncludesSource()
160 &Clang->getPreprocessor()); in createChainedIncludesSource()
[all …]
|
| D | ASTUnit.cpp | 1042 std::unique_ptr<CompilerInstance> Clang( in Parse() local
1047 CICleanup(Clang.get()); in Parse()
1052 Clang->setInvocation(CCInvocation.get()); in Parse()
1053 OriginalSourceFile = Clang->getFrontendOpts().Inputs[0].getFile(); in Parse()
1057 Clang->setDiagnostics(&getDiagnostics()); in Parse()
1060 Clang->setTarget(TargetInfo::CreateTargetInfo( in Parse()
1061 Clang->getDiagnostics(), Clang->getInvocation().TargetOpts)); in Parse()
1062 if (!Clang->hasTarget()) in Parse()
1069 Clang->getTarget().adjust(Clang->getLangOpts()); in Parse()
1071 assert(Clang->getFrontendOpts().Inputs.size() == 1 && in Parse()
[all …]
|
| /external/clang/docs/ |
| D | ReleaseNotes.rst | 2 Clang 3.8 (In-Progress) Release Notes
13 These are in-progress notes for the upcoming Clang 3.8 release. You may
14 prefer the `Clang 3.7 Release Notes
20 This document contains the release notes for the Clang C/C++/Objective-C
22 describe the status of Clang in some detail, including major
29 For more information about Clang or LLVM, including information about
30 the latest release, please check out the main please see the `Clang Web
35 main Clang web page, this document applies to the *next* release, not
39 What's New in Clang 3.8?
42 Some of the major new features and improvements to Clang are listed
[all …]
|
| D | ClangTools.rst | 5 Clang Tools are standalone command line (and potentially GUI) tools
7 Clang as their compiler. These tools provide developer-oriented
12 primary Clang Subversion project. The rest of the tools are kept in a
14 don't. If you want to get access to the extra Clang Tools repository,
15 simply check it out into the tools tree of your Clang checkout and
17 LLVM/Clang checkout:
30 Clang Tools within the project as well as giving an introduction to some
32 document is currently focused on Clang and Clang Tool developers, not on
35 Clang Tools Organization
38 Clang Tools are CLI or GUI programs that are intended to be directly
[all …]
|
| D | Tooling.rst | 5 Clang provides infrastructure to write tools that need syntactic and semantic
20 * Clang Python Bindings
27 cursor, and don't want to learn all the nitty gritty details of Clang's AST.
31 * want full control over the Clang AST
33 Clang Plugins
36 :doc:`Clang Plugins <ClangPlugins>` allow you to run additional actions on the
41 Canonical examples of when to use Clang Plugins:
46 Use Clang Plugins when you...:
50 * need full control over the Clang AST
52 Do not use Clang Plugins when you...:
[all …]
|
| D | ExternalClangExamples.rst | 2 External Clang Examples
9 done with Clang that might serve as useful guides (or starting points) from
11 banal (but necessary) as how to set up your build to integrate Clang.
13 Clang's library-based design is deliberately aimed at facilitating use by
14 external projects, and we are always interested in improving Clang to
16 where Clang is used are:
21 If you know of (or wrote!) a tool or project using Clang, please send an
22 email to Clang's `development discussion mailing list
24 (or if you are already a Clang contributor, feel free to directly commit
40 "qconnectlint is a Clang tool for statically verifying the consistency
[all …]
|
| D | MSVCCompatibility.rst | 17 When Clang compiles C++ code for Windows, it attempts to be compatible with
20 First, Clang attempts to be ABI-compatible, meaning that Clang-compiled code
22 ABIs are particularly large and complicated, and Clang's support for MSVC's C++
27 Second, Clang implements many MSVC language extensions, such as
31 Third, MSVC accepts some C++ code that Clang will typically diagnose as
33 Clang attempts to recover and continue compiling the user's program. Most
68 base class`_. Clang does not yet support this.
75 * Debug info: :partial:`Minimal`. Clang emits both CodeView line tables
79 enabling stack traces in all modern Windows debuggers. Clang does not emit
105 * Lambdas: :good:`Mostly complete`. Clang is compatible with Microsoft's
[all …]
|
| D | IntroductionToTheClangAST.rst | 2 Introduction to the Clang AST
5 This document gives a gentle introduction to the mysteries of the Clang
7 Clang, or use tools that work based on Clang's AST, like the AST
19 Clang's AST is different from ASTs produced by some other compilers in
23 Clang's AST a good fit for refactoring tools.
25 Documentation for all Clang AST nodes is available via the generated
35 A good way to familarize yourself with the Clang AST is to actually look
36 at it on some simple example code. Clang has a builtin AST-dump mode,
49 # Clang by default is a frontend for many tools; -Xclang is used to pass
88 or to access Clang's `table of
[all …]
|
| D | index.rst | 1 .. Clang documentation master file, created by
6 .. title:: Welcome to Clang's documentation!
13 Using Clang as a Compiler
39 Using Clang as a Library
57 Using Clang Tools
|
| D | PTHInternals.rst | 13 The Clang compiler frontend, ``clang -cc1``, supports three command line
30 Alternatively, Clang's PTH files can be used as a raw "token-cache" (or
55 preprocessor state of a header file, Clang's pretokenized header files
66 implementation for Clang that also caches the work for parsing and type
68 in Clang as pretokenized header files was motivated by the following
73 Clang's lexer can handle, including C, Objective-C, and (in the early
81 machinery for PTH resides at the lower-levels of the Clang library
85 precompiled header file implementation that Clang can be directly
86 compared against) the PTH design in Clang yields several attractive
91 those of several other compilers), Clang's PTH files are architecture
[all …]
|
| D | CrossCompilation.rst | 2 Cross-compilation using Clang
8 This document will guide you in choosing the right Clang options
21 related to cross-compilation, and what main compiler options Clang provides
33 On the other hand, Clang/LLVM is natively a cross-compiler, meaning that
43 So you'll need special options to help Clang understand what target
52 Finally, not all toolchains are the same, and consequently, not every Clang
68 General Cross-Compilation Options in Clang
76 match (since Clang assumes the host triple), and the compilation will
97 that Clang doesn't know, like ``blerg``, it'll ignore and assume
117 The default is normally the common denominator, so that Clang doesn't
[all …]
|
| /external/clang/ |
| D | INSTALL.txt | 2 // Clang Installation Instructions
5 These instructions describe how to build and install Clang.
11 Clang is designed to be built as part of an LLVM build. Assuming that the LLVM
27 Assuming you installed clang at $LLVM_SRC_ROOT/tools/clang then Clang will
28 automatically be built with LLVM. Otherwise, run 'make' in the Clang source
29 directory to build Clang.
35 It is a good idea to run the Clang tests to make sure your build works
36 correctly. From inside the Clang build directory, run 'make test' to run the
40 // Step 4: Install Clang
43 From inside the Clang build directory, run 'make install' to install the Clang
[all …]
|
| D | README.txt | 5 Welcome to Clang. This is a compiler front-end for the C family of languages
9 Unlike many other compiler frontends, Clang is useful for a number of things
10 beyond just compiling code: we intend for Clang to be host to a number of
11 different source-level tools. One example of this is the Clang Static Analyzer.
13 If you're interested in more (including how to build Clang) it is best to read
16 Information on Clang: http://clang.llvm.org/
17 Building and using Clang: http://clang.llvm.org/get_started.html
18 Clang Static Analyzer: http://clang-analyzer.llvm.org/
21 If you have questions or comments about Clang, a great place to discuss them is
22 on the Clang development mailing list:
[all …]
|
| D | CODE_OWNERS.TXT | 2 particular part of Clang are reviewed, either by themself or by someone else.
3 They are also the gatekeepers for their part of Clang, with the final word on
13 D: Clang attributes
46 D: Clang Static Analyzer
50 D: Clang LLVM IR generation
54 D: All parts of Clang not covered by someone else
|
| /external/clang/lib/FrontendTool/ |
| D | ExecuteCompilerInvocation.cpp | 164 bool clang::ExecuteCompilerInvocation(CompilerInstance *Clang) { in ExecuteCompilerInvocation() argument
166 if (Clang->getFrontendOpts().ShowHelp) { in ExecuteCompilerInvocation()
177 if (Clang->getFrontendOpts().ShowVersion) { in ExecuteCompilerInvocation()
184 e = Clang->getFrontendOpts().Plugins.size(); i != e; ++i) { in ExecuteCompilerInvocation()
185 const std::string &Path = Clang->getFrontendOpts().Plugins[i]; in ExecuteCompilerInvocation()
188 Clang->getDiagnostics().Report(diag::err_fe_unable_to_load_plugin) in ExecuteCompilerInvocation()
196 if (!Clang->getFrontendOpts().LLVMArgs.empty()) { in ExecuteCompilerInvocation()
197 unsigned NumArgs = Clang->getFrontendOpts().LLVMArgs.size(); in ExecuteCompilerInvocation()
201 Args[i + 1] = Clang->getFrontendOpts().LLVMArgs[i].c_str(); in ExecuteCompilerInvocation()
209 if (Clang->getAnalyzerOpts()->ShowCheckerHelp) { in ExecuteCompilerInvocation()
[all …]
|
| /external/clang/tools/scan-build/libexec/ |
| D | ccc-analyzer | 67 my $Clang;
93 $Clang = $ENV{'CLANG_CXX'};
94 if (!defined $Clang || ! -x $Clang) { $Clang = 'clang++'; }
102 $Clang = $ENV{'CLANG'};
103 if (!defined $Clang || ! -x $Clang) { $Clang = 'clang'; }
149 my ($Clang, $Lang, $file, $Args, $HtmlDir, $ErrorType, $ofile) = @_;
169 system $Clang, @$Args, "-E", "-o", $PPFile;
192 my $OutputStream = silent_system($HtmlDir, $Clang, "-###", $mode, @$Args);
207 my ($Clang, $OriginalArgs, $AnalyzeArgs, $Lang, $Output, $Verbose, $HtmlDir,
225 $Cmd = $Clang;
[all …]
|
| /external/clang/examples/clang-interpreter/ |
| D | main.cpp | 147 CompilerInstance Clang; in main() local
148 Clang.setInvocation(CI.release()); in main()
151 Clang.createDiagnostics(); in main()
152 if (!Clang.hasDiagnostics()) in main()
156 if (Clang.getHeaderSearchOpts().UseBuiltinIncludes && in main()
157 Clang.getHeaderSearchOpts().ResourceDir.empty()) in main()
158 Clang.getHeaderSearchOpts().ResourceDir = in main()
163 if (!Clang.ExecuteAction(*Act)) in main()
|
| D | README.txt | 1 This is an example of Clang based interpreter, for executing standalone C
7 2. Constructing a Clang compiler instance, using the appropriate arguments
10 3. Invoking the Clang compiler to lex, parse, syntax check, and then generate
17 Clang compiler libraries.
|
| /external/clang/www/ |
| D | menu.html.incl | 7 <label>Clang Info</label>
20 <label>Clang Development</label>
24 <a href="/docs/InternalsManual.html">Clang Internals</a>
25 <a href="/hacking.html">Hacking on Clang</a>
29 <label>Clang Tools</label>
31 <a href="/docs/Tooling.html">Writing Clang Tools</a>
40 <a href="http://planet.clang.org/">Planet Clang</a>
58 <label>Clang Events</label>
|
| /external/clang/test/ |
| D | CMakeLists.txt | 1 # Test runner infrastructure for Clang. This configures the Clang test trees
22 option(CLANG_TEST_USE_VG "Run Clang tests under Valgrind" OFF)
74 add_lit_testsuite(check-clang "Running the Clang regression tests"
81 set_target_properties(check-clang PROPERTIES FOLDER "Clang tests")
86 set_target_properties(clang-test PROPERTIES FOLDER "Clang tests")
|
| /external/clang/tools/scan-build/bin/ |
| D | scan-build | 139 my $Clang;
1262 if (defined $Clang && -x $Clang) {
1277 …my $ExecLine = join(' ', qq/"$Clang"/, @PluginLoadCommandline_xclang, "--analyze", "-x", $lang, "-…
1296 …my $ExecLine = join(' ', qq/"$Clang"/, "-cc1", @PluginLoadCommandline, "-analyzer-checker-help", "…
1408 $Clang = Cwd::realpath("$RealBin/bin/clang") if (-f "$RealBin/bin/clang");
1409 if (!defined $Clang || ! -x $Clang) {
1410 $Clang = Cwd::realpath("$RealBin/clang") if (-f "$RealBin/clang");
1412 if (!defined $Clang || ! -x $Clang) {
1425 $Clang = `$xcrun -toolchain XcodeDefault -find clang`;
1426 chomp $Clang;
[all …]
|
| /external/clang/bindings/python/ |
| D | README.txt | 2 // Clang Python Bindings
5 This directory implements Python bindings for Clang.
7 You may need to alter LD_LIBRARY_PATH so that the Clang library can be
|
| /external/clang/docs/CommandGuide/ |
| D | index.rst | 1 Clang "man" pages
4 The following documents are command descriptions for all of the Clang tools.
5 These pages describe how to use the Clang commands and what their options are.
|
| /external/llvm/docs/ |
| D | HowToCrossCompileLLVM.rst | 2 How To Cross-Compile Clang/LLVM using Clang/LLVM
9 Clang on host machine, targeting another platform.
11 For more information on how to use Clang as a cross-compiler,
38 For more information on how to configure CMake for LLVM/Clang,
55 using Clang as a cross-compiler, you will *also* have to set ``-ccc-gcc-name``,
74 #. If you're using Clang as the cross-compiler, there is a problem in
83 This is not a problem, since Clang/LLVM libraries are statically
118 If you're using Clang as the cross-compiler, run:
144 After the LLVM/Clang has built successfully, you should install it
|