<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Issue</th>
<td>
<a href=https://github.com/llvm/llvm-project/issues/54711>54711</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>
Support per-directory index files for HTML coverage report
</td>
</tr>
<tr>
<th>Labels</th>
<td>
coverage
</td>
</tr>
<tr>
<th>Assignees</th>
<td>
</td>
</tr>
<tr>
<th>Reporter</th>
<td>
petrhosek
</td>
</tr>
</table>
<pre>
`llvm-cov` currently generates a single top-level index HTML file. This is fine for smaller projects, for larger codebases this can lead to scalability issues. For example, in case of Fuchsia the [generated index](https://storage.googleapis.com/fuchsia-artifacts/builds/8818061488465309873/coverage/coverage/coverage/coverage/coverage/index.html) has 12M and rendering this file is causing problems for browsers. To address this issues, we would like to support generating per-directory index files which is also an approach [used by lcov](https://llvm.org/reports/coverage/). What's not yet clear is whether this mode should be an opt-in controlled by an option or whether this mode should replace the current model.
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJyVk8uOnDAQRb8GNqVGjYF-LFjkoVYWmVVGytrGBThjMHKZ6em_T9lNazRSZhEJCcuWb906t6ycvrXZYW_t67Tr3CsvoVu9xznYGww4o5cBCSSQmQeLENyys_iKFsys8Q1-PD_9hN5YLOB5NAT89WZG6J0HmqS16GHx7g92gTLxLe1b6Qfe7pxGJYnVQ7zZyRksSs0lgDpppTLWhBsr0opUwIVv4pucFotRyMx8gxBcD5e1G8lIlkHImq8P1_puMWu-Z-I0hrBQVn3JxIU_Cs7LAYvBOW5KLoaKzk180N-ldtIH08vk-aJWY3VcnE7laX8o69OpPjTV_nw6VrzL1DCK_ecyeSvGMNlMnGGUBKV4AjlrYPgaPeO-c4lwIfFZYwaRprI4UUKpvLsSesbz7EBq7ZE2nHdskdQV4epWq8GaF0x012VxPjziTaLod9p4Tsn52xZtLExwHU03xvrSEpeYQS7sQPIeo16JKasb2Dg6_-Acx6pwfuClx1iTPkLg1gv4PcqQiSPB7ALcMEDHkfhY8joiZ-rvDU08LkBj6kRhdOKWsItj4ObgHU9asnLfN45__nMBdmNlh2lktnlP57bIdVvpc3WWeTDBYvtrg_U5oZhDegaPxuDea756237kMZgwrmqbtQhn--22JxLnYsvt0tTHsszHthH6XPfyeFRVLfrmcKi7EhulRFfrRpeHnF8KWmo5jkyId7iCA8lNK_ZC7Ot9KUTFM1vITssaexZXlWpQZ_UeJ2ls8Ygq921ypNaB-NAaCvR-KInMMCOmaqwv1zA63y4Y_OgIX_Jkv03e_wIFZIFn">