Lines Matching full:clang
7 <title>Hacking on clang</title>
15 <h1>Hacking on Clang</h1>
19 on Clang for developers who are new to the Clang and/or LLVM
39 <p>Clang follows the
42 and to match the style of the code to that present in Clang (for example, in
45 <p>Clang has a few additional coding standards:</p>
50 upon clients and block integrating Clang as a library. Libraries should
60 <p>Both Clang and LLVM use doxygen to provide API documentation. Their
63 <li><a href="http://clang.llvm.org/doxygen">Clang</a></li>
77 <li>Many LLVM and Clang data structures provide
121 <p>Clang includes a basic regression suite in the tree which can be
122 run with <tt>make test</tt> from the top-level clang directory, or
127 <p>If you built LLVM and Clang using CMake, the test suite can be run
128 with <tt>make clang-test</tt> from the top-level LLVM directory.</p>
133 beginning indicating the Clang compile options to use, to be read
142 <ul><tt>--- Running clang tests for i686-pc-linux-gnu ---</tt></ul>
155 /home/john/llvm/tools/clang/test/SemaCXX/member-name-lookup.cpp
156 /home/john/llvm/tools/clang/test/SemaCXX/namespace-alias.cpp
157 /home/john/llvm/tools/clang/test/SemaCXX/using-directive.cpp
165 <tt>make test VG=1</tt> in the top-level clang directory.</p>
169 Test Suite</a> with clang is recommended. Currently the best way to
170 override LLVMGCC, as in: <tt>make LLVMGCC="clang -std=gnu89"
171 TEST=nightly report</tt> (make sure <tt>clang</tt> is in your PATH or use the
178 <p>The Clang test suite can be run from either Visual Studio or
195 for running the tests, "clang-test" being the root. Therefore, to
196 run the test from Visual Studio, right-click the clang-test project
215 (path to llvm)/llvm/tools/clang/test
226 (path to llvm)/llvm/tools/clang/test/(dir)/(test)
233 C:/Tools/llvm/tools/clang/test/Sema/wchar.c
241 <tt><pre>lit.py: lit.cfg:152: note: using clang: 'C:/Tools/llvm/bin/Release\\clang.EXE'
256 <p>To return changes to the Clang team, unless you have checkin
260 you are doing, such as if you are new to Clang development, you can use
265 to the llvm/tools/clang root and run:</p>
269 <p>For example, for getting the diffs of all of clang:</p>
278 so changing directory to the llvm/tools/clang directory is recommended.</p>
284 <p>The LLVM IR generation part of clang handles conversion of the
287 "codegen", and the Clang code for this lives
291 option to clang (possibly in conjunction with <tt>-o -</tt>). You
