Displaying 8 results from an estimated 8 matches for "difunct".
Did you mean:
defunct
2012 May 06
2
[LLVMdev] DebugInfo library
...umn triples from an object file, so not much
> thought went into it. However, the only user is llvm-objdump so you can be
> really free in redesigning and extending it.
>
> I'd like to keep the DWARF stuff an implementation detail so you'll likely
> end up with something like DIFunction, DIGlobalVariable, … which is then
> filled by the dwarf-implementation of DIContext. Some operations require
> traversing the DIE tree so it would be nice if the API only gives you what
> you ask for. Getting the File/Line/Column triple is a completely different
> operation in DWARF...
2012 May 06
0
[LLVMdev] DebugInfo library
...file/line/column triples from an object file, so not much thought went into it. However, the only user is llvm-objdump so you can be really free in redesigning and extending it.
>
> I'd like to keep the DWARF stuff an implementation detail so you'll likely end up with something like DIFunction, DIGlobalVariable, … which is then filled by the dwarf-implementation of DIContext. Some operations require traversing the DIE tree so it would be nice if the API only gives you what you ask for. Getting the File/Line/Column triple is a completely different operation in DWARF than fetching the f...
2012 May 05
0
[LLVMdev] DebugInfo library
...extracting file/line/column triples from an object file, so not much thought went into it. However, the only user is llvm-objdump so you can be really free in redesigning and extending it.
I'd like to keep the DWARF stuff an implementation detail so you'll likely end up with something like DIFunction, DIGlobalVariable, … which is then filled by the dwarf-implementation of DIContext. Some operations require traversing the DIE tree so it would be nice if the API only gives you what you ask for. Getting the File/Line/Column triple is a completely different operation in DWARF than fetching the f...
2012 May 05
2
[LLVMdev] DebugInfo library
Hi,
I would like to extend DebugInfo library for the purpose of using it in
AddressSanitizer/ThreadSanitizer run-time libraries.
Current interface is:
class DILineInfo {
const char *FileName;
uint32_t Line;
uint32_t Column;
...
};
class DIContext {
...
virtual DILineInfo getLineInfoForAddress(uint64_t address) = 0;
};
First, I would like to get function name associated with the
2018 Sep 19
2
Obtaining the origin function for a local var after inlining
...lar/value/addr intrinsic, then the DILocation attached to the intrinsic indirectly points there:
>
> DIScope *Scope = DILocation(dbg_intrinsic.getDebugLoc()).getScope();
> while (!isa<DISubprogram>(Scope))
> Scope = Scope->getScope();
> auto *origFunction = cast<DIFunction>(Scope);
This works, thank you!
(I had to slightly modify the code FWIW:
DILocation *DIL = dbg_intrinsic.getDebugLoc();
if (DIL) {
DIScope *Scope = DIL->getScope();
while (Scope && !isa<DISubprogram>(Scope))
Scope = Scope->getScope().resolve();...
2015 Feb 19
4
[LLVMdev] Parameter names in IR and debug info
...variable, without any actual function at all.
To build corresponding debug info, I must:
6. Build a llvm::DIArray, using llvm::getOrCreateArray, from the results of 4.
7. Build a llvm::DIComposite type for the function, using
llvm::createSubroutineType, from the result of 6.
8. Build a llvm::DIFunction using llvm::createFunction, from the result of 7.
Here, I need the formal values, with names, first, before building the function
type. This appears to imply that, in debug info, the formal names are also part
of the function type, which thus cannot be reused for a different function with
diff...
2018 Sep 17
3
Obtaining the origin function for a local var after inlining
(I think I've asked a similar question off-list a couple of times, but
never got an answer)
Hi folks,
For [K]MSAN we need to figure out which inlined function a local var
originally belonged to in the source file.
E.g. when a local buffer %buf is declared in @bar(), but @bar() is
inlined into @foo(), then there's a local %buf.i in @foo(), but we
need to determine that the local came from
2018 Sep 25
1
Obtaining the origin function for a local var after inlining
...tion attached to the intrinsic indirectly points there:
> >>
> >> DIScope *Scope = DILocation(dbg_intrinsic.getDebugLoc()).getScope();
> >> while (!isa<DISubprogram>(Scope))
> >> Scope = Scope->getScope();
> >> auto *origFunction = cast<DIFunction>(Scope);
> > This works, thank you!
> >
> > (I had to slightly modify the code FWIW:
> > DILocation *DIL = dbg_intrinsic.getDebugLoc();
> > if (DIL) {
> > DIScope *Scope = DIL->getScope();
> > while (Scope && !isa<DISubpr...