Lines Matching full:clang
7 <title>Hacking on clang</title>
18 <h1>Hacking on Clang</h1>
22 on Clang for developers who are new to the Clang and/or LLVM
43 <p>Clang follows the
46 and to match the style of the code to that present in Clang (for example, in
49 <p>Clang has a few additional coding standards:</p>
54 upon clients and block integrating Clang as a library. Libraries should
64 <p>Both Clang and LLVM use doxygen to provide API documentation. Their
67 <li><a href="http://clang.llvm.org/doxygen">Clang</a></li>
81 <li>Many LLVM and Clang data structures provide
91 data formatters for clang data structures in
103 <a href="http://llvm.org/svn/llvm-project/cfe/trunk/utils/ClangVisualizers/clang.natvis">
104 <tt>utils/ClangVisualizers/clang.natvis</tt></a> provide debugger visualizers
120 <p>Clang includes a basic regression suite in the tree which can be
121 run with <tt>make test</tt> from the top-level clang directory, or
126 <p>If you built LLVM and Clang using CMake, the test suite can be run
127 with <tt>make clang-test</tt> from the top-level LLVM directory.</p>
132 beginning indicating the Clang compile options to use, to be read
141 <pre>--- Running clang tests for i686-pc-linux-gnu ---</pre>
154 /home/john/llvm/tools/clang/test/SemaCXX/member-name-lookup.cpp
155 /home/john/llvm/tools/clang/test/SemaCXX/namespace-alias.cpp
156 /home/john/llvm/tools/clang/test/SemaCXX/using-directive.cpp
164 <tt>make test VG=1</tt> in the top-level clang directory.</p>
168 Test Suite</a> with clang is recommended. Currently the best way to
169 override LLVMGCC, as in: <tt>make LLVMGCC="clang -std=gnu89"
170 TEST=nightly report</tt> (make sure <tt>clang</tt> is in your PATH or use the
177 <p>The Clang test suite can be run from either Visual Studio or
194 for running the tests, "clang-test" being the root. Therefore, to
195 run the test from Visual Studio, right-click the clang-test project
223 --param=clang_site_config=(build dir)\tools\clang\test\lit.site.cfg
224 (path to llvm)\llvm\tools\clang\test
233 lives in (build dir)\tools\clang\test, via
234 <tt>--param=clang_site_config=(build dir)\tools\clang\test\lit.site.cfg</tt>.
242 --param=clang_site_config=(build dir)\tools\clang\test\lit.site.cfg
243 (path to llvm)\llvm\tools\clang\test\(dir)\(test)
251 --param=clang_site_config=c:\Tools\build\tools\clang\test\lit.site.cfg
252 C:\Tools\llvm\tools\clang\test\Sema\wchar.c
263 <pre>lit.py: lit.cfg:152: note: using clang: 'C:\Tools\llvm\bin\Release\clang.EXE'
278 <p>To return changes to the Clang team, unless you have checkin
281 for. clang follows <a
287 to the llvm/tools/clang root and run:</p>
291 <p>For example, for getting the diffs of all of clang:</p>
300 so changing directory to the llvm/tools/clang directory is recommended.</p>
306 <p>The LLVM IR generation part of clang handles conversion of the
309 "codegen", and the Clang code for this lives
313 option to clang (possibly in conjunction with <tt>-o -</tt>). You
