search for: cgdebuginfo

I'm probably missing something simple here but in: CGDebugInfo.h: std::vector<std::pair<void *, llvm::WeakVH> >ReplaceMap; but then in CGDebugInfo.cpp: llvm::DIType TC = getTypeOrNull(Ty); void * v = Ty.getAsOpaquePtr(); std::pair<void *, llvm::WeakVH> tmp = std::make_pair(v, TC); if (TC.Verify() && TC.isForwardDecl()...

This patch adds EmitTypeAuxAttribute() function to CGDebugInfo, which allows other parts of clang issue auxiliary information through an enumeration type in Dwarf information. For example, by calling DI->EmitTypeAuxAttribute(type, "ID", 1234); We can get following information in dwarf: <1><3f>: Abbrev Number: 3 (DW_TAG_structure_...

On 09.08.2012, at 19:43, "Gaster, Benedict" <Benedict.Gaster at amd.com> wrote: > I’m probably missing something simple here but in: > > CGDebugInfo.h: > > std::vector<std::pair<void *, llvm::WeakVH> >ReplaceMap; > > but then in > > CGDebugInfo.cpp: > > llvm::DIType TC = getTypeOrNull(Ty); > > void * v = Ty.getAsOpaquePtr(); > std::pair<void *, llvm::WeakVH> tmp = std::make_p...

...ultiprog 2013: http://multiprog.ac.upc.edu/ > -----Original Message----- > From: Benjamin Kramer [mailto:benny.kra at gmail.com] > Sent: Thursday, August 09, 2012 10:55 AM > To: Gaster, Benedict > Cc: llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] Type inconsistency in LLVM 3.1: CGDebugInfo.cpp > > > On 09.08.2012, at 19:43, "Gaster, Benedict" <Benedict.Gaster at amd.com> > wrote: > > > I'm probably missing something simple here but in: > > > > CGDebugInfo.h: > > > > std::vector<std::pair<void *, llvm::WeakVH...

On Thu, Oct 1, 2009 at 8:34 PM, Talin <viridia at gmail.com> wrote: > Here is a patch that does just that. This does not work. I'm getting llvm/tools/clang/lib/CodeGen/CGDebugInfo.cpp: In member function ‘llvm::DIType clang::CodeGen::CGDebugInfo::CreateQualifiedType(clang::QualType, llvm::DICompileUnit)’: /Users/yash/clean/llvm/tools/clang/lib/CodeGen/CGDebugInfo.cpp:225: error: call of overloaded ‘CreateDerivedType(unsigned int&, llvm::DICompileUnit&, const char [1]...

...gCodeGen.a(ObjectFilePCHContainerOperations.cpp.o): In function `(anonymous namespace)::PCHContainerGenerator::DebugTypeVisitor::VisitImportDecl(clang::ImportDecl*)': /home/rdp/dev/llvm/llvm/tools/clang/lib/CodeGen/ObjectFilePCHContainerOperations.cpp:76: undefined reference to `clang::CodeGen::CGDebugInfo::EmitImportDecl(clang::ImportDecl const&)' ../../../../lib/libclangCodeGen.a(ObjectFilePCHContainerOperations.cpp.o): In function `(anonymous namespace)::PCHContainerGenerator::DebugTypeVisitor::VisitTypeDecl(clang::TypeDecl*)': /home/rdp/dev/llvm/llvm/tools/clang/lib/CodeGen/ObjectFile...

On Mon, Nov 2, 2015 at 8:38 AM, Adrian Prantl via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Looking at the code in clang CGDebugInfo just passes through the width of > the type as it is described by the TypeInfo, which in turn is defined by > the Target. At the moment I do not understand why an x86_fp80 is reported > to be 128 bits wide. (Since it’s a type natively supported by LLVM > http://llvm.org/docs/LangRef.htm...

...-DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd9.0\" -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/tmp\" -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -stdlib=libc++ -std=c++11 -c /usr/src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen/CGDebugInfo.cpp -o CGDebugInfo.o /usr/src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen/CGDebugInfo.cpp:1695:16: error: no matching member function for call to 'push_back' ReplaceMap.push_back(std::make_pair(Ty.getAsOpaquePtr(), TC)); ~~~~~~~~~~~^~~~~~~~~ /usr/in...

...On Wed, Oct 7, 2009 at 9:50 AM, Devang Patel <devang.patel at gmail.com> wrote: > On Thu, Oct 1, 2009 at 8:34 PM, Talin <viridia at gmail.com> wrote: > > Here is a patch that does just that. > > This does not work. I'm getting > > llvm/tools/clang/lib/CodeGen/CGDebugInfo.cpp: In member function > ‘llvm::DIType > clang::CodeGen::CGDebugInfo::CreateQualifiedType(clang::QualType, > llvm::DICompileUnit)’: > /Users/yash/clean/llvm/tools/clang/lib/CodeGen/CGDebugInfo.cpp:225: > error: call of overloaded ‘CreateDerivedType(unsigned int&, > llvm::DICo...

...hereas I've not been looking at/analyzing LTO size costs. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131115/d922ab4c/attachment.html> -------------- next part -------------- diff --git lib/CodeGen/CGDebugInfo.cpp lib/CodeGen/CGDebugInfo.cpp index 9b131fd..c75fd05 100644 --- lib/CodeGen/CGDebugInfo.cpp +++ lib/CodeGen/CGDebugInfo.cpp @@ -138,7 +138,7 @@ void CGDebugInfo::setLocation(SourceLocation Loc) { /// getContextDescriptor - Get context info for the decl. llvm::DIScope CGDebugInfo::getContextDesc...

Hi All, I have question about 'isUnsignedDIType' function on 'llvm/lib/CodeGen/AsmPrinter/DwarfUnit.cpp' When we want to generate object file with dwarf debug format, clang can generates 'DW_ATE_lo_user' encoding for complex integer type as follow: "clang/lib/CodeGen/CGDebugInfo.cpp" llvm::DIType *CGDebugInfo::CreateType(const ComplexType *Ty) { ... if (Ty->isComplexIntegerType()) Encoding = llvm::dwarf::DW_ATE_lo_user; ... There is a assert for DIBasicType's enconding in the 'isUnsignedDIType' function and it generates assertion for 'DW_ATE_...

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 parameter > in a function type des...

I'm in the process of teaching the Verifier to validate that the size of debug info variable and the described value matches (already caught a couple of bugs, both in my frontend and in LLVM itself). However, I've run into the following: size of passed value (80) does not match size of declared variable (128) call void @llvm.dbg.declare(metadata x86_fp80* %x, metadata !11, metadata

On Mon, Nov 9, 2015 at 4:00 AM, Aboud, Amjad <amjad.aboud at intel.com> wrote: > I found a way to skip representing macros in AST and create them directly > in CGDebugInfo through PPCallbacks during preprocessing. > > To do that, I needed to extend ASTConsumer interface with this extra > method: > > > > /// If the consumer is interested in notifications from Preprocessor, > > /// for example: notifications on macro definitions, etc., it...

...declarations of parameters and local variables, which doesn't prevent the problem from occurring. (Since my current understanding is that CIE and FDE are used to describe the call frame, I'm trying to simplify the problem as much as possible.) 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 parameter in a function type descriptor, but accordi...

...21 AM, David Blaikie via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > >> On Mon, Nov 9, 2015 at 4:00 AM, Aboud, Amjad <amjad.aboud at intel.com> >> wrote: >> >>> I found a way to skip representing macros in AST and create them >>> directly in CGDebugInfo through PPCallbacks during preprocessing. >>> >>> To do that, I needed to extend ASTConsumer interface with this extra >>> method: >>> >>> >>> >>> /// If the consumer is interested in notifications from Preprocessor, >>> >...

> Right - I was wondering if CGDebugInfo already implemented PPCallbacks or was otherwise being notified of PPCallback related things, possibly through a layer or two of indirection. I checked the approach of skipping representing macros in AST, and communicate them directly from Parser to CGDebugInfo. However, I could not find a way to...

Devang Patel wrote: > Hi Richard, > > How do you produce this LLVM assembly? In newest form, > llvm.dbg.func_start intrinsic is not used. > - > Devang > Hi Devang, The assembly is disassembled from bitcode that I create. I must be using obsolete remnants of the API. I'm calling EmitFunctionStart(), EmitStopPoint(), etc. What should I be using? -Rich

...: > > Adrian, this appears to generate, in my example below, the return type for > the external function (“foo” below) but does not generate a (in Dwarf) > DW_TAG_Subprogram which binds that type to the name. Is that expected? > We are probably not visiting forward declarations in CGDebugInfo. You would probably need to visit them and call something like CGDebugInfo::getFunctionForwardDeclaration() on each declaration. -- adrian

...sary. If you break the reference to the type itself, it won't matter that sometimes the type is defined in a different place, will it? For example, the following patch (actually only the first part is needed for this specific test case) causes the assertion not to fire: diff --git lib/CodeGen/CGDebugInfo.cpp lib/CodeGen/CGDebugInfo.cpp index 048c8f8..2bded23 100644 --- lib/CodeGen/CGDebugInfo.cpp +++ lib/CodeGen/CGDebugInfo.cpp @@ -771,7 +771,7 @@ llvm::DIType CGDebugInfo::CreateType(const FunctionType *Ty, SmallVector<llvm::Value *, 16> EltTys; // Add the result type at least. - EltT...