search for: llvmdebugversion

Hi all, In LLVM documentation about source level debugging (http://www.llvm.org/releases/2.9/docs/SourceLevelDebugging.html) Subprogram descriptor is defined as: !2 = metadata !{ i32, ;; Tag = 46 + LLVMDebugVersion <http://www.llvm.org/releases/2.9/docs/SourceLevelDebugging.html#LLVMDebugVersion> ;; (DW_TAG_subprogram) i32, ;; Unused field. metadata, ;; Reference to context descriptor metadata, ;; Name metadata, ;; Display name (fully qualified C++ name) metadata, ;; MIPS link...

...> On Dec 15, 2011, at 2:32 AM, Seb wrote: > > Hi all, > > In LLVM documentation about source level debugging (http://www.llvm.org/releases/2.9/docs/SourceLevelDebugging.html) > > > Subprogram descriptor is defined as: > > !2 = metadata !{ > i32, ;; Tag = 46 + LLVMDebugVersion <http://www.llvm.org/releases/2.9/docs/SourceLevelDebugging.html#LLVMDebugVersion> > ;; (DW_TAG_subprogram) > > i32, ;; Unused field. > metadata, ;; Reference to context descriptor > metadata, ;; Name > metadata, ;; Display name (fully qualified C++...

...> > Adding a debug info version number and ignoring the debug info MDNodes > when version does not match makes sense. And changing the version number > with every release sounds reasonable. > > One implementation is > 1> completely get rid of version number in the tag > LLVMDebugVersion is only used in two places and we should be able to > remove it. > include/llvm/DebugInfo.h: return getUnsignedField(0) & > ~LLVMDebugVersionMask; > lib/IR/DIBuilder.cpp: assert((Tag & LLVMDebugVersionMask) == 0 && > lib/IR/DIBuilder.cpp: return >...

...ignoring the debug info MDNodes >>> when version does not match makes sense. And changing the version number >>> with every release sounds reasonable. >>> >>> One implementation is >>> 1> completely get rid of version number in the tag >>> LLVMDebugVersion is only used in two places and we should be able to >>> remove it. >>> include/llvm/DebugInfo.h: return getUnsignedField(0) & >>> ~LLVMDebugVersionMask; >>> lib/IR/DIBuilder.cpp: assert((Tag & LLVMDebugVersionMask) == 0 && >>>...

...obvious diff if > still huge. > Adding a debug info version number and ignoring the debug info MDNodes when version does not match makes sense. And changing the version number with every release sounds reasonable. One implementation is 1> completely get rid of version number in the tag LLVMDebugVersion is only used in two places and we should be able to remove it. include/llvm/DebugInfo.h: return getUnsignedField(0) & ~LLVMDebugVersionMask; lib/IR/DIBuilder.cpp: assert((Tag & LLVMDebugVersionMask) == 0 && lib/IR/DIBuilder.cpp: return ConstantInt::get(Type::getInt3...

On Dec 15, 2011, at 2:32 AM, Seb wrote: > Hi all, > > In LLVM documentation about source level debugging (http://www.llvm.org/releases/2.9/docs/SourceLevelDebugging.html) > > > Subprogram descriptor is defined as: > > !2 = metadata !{ > i32, ;; Tag = 46 + LLVMDebugVersion > ;; (DW_TAG_subprogram) > > i32, ;; Unused field. > metadata, ;; Reference to context descriptor > metadata, ;; Name > metadata, ;; Display name (fully qualified C++ name) > metadata, ;; MIPS linkage name (for C++) > metadata, ;; Reference to f...

...MDNodes >>>> when version does not match makes sense. And changing the version number >>>> with every release sounds reasonable. >>>> >>>> One implementation is >>>> 1> completely get rid of version number in the tag >>>> LLVMDebugVersion is only used in two places and we should be able to >>>> remove it. >>>> include/llvm/DebugInfo.h: return getUnsignedField(0) & >>>> ~LLVMDebugVersionMask; >>>> lib/IR/DIBuilder.cpp: assert((Tag & LLVMDebugVersionMask) == 0 &&a...

...info version number and ignoring the debug info MDNodes >> when version does not match makes sense. And changing the version number >> with every release sounds reasonable. >> >> One implementation is >> 1> completely get rid of version number in the tag >> LLVMDebugVersion is only used in two places and we should be able to >> remove it. >> include/llvm/DebugInfo.h: return getUnsignedField(0) & >> ~LLVMDebugVersionMask; >> lib/IR/DIBuilder.cpp: assert((Tag & LLVMDebugVersionMask) == 0 && >> lib/IR/DIBuilde...

Hello, The documentation for debug information (http://llvm.org/docs/SourceLevelDebugging.html) says the structure of block descriptors metadata is: !3 = metadata !{ i32, ;; Tag = 11 + LLVMDebugVersion (DW_TAG_lexical_block) metadata,;; Reference to context descriptor i32, ;; Line number i32 ;; Column number } However, looking at the generated metadata, there are 2 extra fields not documented here. From the source code it appears to be a link to the function holding the block, and...

Hi, I need to find out the line no info for each lexical block in the code being compiled with llc. The docs mention metadata format for debug info for lexical block is !3 = metadata !{ i32, ;; Tag = 11 + LLVMDebugVersion (DW_TAG_lexical_block) metadata, ;; Reference to context descriptor i32, ;; Line number i32 ;; Column number } So the line no. info is present as its 3rd member. I am trying to extract this line number...

...;> when version does not match makes sense. And changing the version number >>>>> with every release sounds reasonable. >>>>> >>>>> One implementation is >>>>> 1> completely get rid of version number in the tag >>>>> LLVMDebugVersion is only used in two places and we should be able to >>>>> remove it. >>>>> include/llvm/DebugInfo.h: return getUnsignedField(0) & >>>>> ~LLVMDebugVersionMask; >>>>> lib/IR/DIBuilder.cpp: assert((Tag & LLVMDebugVersionMa...

...>>>>>>> number with every release sounds reasonable. >>>>>>>>> >>>>>>>>> One implementation is >>>>>>>>> 1> completely get rid of version number in the tag >>>>>>>>> LLVMDebugVersion is only used in two places and we should be >>>>>>>>> able to remove it. >>>>>>>>> include/llvm/DebugInfo.h: return getUnsignedField(0) & >>>>>>>>> ~LLVMDebugVersionMask; >>>>>>>>>...

...sense. And changing the version >>>>>>> number with every release sounds reasonable. >>>>>>> >>>>>>> One implementation is >>>>>>> 1> completely get rid of version number in the tag >>>>>>> LLVMDebugVersion is only used in two places and we should be able >>>>>>> to remove it. >>>>>>> include/llvm/DebugInfo.h: return getUnsignedField(0) & >>>>>>> ~LLVMDebugVersionMask; >>>>>>> lib/IR/DIBuilder.cpp: asse...

...the version >>>>>>>> number with every release sounds reasonable. >>>>>>>> >>>>>>>> One implementation is >>>>>>>> 1> completely get rid of version number in the tag >>>>>>>> LLVMDebugVersion is only used in two places and we should be able >>>>>>>> to remove it. >>>>>>>> include/llvm/DebugInfo.h: return getUnsignedField(0) & >>>>>>>> ~LLVMDebugVersionMask; >>>>>>>> lib/IR/DIBu...

...oes not match makes sense. And changing the version >>>>>> number with every release sounds reasonable. >>>>>> >>>>>> One implementation is >>>>>> 1> completely get rid of version number in the tag >>>>>> LLVMDebugVersion is only used in two places and we should be able >>>>>> to remove it. >>>>>> include/llvm/DebugInfo.h: return getUnsignedField(0) & >>>>>> ~LLVMDebugVersionMask; >>>>>> lib/IR/DIBuilder.cpp: assert((Tag & LL...

...>>> number with every release sounds reasonable. >>>>>>>>>> >>>>>>>>>> One implementation is >>>>>>>>>> 1> completely get rid of version number in the tag >>>>>>>>>> LLVMDebugVersion is only used in two places and we should be >>>>>>>>>> able to remove it. >>>>>>>>>> include/llvm/DebugInfo.h: return getUnsignedField(0) & >>>>>>>>>> ~LLVMDebugVersionMask; >>>>>>...

...with every release sounds reasonable. > >>>>>>>>>> > >>>>>>>>>> One implementation is > >>>>>>>>>> 1> completely get rid of version number in the tag > >>>>>>>>>> LLVMDebugVersion is only used in two places and we should be > >>>>>>>>>> able to remove it. > >>>>>>>>>> include/llvm/DebugInfo.h: return getUnsignedField(0) & > >>>>>>>>>> ~LLVMDebugVersionMask; > >...

CodeGen, since it depends on MachineModuleInfo. On 2008-06-05, at 04:06, Talin wrote: > HyperQuantum wrote: >> I'm not a LLVM developer, but I'll give it a try... >> >> On Wed, Jun 4, 2008 at 9:12 AM, Talin <viridia at gmail.com> wrote: >> >> >>> I went and added a new file to the "Support" >>> directory (in include and

On Mon, Nov 18, 2013 at 10:55 AM, David Blaikie <dblaikie at gmail.com> wrote: > It depends a bit, also, on what kind of guarantees we need to offer. If > the guarantee when reading IR from disk is "will not crash" then there's > nothing for it but to run full debug info verification. > > On the other hand, if we can assume that some specific metadata implies

HyperQuantum wrote: > I'm not a LLVM developer, but I'll give it a try... > > On Wed, Jun 4, 2008 at 9:12 AM, Talin <viridia at gmail.com> wrote: > > >> I went and added a new file to the "Support" >> directory (in include and lib). However, when I try to compile it, it >> complains of a circular dependency error between libCore and