<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Thu, Sep 26, 2013 at 1:46 PM, Duncan Sands <span dir="ltr"><<a href="mailto:duncan.sands@gmail.com" target="_blank">duncan.sands@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Just to clarify this - who should create llvm.gc_root array - do you suggest to<br>
add a new __attribute__<br>
the user should specify, or to emit llvm.gc_root in frontend,<br>
</blockquote>
<br></div><div class="im">
this one: the front-end would stick globals in the array, for example using the<br>
same logic as in isLeakCheckerRoot (but of course it could use different logic<br>
if it likes).<br></div></blockquote></blockquote><div><br></div><div>So, this means pulling isLeakCheckerRoot to the frontend. Nick, WDYT of it</div><div>as the author of this function?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
</div></blockquote>
<br>
PS: Of course one of the advantages of the array approach is that if a user<br>
specified attribute turns out to be useful, then the front-end can implement<br>
that, or whatever other scheme it likes.<br>
<br>
Ciao, Duncan.<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Alexey Samsonov, MSK</div>
</div></div>