similar to: [LLVMdev] generating !llvm.dbg.sp

Displaying 20 results from an estimated 3000 matches similar to: "[LLVMdev] generating !llvm.dbg.sp"

2012 Feb 09
0
[LLVMdev] generating !llvm.dbg.sp
On Feb 9, 2012, at 7:17 AM, "Bendersky, Eli" <eli.bendersky at intel.com> wrote: > Hello, > > According to the documentation here -http://llvm.org/docs/SourceLevelDebugging.html: > > >> All subprogram descriptors are collected by a named metadata!llvm.dbg.sp. > > LLVM seems to have lost the ability to generate this metadata node in r126871, when
2012 Feb 13
2
[LLVMdev] generating !llvm.dbg.sp
Thanks. Note that there are still a few references to this MDNode scattered throughout the code-base, so if it's no longer being generated, there may be some bugs lurking there. Eli From: Devang Patel [mailto:dpatel at apple.com] Sent: Thursday, February 09, 2012 19:36 To: Bendersky, Eli Cc: llvmdev at cs.uiuc.edu Subject: Re: generating !llvm.dbg.sp On Feb 9, 2012, at 7:17 AM,
2012 Feb 13
2
[LLVMdev] generating !llvm.dbg.sp
Thanks Eric. I know some of the references are in the code used for backward compatibility. - Devang On Feb 13, 2012, at 9:21 AM, Eric Christopher <echristo at apple.com> wrote: > Thanks. I'll get them. :) > > -eric > > On Feb 13, 2012, at 1:41 AM, Bendersky, Eli wrote: > >> Thanks. Note that there are still a few references to this MDNode scattered throughout
2012 Feb 13
0
[LLVMdev] generating !llvm.dbg.sp
Thanks. I'll get them. :) -eric On Feb 13, 2012, at 1:41 AM, Bendersky, Eli wrote: > Thanks. Note that there are still a few references to this MDNode scattered throughout the code-base, so if it’s no longer being generated, there may be some bugs lurking there. > > Eli > > > From: Devang Patel [mailto:dpatel at apple.com] > Sent: Thursday, February 09, 2012
2012 Feb 14
0
[LLVMdev] generating !llvm.dbg.sp
Eric, Devang, FYI exactly the same applies for llvm.dbg.gv - it's also still listed in the docs and in various places throughout the code, although no longer generated. Eli From: Devang Patel [mailto:dpatel at apple.com] Sent: Monday, February 13, 2012 19:26 To: Eric Christopher Cc: Bendersky, Eli; llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] generating !llvm.dbg.sp Thanks Eric. I know
2012 Feb 21
1
[LLVMdev] generating !llvm.dbg.sp
I've opened PR 12050 to track the problem with llvm.dbg.gv Eli From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Bendersky, Eli Sent: Tuesday, February 14, 2012 13:45 To: Devang Patel; Eric Christopher Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] generating !llvm.dbg.sp Eric, Devang, FYI exactly the same applies for llvm.dbg.gv - it's also
2010 Sep 07
2
[LLVMdev] More DIFactory questions - still stumped
On 7 September 2010 16:49, Devang Patel <dpatel at apple.com> wrote: > Your recent changes mentioned below would change correctness of debug info, > but it would unlikely to impact structure of DWARF generated. And somehow, > this structure is invalid in your case. I was hoping for a quick-fix on the assumptions of DwarfDebug about Subprograms' MDNodes, but it might be
2011 Sep 05
2
[LLVMdev] Internal API Changes
On Sun, Sep 4, 2011 at 11:38 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi Talin, > > > So, I just sync'd to LLVM tip and added the call to > DIBuilder::finalize(). But > > even with that change I am getting an error when I try to run llc: > > > > Assertion failed: (TheCU && "Unable to find compile unit!"), function > >
2011 Sep 05
2
[LLVMdev] Internal API Changes
So, I just sync'd to LLVM tip and added the call to DIBuilder::finalize(). But even with that change I am getting an error when I try to run llc: Assertion failed: (TheCU && "Unable to find compile unit!"), function endFunction, file /Users/talin/Projects/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp, line 1306. And looking at the .bc dissassembly, I see there are indeed
2010 Oct 10
2
[LLVMdev] More DIFactory questions - still stumped
BTW, the reason I stopped responding to this thread is not because I solved the problem, but because I simply gave up and decided to work on other things for a while since I was making no progress. Having finished those other things (the stack crawler, for one), I'm hoping that time and a fresh start will yield better results. Unfortunately after about a day spent reviewing old llvm-dev
2010 Sep 05
0
[LLVMdev] More DIFactory questions - still stumped
On 5 September 2010 19:32, Talin <viridia at gmail.com> wrote: > I've carefully studied the source code of CGDebugInfo in clang as a working > example. One puzzlement is that there's a discrepancy between what the > "source level debugging with LLVM" docs say and what clang does: According > to the docs, DW_TAG_formal_parameter is used to specify a formal
2009 Oct 21
1
[LLVMdev] A few more questions about DIFactory and source-level debugging.
Well, I am much happier now that I understand about dsymutil, and can actually step through my program in gdb. However, there are still some issues that are puzzling me. 1) First off, the debugger appears to stop at odd points. The IR for my main function looks correct to me: define i32 @"main(tart.core.Array[tart.core.String])->int"(%"tart.core.Array[tart.core.String]"*
2010 Sep 05
2
[LLVMdev] More DIFactory questions - still stumped
I hate to be a nag, but after several days of working on this I am still utterly stumped. Let me recap the situation as it currently stands: I'm trying to write code that generates DWARF debugging information for my compiler using DIFactory and friends. Unfortunately the information I am generating appears to be invalid, but I can't figure out the cause. Based on the advice in the
2010 Sep 07
0
[LLVMdev] More DIFactory questions - still stumped
On Sep 7, 2010, at 9:11 AM, Renato Golin wrote: > On 7 September 2010 16:49, Devang Patel <dpatel at apple.com> wrote: >> Your recent changes mentioned below would change correctness of debug info, >> but it would unlikely to impact structure of DWARF generated. And somehow, >> this structure is invalid in your case. > > I was hoping for a quick-fix on the
2011 Sep 05
0
[LLVMdev] Internal API Changes
Hi Talin, > So, I just sync'd to LLVM tip and added the call to DIBuilder::finalize(). But > even with that change I am getting an error when I try to run llc: > > Assertion failed: (TheCU && "Unable to find compile unit!"), function > endFunction, file > /Users/talin/Projects/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp, line 1306. > > And looking at
2011 Sep 05
0
[LLVMdev] Internal API Changes
Hi Talin, I mentioned it because the error message you are getting is identical (IIRC) to the error message being produced by llvm-gcc before this patch went in. Ciao, Duncan. On 05/09/11 11:21, Talin wrote: > On Sun, Sep 4, 2011 at 11:38 PM, Duncan Sands <baldrick at free.fr > <mailto:baldrick at free.fr>> wrote: > > Hi Talin, > > > So, I just
2011 Sep 06
1
[LLVMdev] Internal API Changes
Yup. Now, the debug info nodes do not refer to compile unit. - Devang On Sep 5, 2011, at 2:23 AM, Duncan Sands wrote: > Hi Talin, I mentioned it because the error message you are getting is > identical (IIRC) to the error message being produced by llvm-gcc before > this patch went in. > > Ciao, Duncan. > > On 05/09/11 11:21, Talin wrote: >> On Sun, Sep 4, 2011 at
2010 Oct 11
0
[LLVMdev] More DIFactory questions - still stumped
On Sun, Oct 10, 2010 at 9:54 AM, Talin <viridia at gmail.com> wrote: > BTW, the reason I stopped responding to this thread is not because I solved > the problem, but because I simply gave up and decided to work on other > things for a while since I was making no progress. Having finished those > other things (the stack crawler, for one), I'm hoping that time and a fresh >
2010 Jul 14
2
[LLVMdev] DIFactory
Hi All, Is there any documentation on how to use DIFactory to generate basic debug info? It seems similar enough to IRBuilder but working with objects (rather than pointers) and that's raising some issues. Also, am I supposed to run the ModuleDebugInfoPrinterPass manually, or it gets printed automatically when I WriteBitcodeToFile? -- cheers, --renato http://systemcall.org/ Reclaim
2011 Feb 02
1
[LLVMdev] reference to %llvm.dbg.variable in source level debug docs
>> There are a couple of references made to %llvm.dbg.variable, which >> isn't defined anywhere. It it an intrinsic? A global? Could it be a >> relic from the old debug info docs (where it *is* defined?). The same >> goes for llvm.dbg.derivedtype and llvm.dbg.subrange which are also >> referenced but not defined. > > It was a stale reference. I fixed the