similar to: [LLVMdev] reference to %llvm.dbg.variable in source level debug docs

On Feb 1, 2011, at 3:58 AM, Eli Bendersky wrote: > Hello > I'm reading http://llvm.org/docs/SourceLevelDebugging.html and some > things aren't clear. > > 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

>> 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

Hi, I had a problem with LLVM not emitting local variable info, even though I had calls to llvm.dbg.define. After some tracking I found that the llvm.dbg.declare (and probably value too) have to have a !dbg !nr after them to get emitted at all. maybe someone can adjust http://llvm.org/docs/SourceLevelDebugging.html#format_common_declare that the two llvm.dbg. functions need a !dbg line info

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]"*

On Jul 27, 2012, at 2:35 AM, Carlo Kok <ck at remobjects.com> wrote: > Hi, > > I had a problem with LLVM not emitting local variable info, even though > I had calls to llvm.dbg.define. After some tracking I found that the > llvm.dbg.declare (and probably value too) have to have a !dbg !nr after > them to get emitted at all. maybe someone can adjust >

Hello Everyone, I have general question WRT llvm.dbg.value intrinsic function semantics. Under what circumstances should a frontend choose to emit(at -O0(No optimization)) llvm.dbg.value for a local variable. I saw some debuginfo code in flang(older one), sort of it choose to emit *llvm.dbg.value* for *every load operation* happening on a *local variable*. And as noted below in IR snippet it

> On Mar 30, 2020, at 4:13 AM, Jeremy Morse via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi Sourabh, > > On Mon, Mar 30, 2020 at 8:09 AM Sourabh Singh Tomar via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Under what circumstances should a frontend choose to emit(at -O0(No optimization)) llvm.dbg.value for a local variable. >> >> I

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 DIFactory was removed. Is this an intended change? We were relying in the existence of this node, and things broke once we switched

On Tue, Jan 5, 2016 at 6:59 PM, Adrian Prantl <aprantl at apple.com> wrote: > Thanks for the clarification, Paul! > Keno, just a few more questions for my understanding: > > > - Indicating that a value changed at source level (e.g. because an > > assignment occurred) > > This is done by a key call. Correct > > - Indicating that the same

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,

I will be out of the office on January 7th and will return on January 19th. I will not have access to email during this time. Please contact Karen Lavelle at klavelle at rice.edu or 713-348-2062 if you have any questions or concerns. Best regards, Annepha On Jan 6, 2016, at 3:58 PM, Adrian Prantl via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Jan 5, 2016, at 10:37 AM,

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

Adrian had proposed the following staging: 1. Remove offset argument from dbg.value 2. Unify dbg.value and dbg.declare 3. Full implementation I'm not yet sure what to do about the difference in dbg.declare semantics. For example, i think the following currently works ``` top: %x = alloca br else if: dbg.declare(%x... unreachable else: # dbg.declare still applies here ``` I think it would

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

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

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

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

Hi Martijn On Fri, Nov 13, 2009 at 4:52 AM, Martijn <martijn at martijnrutten.com> wrote: > Hello, > > I use llvm and llvm-gcc as a C-to-C transformation tool using a > modified version of the c backend, and rely on llvm debug instructions > to link back to the original source code. > > Does anyone know how to get detailed line number and variable debug > information

Hello, I use llvm and llvm-gcc as a C-to-C transformation tool using a modified version of the c backend, and rely on llvm debug instructions to link back to the original source code. Does anyone know how to get detailed line number and variable debug information at optimization levels beyond O0? Currently, I extract this debug information by compiling with -g. This works fine with

I think probably the simplest answer is that dbg.declare documents that it must point to an alloca ("This intrinsic provides information about a local element (e.g., variable). The first argument is metadata holding the alloca for the variable. ") - so it's probably best not to think too hard about what it does when that criteria is not met.