Displaying 10 results from an estimated 10 matches for "islocaltounit".
2014 Sep 11
3
[LLVMdev] patch for DragonEgg 3.3
Hi - attached is a patch to enable building DragonEgg (x86_64) for LLVM3.3 and LLVM3.4. That is, add these changes to the 3.3 release, and it becomes possible to build DragonEgg against a llvm3.4 compiler.
Regards,
Richard Gorton
Cognitive Electronics
rcgorton at cog-e.com
----------
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name:
2018 Mar 22
2
Question about debug information for global variables
..._OP_constu);
ops.push_back(offset);
ops.push_back(llvm::dwarf::DW_OP_plus);
llvm::DIExpression *DIexpr{nullptr};
auto *DIE = DIBuilder_->createExpression(ops);
auto *GVE = DIBuilder_->createGlobalVariableExpression(
cu, name, "", file, 0, type,
/* isLocalToUnit */ false, DIE);
// Add GVE as debug info to BaseAddress.
baseAddress->addDebugInfo(GVE);
I guess I'm doing something wrong, but I cannot see what it is.
Interestingly enough, when I tried a similar approach, where
BaseAddress would be a function argument and logical variables would...
2012 Dec 28
2
[LLVMdev] Newbie question(?): How to correctly create debug info, when generating IR
...;
DICompileUnit compile_unit = DICompileUnit(file);
dibuilder->createFunction(compile_unit /*Scope*/,
StringRef(function_name), StringRef(function_name),
file,
42 /* line number*/,
di_func_type,
false /*isLocalToUnit*/, true /*isDefinition*/,
42 /*ScopeLine*/
);
...
...
dibuilder->finalize();
module->dump();
To me, it seems wrong to create two compile units, one with
dibuilder->createCompileUnit()
and the other directly
DICompileUnit compile_unit =...
2018 Mar 22
0
Question about debug information for global variables
...h_back(offset);
> ops.push_back(llvm::dwarf::DW_OP_plus);
> llvm::DIExpression *DIexpr{nullptr};
> auto *DIE = DIBuilder_->createExpression(ops);
> auto *GVE = DIBuilder_->createGlobalVariableExpression(
> cu, name, "", file, 0, type,
> /* isLocalToUnit */ false, DIE);
> // Add GVE as debug info to BaseAddress.
> baseAddress->addDebugInfo(GVE);
>
> I guess I'm doing something wrong, but I cannot see what it is.
>
> Interestingly enough, when I tried a similar approach, where
> BaseAddress would be a function arg...
2018 Mar 22
2
Question about debug information for global variables
...ops.push_back(llvm::dwarf::DW_OP_plus);
>> llvm::DIExpression *DIexpr{nullptr};
>> auto *DIE = DIBuilder_->createExpression(ops);
>> auto *GVE = DIBuilder_->createGlobalVariableExpression(
>> cu, name, "", file, 0, type,
>> /* isLocalToUnit */ false, DIE);
>> // Add GVE as debug info to BaseAddress.
>> baseAddress->addDebugInfo(GVE);
>>
>> I guess I'm doing something wrong, but I cannot see what it is.
>>
>> Interestingly enough, when I tried a similar approach, where
>> BaseAddre...
2018 Mar 22
0
Question about debug information for global variables
...ck(llvm::dwarf::DW_OP_plus);
>>> llvm::DIExpression *DIexpr{nullptr};
>>> auto *DIE = DIBuilder_->createExpression(ops);
>>> auto *GVE = DIBuilder_->createGlobalVariableExpression(
>>> cu, name, "", file, 0, type,
>>> /* isLocalToUnit */ false, DIE);
>>> // Add GVE as debug info to BaseAddress.
>>> baseAddress->addDebugInfo(GVE);
>>>
>>> I guess I'm doing something wrong, but I cannot see what it is.
>>>
>>> Interestingly enough, when I tried a similar approach,...
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
2010 Sep 06
2
[LLVMdev] More DIFactory questions - still stumped
...ify());
sp = dbgFactory_.CreateSubprogram(
dbgCompileUnit_,
fn->name(),
fn->qualifiedName(),
fn->linkageName(),
dbgFile_, // genDIFile(fn),
1, // getSourceLineNumber(fn->location()),
dbgFuncType,
fn->isSynthetic() /* isLocalToUnit */,
false /* isDefinition */,
0, 0 /* VK, Index */,
DIType(),
false /* isArtificial */,
false /* isOptimized */,
f);
DASSERT(sp.Verify());
}
return sp;
}
And here's the code that generates function type descriptors:
DICompositeType Co...
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
2018 Mar 23
2
Question about debug information for global variables
...P_plus);
>>>> llvm::DIExpression *DIexpr{nullptr};
>>>> auto *DIE = DIBuilder_->createExpression(ops);
>>>> auto *GVE = DIBuilder_->createGlobalVariableExpression(
>>>> cu, name, "", file, 0, type,
>>>> /* isLocalToUnit */ false, DIE);
>>>> // Add GVE as debug info to BaseAddress.
>>>> baseAddress->addDebugInfo(GVE);
>>>>
>>>> I guess I'm doing something wrong, but I cannot see what it is.
>>>>
>>>> Interestingly enough, when I trie...