<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>This is a cool project! Looking forward to seeing what kinds of data we can get.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Is there a good place to discuss potential ideas for this? I don't just want to add more to the end of this thread if you think it'll get unwieldy. Perhaps bugzilla feature requests or something like that?</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">And +1 to the request for more information on the kinds of things you are planning to write. Would be great to know what you have in mind and then discuss other ideas too.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Pete<br><br>Sent from my iPhone</div><div><br>On Apr 19, 2016, at 4:40 PM, Chandler Carruth via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Tue, Apr 19, 2016 at 10:18 AM Filipe Cabecinhas via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Sun, Apr 17, 2016 at 10:46 PM, Derek Bruening via llvm-dev<br>
<<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>> wrote:<br>
> TL;DR: We plan to build a suite of compiler-based dynamic instrumentation<br>
> tools for analyzing targeted performance problems. These tools will all<br>
> live under a new "EfficiencySanitizer" (or "esan") sanitizer umbrella, as<br>
> they will share significant portions of their implementations.<br>
<br>
I will bike-shed the name as much as anyone else, but I'll stay away for now :-)<br><br>
</blockquote><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> While these tools are not addressing correctness issues like other<br>
> sanitizers, they will be sharing a lot of the existing sanitizer runtime<br>
> library support code. Furthermore, users are already familiar with the<br>
> sanitizer brand, and it seems better to extend that concept rather than add<br>
> some new term.<br>
<br>
Not the email to bike-shed the name, but I don't like "Efficiency"<br>
that much here :-)<br></blockquote><div><br></div><div>Heh, so I really do like "efficiency", much more than performance or quickness.</div><div><br></div><div>But I really do think that we shouldn't try to bikeshed the name much. IMO, while it's great to throw out ideas around better names, and certainly to point out any serious *problems* with a name, but past that I'll be happy with whatever the folks actually working on this pick.</div><div><br></div><div>I think we should all focus on the relevant technical discussion, and float any name ideas that we have, and let Derek and Qin make the final call on the name.</div><div><br></div><div>-Chandler</div></div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>LLVM Developers mailing list</span><br><span><a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a></span><br><span><a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a></span><br></div></blockquote></body></html>