|
38 | 38 | <ol> |
39 | 39 | <li>Core Cppcheck |
40 | 40 | <ol> |
41 | | - <li>Add a new checker (C++)</li> |
| 41 | + <li>Add 1 new checker (C++)</li> |
42 | 42 | <li>Improved value flow (C++)</li> |
| 43 | + <li>Check for unused functions when -j is used (C++)</li> |
43 | 44 | </ol></li> |
44 | 45 | <li>Configurations |
45 | 46 | <ol> |
46 | | - <li>Write more configurations (XML)</li> |
| 47 | + <li>Add a configuration (XML)</li> |
47 | 48 | <li>Auto generate configuration (C++ / scripting) |
48 | 49 | <li>GUI for editing configurations (C++,Qt)</li> |
49 | 50 | </ol></li> |
|
58 | 59 |
|
59 | 60 | <p> |
60 | 61 | <strong>Project 1.1</strong><br> |
61 | | - <strong>Name:</strong> Add a new checker<br> |
| 62 | + <strong>Name:</strong> Add 1 new checker<br> |
62 | 63 | <strong>Skills required:</strong> C++<br> |
63 | 64 | <strong>Description:</strong> There are several tickets in our issue tracker that has ideas for new checkers. |
64 | 65 | The subtasks will be: implement a new checker, write test cases, test it against various projects. |
|
73 | 74 | after conditions, inside loops, etc. |
74 | 75 | </p> |
75 | 76 |
|
| 77 | + <p> |
| 78 | + <strong>Project 1.3</strong><br> |
| 79 | + <strong>Name:</strong> Check for unused functions when -j is used<br> |
| 80 | + <strong>Skills required:</strong> C++, threads<br> |
| 81 | + <strong>Description:</strong> Currently the check for unused functions only works when the analysis is |
| 82 | + single-threaded. When multithreaded analysis is done the check is disabled. The function usage must be |
| 83 | + stored in a thread safe way. The problem is that you don't have access to mutexes inside the check so |
| 84 | + instead of store to the same container from different threads it might be a good idea to store the |
| 85 | + function usage in different containers. And when all threads are done the results can be "merged". |
| 86 | + </p> |
76 | 87 |
|
77 | 88 | <h2>2. Configurations</h2> |
78 | 89 |
|
79 | 90 | <p> |
80 | 91 | <strong>Project 2.1</strong><br> |
81 | | - <strong>Name:</strong> Write more configurations<br> |
82 | | - <strong>Skills required:</strong> XML<br> |
83 | | - <strong>Description:</strong> More configuration files are needed for various libraries. It |
84 | | - would be most interesting to have more configurations for popular libraries. |
| 92 | + <strong>Name:</strong> Add a configuration<br> |
| 93 | + <strong>Skills required:</strong> C/C++ (not much), XML<br> |
| 94 | + <strong>Description:</strong> More configuration files are needed for various libraries. Subtasks: choose |
| 95 | + a popular library. Analyse the library functions and read API documentation. Write proper configuration |
| 96 | + file for Cppcheck. |
85 | 97 | </p> |
86 | 98 |
|
87 | 99 | <p> |
|
0 commit comments