Lines Matching +full:docs +full:- +full:clang +full:- +full:html
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
3 <html>
5 <META http-equiv="Content-Type" content="text/html; charset=utf-8">
6 <title>Clang - Open Projects</title>
12 <!--#include virtual="menu.html.incl"-->
16 <h1>Open Clang Projects</h1>
21 <a href="https://discourse.llvm.org/c/clang">Discourse</a> for more specifics
25 <li><b>Refresh and improve Clang's documentation</b>: Clang is inconsistent
26 with documenting implementation-defined behaviors. We have significant
27 documentation in the <a href="https://clang.llvm.org/docs/LanguageExtensions.html">
32 <li><a href="https://llvm.org/docs/TableGen/">table generating</a>
34 target-specific information,</li>
36 <a href="https://github.com/llvm/llvm-project/blob/main/clang/include/clang/Basic/AttrDocs.td">
38 <li>documenting <a href="https://github.com/llvm/llvm-project/blob/main/clang/include/clang/Basic/DiagnosticDocs.td">
41 <li>documenting <a href="https://github.com/llvm/llvm-project/blob/main/clang/include/clang/Driver/Options.td">
47 <li><b>Complete the investigation into Clang's C conformance</b>: Clang's
48 <a href="c_status.html">C status page</a> contain a number of entries marked as
50 <a href="https://github.com/llvm/llvm-project/tree/main/clang/test/C">test
55 <li><b>Improve Clang's C and C++ standard conformance test coverage</b>:
56 Clang's test suite is structured such that most tests are written to provide
58 we have parsing tests in <code>clang/test/Parser</code>, and semantic analysis
59 tests in <code>clang/test/Sema*</code>, etc. We also have tests written to
60 provide coverage for the standard requirements (<code>clang/test/CXX</code> and
61 <code>clang/test/C</code>). The standards coverage is not structured in a way
68 <li><b>Complete the investigation into Clang's C and C++ Defect Report
70 determining which <a href="c_dr_status.html">C defect reports</a> and
71 <a href="cxx_dr_status.html">C++ defect reports</a> Clang implements. These
74 <a href="https://github.com/llvm/llvm-project/tree/main/clang/test/C/drs">C</a>
76 <a href="https://github.com/llvm/llvm-project/tree/main/clang/test/CXX/drs">C++</a>
79 <li><b>Bug triage</b>: Clang's <a href="https://github.com/llvm/llvm-project/issues">
83 <a href="https://llvm.org/docs/BugLifeCycle.html#triaging-bugs">bug triage and
87 <li><b>Improve build times with Clang</b>: the time it takes Clang to process a
89 better the overall user experience. It would be good to improve Clang's
93 <li><b>Improve clang-doc</b>: Clang's library-based design allows it to be used
95 <a href="https://clang.llvm.org/extra/clang-doc.html">clang-doc</a> is one
100 <li><b>Self-testing using clang</b>: There are several neat ways to
101 improve the quality of clang by self-testing. Some examples:
104 ensuring that the AST produced by clang on an input doesn't change
108 or randomly changing the input checking that clang doesn't crash and
118 <a href="cxx_status.html">C++ status report page</a> to find out what is
123 char *</tt> or <tt>std::string</tt>) various clang interfaces. This generally
126 <li><b>Configuration Manager</b>: Clang/LLVM works on a large number of
127 architectures and operating systems and can cross-compile to a similarly large
128 number of configurations, but the pitfalls of choosing the command-line
129 options, making sure the right sub-architecture is chosen and that the correct
133 in files that can later be used by Clang itself to avoid command-line options,
138 to command-line options (VFP, SSE, NEON, ARM vs. Thumb etc), triple settings etc.</p>
140 <p>The first stage is to build a CFLAGS for Clang that would produce code on the
144 independently of the Host) so that Clang can read it and not need a gazillion
145 of command-line options. Such file should be simple JSON / INI or anything that
149 <p>If you hit a bug with Clang, it is very useful for us if you reduce the code
151 do this; ask on <a href="https://discourse.llvm.org/c/clang">Discourse</a>,
157 </html>