Displaying 6 results from an estimated 6 matches for "gendifunctiontype".
2010 Sep 06
2
[LLVMdev] More DIFactory questions - still stumped
...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 CodeGenerator::genDIFunctionType(const FunctionType * type)
{
DIDescriptorArray args;
args.push_back(genDIType(type->returnType()));
if (type->selfParam() != NULL) {
const ParameterDefn * param = type->selfParam();
// genDIParameterType() calls genDIType and then makes it a pointer
// if the underlying...
2010 Sep 07
0
[LLVMdev] More DIFactory questions - still stumped
...> false /* isDefinition */,
(...)
Hi Talin,
The only difference from what I'm doing is that I only export debug
symbols in definitions, not declarations. I may be doing wrong,
though, for multi-file compilation (haven't tested thoroughly).
> DICompositeType CodeGenerator::genDIFunctionType(const FunctionType * type)
(...)
> for (ParameterList::const_iterator it = params.begin(); it !=
> params.end(); ++it) {
> const ParameterDefn * param = *it;
> args.push_back(genDIParameterType(param->type()));
> }
Don't do that. I know it looks right, but it'...
2010 Sep 07
2
[LLVMdev] More DIFactory questions - still stumped
...>
> Hi Talin,
>
> The only difference from what I'm doing is that I only export debug
> symbols in definitions, not declarations. I may be doing wrong,
> though, for multi-file compilation (haven't tested thoroughly).
>
>
>
> > DICompositeType CodeGenerator::genDIFunctionType(const FunctionType *
> type)
> (...)
> > for (ParameterList::const_iterator it = params.begin(); it !=
> > params.end(); ++it) {
> > const ParameterDefn * param = *it;
> > args.push_back(genDIParameterType(param->type()));
> > }
>
> Don't...
2010 Sep 07
0
[LLVMdev] More DIFactory questions - still stumped
...> Hi Talin,
>
> The only difference from what I'm doing is that I only export debug
> symbols in definitions, not declarations. I may be doing wrong,
> though, for multi-file compilation (haven't tested thoroughly).
>
>
>
> > DICompositeType CodeGenerator::genDIFunctionType(const FunctionType * type)
> (...)
> > for (ParameterList::const_iterator it = params.begin(); it !=
> > params.end(); ++it) {
> > const ParameterDefn * param = *it;
> > args.push_back(genDIParameterType(param->type()));
> > }
>
> Don't do...
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 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