<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi Dmitry,</div><div><br></div><div>I can try my best, but it would be a bit tricky to get it all finished by then...</div><div><br></div><div>-bw</div><br><div><div>On Oct 11, 2013, at 4:10 AM, Dmitry Babokin <<a href="mailto:babokin@gmail.com">babokin@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div style="">Bill,</div><div><br></div>Are there any chances that you complete it before 3.4 is branched?</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Oct 10, 2013 at 10:16 PM, Bill Wendling <span dir="ltr"><<a href="mailto:isanbard@gmail.com" target="_blank">isanbard@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Oct 10, 2013, at 4:22 AM, Dmitry Babokin <<a href="mailto:babokin@gmail.com">babokin@gmail.com</a>> wrote:<br>
<br>
> Bill,<br>
><br>
</div><div class="im">> Thanks for answering. To make sure that we are on the same page, let's agree on definitions :) Here, by fat binaries I mean the binary, where some functions are compiled for one flavor of x86, while others are compiled for another flavor of x86. I care about the usage model, which is important for LTO - a dispatch function (compiled for the least common denominator) + plus set of specialized functions for sse4, avx ,avx2 and etc., which are called by dispatch function depending on runtime cpu id check.<br>
><br>
</div>Okay. The terminology was a bit overloaded. :-)<br>
<div class="im"><br>
> lipo may help achieving this on Darwin, but it's not exactly what I need. I need a solution suitable for LTO. Actually lipo may work for me as a workaround, but I need cross platform solution.<br>
><br>
> The current solution doesn't really address this (on x86 at least), as sub-target is not recreated if feature string doesn't match the sub-target. Instead it tries to satisfy feature string requirements using existing sub-target and this leads to the fails, that were noticed by Ben. Please correct me if my understanding is wrong.<br>
><br>
> So do I understand you correctly, that your new solution supposed to solve this problem?<br>
><br>
</div>That's correct. It still needs to be implemented (of course), but that's the eventual goal.<br>
<span class="HOEnZb"><font color="#888888"><br>
-bw<br>
<br>
</font></span></blockquote></div><br></div>
</blockquote></div><br></body></html>