Showing content from http://mail.python.org/pipermail/python-dev/attachments/20130731/0bc3afe4/attachment.html below:
<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 30, 2013 at 8:28 PM, Christian Heimes <span dir="ltr"><<a href="mailto:christian@python.org" target="_blank">christian@python.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Am 29.07.2013 21:48, schrieb Antoine Pitrou:<br>
<div class="im">> Ideally, we should run coverage runs on different systems (Unices,<br>
> Windows...) and merge the results together, so that we know which paths<br>
> are really uncovered.<br>
<br>
</div>I don't that is easily possible. The coverage report depends on GCC and<br>
its gcov extension -- so much for Windows. I also don't know if gcov<br>
supports cross-profiling on varying platforms and operating systems.<br>
<br>
By the way gcov understands preprocessor output. It doesn't report lines<br>
as uncovered when the lines or functions are #ifdef-ed out.<br></blockquote><div><br></div><div>In case are curious to try and make this work using clang, I found the flags to use at <a href="http://clang-developers.42468.n3.nabble.com/Code-coverage-on-clang-td4033066.html">http://clang-developers.42468.n3.nabble.com/Code-coverage-on-clang-td4033066.html</a> and how to make it work with lcov. I also discovered clang itself uses <a href="https://github.com/ddunbar/zcov">https://github.com/ddunbar/zcov</a> instead of lcov. This is all untested, but I didn't want to forget the links and in case someone has clang installed with compiler-rt and wants to see how it works.</div>
</div></div></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4