<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Apr 17, 2013, at 10:43 AM, Eli Bendersky <<a href="mailto:eliben@google.com">eliben@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div class="gmail_extra"><br class="Apple-interchange-newline"><br><br><div class="gmail_quote">On Wed, Apr 17, 2013 at 10:23 AM, Krzysztof Parzyszek<span class="Apple-converted-space"> </span><span dir="ltr"><<a href="mailto:kparzysz@codeaurora.org" target="_blank">kparzysz@codeaurora.org</a>></span><span class="Apple-converted-space"> </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;"><div class="im">On 4/17/2013 12:15 PM, Eric Christopher 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;"><br>Give a compelling argument and I might :)<br></blockquote><br></div>The cost is the extra time spent verifying that the binaries are fresh. In my experience it has never happened that I ran "make check" on a wrong set of binaries. On the other hand, it does happen that I run "make check" repeatedly, when working on a testcase (or a set of testcases), or when I fixed something that previously caused some testcases to be XFAILed.</blockquote><div><br></div><div>If development speed / turnaround time is important for you, 'make' is the wrong solution in the first plane. Use a cmake+ninja build, which is way faster, especially for null builds (where all the build system does is make sure there's nothing new to build, or very few things to build). </div><div><br></div><div>Here's a ninja build run on a fully built debug LLVM+Clang checkout:</div><div><br></div><div><div>$ time ninja</div><div>ninja: no work to do.</div><div><br></div><div>real<span class="" style="white-space: pre;"> </span>0m0.088s</div><div>user<span class="" style="white-space: pre;"> </span>0m0.070s</div><div>sys<span class="" style="white-space: pre;"> </span>0m0.010s</div><div><br></div><div>You can't beat that with 'make' no matter what you do ;-)</div><div><br></div></div></div></div></div></blockquote><br></div><div>cmake+ninja is a non-option for many developers. Fixing that is a separate problem. We can’t just ignore problems in our configure+make build system in the meantime.</div></body></html>