Just a follow up on this - I am still having problems, I never did figure out a solution. (I've been running with debug off for the last month so that I could get work done.)<div><br></div><div>Here's what I am seeing: I am definitely calling DIBuilder::finalize(). I even put a debug print statement right after it, so that I could be sure that the code was being executed. I also insured that it was getting called before the module was written out, and that no additional debug information gets added after it has been called.</div>
<div><br></div><div>Yet despite this, the second-to-last parameter for DW_TAG_subprogram metadata is in fact null in the module dissassembly.</div><div><br></div><div>So essentially I am completely stumped.</div><div><br>
</div><div><div><div><div><div><div class="gmail_quote">On Mon, Sep 26, 2011 at 8:01 AM, James Molloy <span dir="ltr"><<a href="mailto:James.Molloy@arm.com">James.Molloy@arm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Talin,<br>
<br>
Followup as promised: in our case we weren't calling finalize(). As this manifests itself as exactly the same assertion failure as yours I suggest you double-check you are actually calling it before any passes run on the Module.<br>
<br>
Functionally, instead of maintaining a pointer to the CU in all Debug nodes, the main CompilationUnit node has a list of subprogram nodes. It is from this that a map gets generated of Subprogram -> CU. If such a mapping doesn't exist, the assertion you see (assuming it is the same as ours) fires.<br>
<br>
First thing I'd do is check the generated metadata. Is second-to-last parameter of the DW_TAG_subprogram metadata pointing at a pointer to NULL, or is it pointing at a pointer to DW_TAG_subprogram?<br>
<br>
If the former, finalize() is not being run (or something is failing at that point). If the latter, your problem is different to ours.<br>
<br>
Hope this helps,<br>
<font color="#888888"><br>
James<br>
</font><div><div></div><div class="h5"><br>
-----Original Message-----<br>
From: <a href="mailto:llvmdev-bounces@cs.uiuc.edu">llvmdev-bounces@cs.uiuc.edu</a> [mailto:<a href="mailto:llvmdev-bounces@cs.uiuc.edu">llvmdev-bounces@cs.uiuc.edu</a>] On Behalf Of James Molloy<br>
Sent: 24 September 2011 09:38<br>
To: Devang Patel; Talin<br>
Cc: LLVM Developers Mailing List<br>
Subject: Re: [LLVMdev] DIBuilder - what's with the null compile units?<br>
<br>
Hi,<br>
<br>
Thanks for bringing this up, I'm just about to investigate an identical case which has broken our front-end. Both ours and clang generate subroutineinfo with null compilationunits, but ours asserts and clang's doesn't.<br>
<br>
I'll take a look at this on Monday, if it is a bug in LLVM.<br>
<br>
Cheers,<br>
<br>
James<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:llvmdev-bounces@cs.uiuc.edu">llvmdev-bounces@cs.uiuc.edu</a> [mailto:<a href="mailto:llvmdev-bounces@cs.uiuc.edu">llvmdev-bounces@cs.uiuc.edu</a>] On Behalf Of Devang Patel<br>
Sent: 23 September 2011 21:06<br>
To: Talin<br>
Cc: LLVM Developers Mailing List<br>
Subject: Re: [LLVMdev] DIBuilder - what's with the null compile units?<br>
<br>
<br>
On Sep 23, 2011, at 12:39 PM, Talin wrote:<br>
<br>
> Sometime about two months ago, something changed in LLVM that broke my frontend's ability to generate debug info. This was around the time that the requirement to call DIBuilder::finalize() was added (and yes, I am calling it.) Specifically, what I am seeing is an assertion failure in llc because it can't find the compile unit for a subroutine.<br>
<br>
I forgot to say earlier, that's a bug. Please file a PR with a test case.<br>
-<br>
Devang<br>
<br>
><br>
> I took a look at the code in DIBuilder.cpp, and I see that indeed it is setting the compile unit to null for all of the various descriptors being created. I assume that the intent is that these references would be filled in later - but apparently this is not happening in my case. Any idea what could be wrong?<br>
><br>
> --<br>
> -- Talin<br>
> _______________________________________________<br>
> LLVM Developers mailing list<br>
> <a href="mailto:LLVMdev@cs.uiuc.edu">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>
<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu">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>
<br>
<br>
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.<br>
<br>
<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu">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>
<br>
<br>
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>-- Talin<br>
</div></div></div></div></div>