<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 21, 2013, at 1:30 AM, Chandler Carruth <<a href="mailto:chandlerc@google.com">chandlerc@google.com</a>> wrote:</div><blockquote type="cite"><div dir="ltr">On Thu, Jun 20, 2013 at 6:15 PM, John McCall <span dir="ltr"><<a href="mailto:rjmccall@apple.com" target="_blank" class="cremed">rjmccall@apple.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div class="h5"><div>On Jun 20, 2013, at 12:37 AM, Chandler Carruth <<a href="mailto:chandlerc@google.com" target="_blank" class="cremed">chandlerc@google.com</a>> wrote:</div>
<blockquote type="cite"><div dir="ltr"><div class="gmail_extra">On Thu, Feb 7, 2013 at 4:37 PM, Richard Smith <span dir="ltr"><<a href="mailto:richard-llvm@metafoo.co.uk" target="_blank" class="cremed">richard-llvm@metafoo.co.uk</a>></span> wrote:<br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="overflow:hidden">cfe/trunk/test/Modules/<span>cxx</span>-<span>many</span>-<span>overloads</span>.<span>cpp</span></div>
</blockquote></div><br>Hate to dig up this test, but I wanted to mention that this is the single slowest test in the regression test suite for me at 28.84s... Wondered if you had any ideas about making it cheaper.</div></div>
</blockquote><div><br></div></div></div>Maybe it would just more appropriate in a different test suite? I believe there are a number of bots that run clang-tests, and getting 100% platform coverage doesn't seem completely imperative here.</div>
</blockquote><div><br></div><div>My suspicion (which is nothing more as I've not investigated) is that this is testable with a reasonable cheap test, and having in the basic 'make check' pattern seems worthwhile on the whole. But certainly if the first proves to not be the case, we shouldn't keep it here just for the second... </div>
</div></div></div>
</blockquote><br></div><div>If it can be made efficient, then absolutely it can and should stay. But 'make check' is never going to be an exhaustive test suite, and tying up a core for a long time (even on your presumably quite beefy machine) in a deliberate stress test feels like something that really belongs in a secondary test suite like clang-tests, especially to test a fix that honestly does not seem particularly fragile.</div><div><br></div><div>John.</div></body></html>