<div style="font-family: arial, helvetica, sans-serif"><font size="2"><br><br><div class="gmail_quote">On Thu, Jun 21, 2012 at 1:34 PM, Dmitry Vyukov <span dir="ltr"><<a href="mailto:dvyukov@google.com" target="_blank">dvyukov@google.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="font-family:arial,helvetica,sans-serif"><font size="2"><div class="im"><div class="gmail_quote">On Thu, Jun 21, 2012 at 1:30 PM, Chandler Carruth <span dir="ltr"><<a href="mailto:chandlerc@google.com" target="_blank">chandlerc@google.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="font-family:arial,helvetica,sans-serif"><font size="2"><div class="gmail_quote"><div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-family:arial,helvetica,sans-serif"><font size="2"><div class="gmail_quote"><div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="font-family:arial,helvetica,sans-serif">
<font size="2"><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="font-family:arial,helvetica,sans-serif"><font size="2"><div class="gmail_quote">
<div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="font-family:arial,helvetica,sans-serif"><font size="2">Can we alter the build system so that when building a run-time library it modifies all .cpp files like this:<div>
namespace FOO {</div><div> <file body></div>
<div> }</div><div>This will give us essentially the same thing, but w/o system dependent object file hackery. </div><div>Maybe we can add a Clang flag to add such a namespace for us? </div></font></div></blockquote><div>
<br></div></div><div>I think this is essentially what Dmitry was talking about w/ past STLport experience. It has lots of limitations:</div></div></font></div></blockquote><div><br></div></div><div>Patching object files still sounds much scarier and harder to port. </div>
<div>I'd prefer to find a solution that involves only source files and maybe clang.</div><div>Pondering...</div><div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-family:arial,helvetica,sans-serif"><font size="2"><div class="gmail_quote"><div><br></div><div>- You can't use the normal system standard library</div></div></font></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-family:arial,helvetica,sans-serif"><font size="2"><div class="gmail_quote"><div>- You have to build the standard library from source</div>
<div>- You can't wrap certain parts of it (operator new, delete, a few other things)</div><div>- You can't re-use any C libraries (zlib for example)</div></div></font></div></blockquote></div></div></font></div></blockquote>
<div><br></div><div><br></div></div></div><div>Perhaps you are solving a broader problem. But as for asan/tsan, we currently need only symbolizer, it's separable from everything else, and can be made to not use STL.</div>
</div></font></div></blockquote><div><br></div></div></div><div>If you want to share LLVM code for the object and dwarf reading, I do not believe this to be true at all. </div></div></font></div>
</blockquote></div><br></div><div>I've already removed code for the object reading for exactly that reason, so now it's just dwarf parsing :) There are some CTL containers involved, but I think they can be replaced.</div>
</font></div></blockquote><div><br></div><div>Agree here. I hope to modify/extend this code soon anyway.</div></div><div><br></div>-- <br><div>Alexey Samsonov, MSK</div><br>
</font></div>