Sorry, I meant DIBuilder.<br><br><div class="gmail_quote">On Fri, Feb 18, 2011 at 1:32 PM, Talin <span dir="ltr"><<a href="mailto:viridia@gmail.com">viridia@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

I didn't know DIFactory existed until you mentioned it just now.<div><br></div><div>And if folks are adding brand new classes to LLVM, can we not follow the naming conventions in the developer guidelines?<br><div><div>

<div></div><div class="h5"><br><div class="gmail_quote">
On Fri, Feb 18, 2011 at 5:14 AM, Renato Golin <span dir="ltr"><<a href="mailto:rengolin@systemcall.org" target="_blank">rengolin@systemcall.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


Seems the last use of DIFactory in LLVM/Clang is in:<br>
<br>
clang/lib/CodeGen/CGDebugInfo.cpp to get the enums<br>
llvm::DIFactory::OpDeref and llvm::DIFactory::OpPlus.<br>
<br>
Shouldn't this be moved to DIBuilder and remove the dependency completely?<br>
<br>
--<br>
cheers,<br>
--renato<br>
<br>
<a href="http://systemcall.org/" target="_blank">http://systemcall.org/</a><br>
<br>
Reclaim your digital rights, eliminate DRM, learn more at<br>
<a href="http://www.defectivebydesign.org/what_is_drm" target="_blank">http://www.defectivebydesign.org/what_is_drm</a><br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a>         <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
</blockquote></div><br><br clear="all"><br></div></div>-- <br>-- Talin<br>
</div></div>
</blockquote></div><br><br clear="all"><br>-- <br>-- Talin<br>