search for: replacetemporary

Displaying 5 results from an estimated 5 matches for "replacetemporary".

2016 Feb 24
0
How to resolve debug info forward types
...Of(actual) * 8, alignOf(actual) * 8, 0, nullptr, elts); it = m_TmpStructDI.find(name); if (it != m_TmpStructDI.end()) { MDNode *node = /* the result from createReplaceableCompositeType earlier */ llvm::TempMDNode fwd_decl(node); m_DIBuilder->replaceTemporary(std::move(fwd_decl), result); You will need to keep a map of outstanding temporary forward declarations to do this. On Wed, Feb 24, 2016 at 5:09 PM, Rodney M. Bates via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Before metadata was separated from values, I could create a debug info...
2016 Feb 24
3
How to resolve debug info forward types
Before metadata was separated from values, I could create a debug info forward declaration and eventually resolve it using LLVMReplaceAllUsesWith in core.h. Now, I can't figure out how to resolve it. I can find no function that seems to do this. My one wild guess that giving the forward decl and the resolving decl the same UniqueId might do it is not working. I am currently using 3.6.1, but
2016 Feb 10
3
Question about an error we're now starting to get on LLVM 3.8.0rc2since
On Wed, Feb 10, 2016 at 10:50 AM, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> Is this change indeed intended as a visible API change to source code generating references to argument list values? If so, can you point me to a description of how I should change our code? Should I bug someone else about this problem? Should this API change be documented in
2016 Jan 12
2
Assertion isUniqued() failure
I'm upgrading my application to use LLVM 3.7.1 instead of 3.5.1. On one of my regression tests I am getting an assertion: /home2/djones/llvm-3.7.1.src/lib/IR/Metadata.cpp:490: void llvm::MDNode::resolve(): Assertion `isUniqued() && "Expected this to be uniqued"' failed. This occurs when finalizing debug info prior to code generation: #4 0x00007ffff4520455 in
2020 Jan 02
2
Query/Suggestions on upgrading macro infrastructure.
Hello Everyone, I would like to have your thoughts on this. Overview of the problem =================== While implementing support for the DWARFv5 debug_macro section support in LLVM. I came across these holes: - The macros infrastructure in CLANG/LLVM is inherently tied to a particular version(v4 macinfo). For instance, consider this snippet from CLANG: