search for: dwarfdebugline

...Pistocchi <apukfreelance at gmail.com> wrote: > Hi, I tried patching and rebuilding and now I get this error. Did I miss anything? > > /home/yawmoo/Desktop/clfs/sources/llvm/tools/lld/ELF/InputFiles.cpp:82:23: error: > no matching constructor for initialization of 'llvm::DWARFDebugLine' > DwarfLine.reset(new DWARFDebugLine(&Dwarf.getLineSection().Relocs)); > ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > /home/yawmoo/Desktop/clfs/sources/llvm/include/llvm/DebugInfo/DWARF/DWARFDebugLine.h:27:7: note: > candidate constructor (the i...

The bottom of the bug has the revision numbers (e.g. D34035). That one corresponds to e.g. https://reviews.llvm.org/D34035 There's also https://reviews.llvm.org/D34634 which contains all of Peter's patches, but it's not going to rebase cleanly once the individual patches start going in. On 6/28/17, 10:56 AM, "Alessandro Pistocchi" <apukfreelance at gmail.com> wrote:

...ged for the .debug_line section, but I suppose that was mostly laziness on my part, hoping that you had a plan that you could just spell out for me. Having overcome my laziness a bit today and looked at the code some more, it looks like I'd need to pass the new map (however it was stored) into DWARFDebugLine and have that class use it in its parseStatementTable and associated methods. It looks like it would take a bit of thought to figure out which fields might be candidates for relocation and which wouldn't, but I suppose that's manageable. Does this sound basically correct? Or should I jus...

...ziness on my part, hoping that you had a plan that you > could just spell out for me.**** > > ** > Oh sorry :) > ** > > Having overcome my laziness a bit today and looked at the code some more, > it looks like I’d need to pass the new map (however it was stored) into > DWARFDebugLine and have that class use it in its parseStatementTable and > associated methods. It looks like it would take a bit of thought to figure > out which fields might be candidates for relocation and which wouldn’t, but > I suppose that’s manageable.**** > > ** ** > > Does this sound...

...en it needs a different relocation map. It's only the string data that causes a problem; all the other kinds of data in the file table are constants, and retrieving constants with DWARFFormValue is no problem. I think the right tactic is a "top-down" approach, starting by teaching DWARFDebugLine to parse a v5 line-table header but support only DW_FORM_string for the paths. This should let me use an unmodified DWARFFormValue to parse the directory and file tables. >From there, teaching DWARFFormValue to handle DW_FORM_strp from the .debug_line section should be pretty well motivated...

...iginal) >> +++ llvm/trunk/lib/DebugInfo/DWARFContext.h Tue Feb 5 17:30:58 2013 >> @@ -12,6 +12,7 @@ >> >> #include "DWARFCompileUnit.h" >> #include "DWARFDebugAranges.h" >> +#include "DWARFDebugFrame.h" >> #include "DWARFDebugLine.h" >> #include "DWARFDebugRangeList.h" >> #include "llvm/ADT/OwningPtr.h" >> @@ -29,6 +30,7 @@ class DWARFContext : public DIContext { >> OwningPtr<DWARFDebugAbbrev> Abbrev; >> OwningPtr<DWARFDebugAranges> Aranges; >&...

On Thu, Jan 10, 2013 at 3:13 PM, Kaylor, Andrew <andrew.kaylor at intel.com>wrote: > Actually, MCJIT doesn’t perform relocations on debug sections. I’m not > sure that would matter anyway. The place where I’m handling the debug > information is outside MCJIT and the MCJIT relocation code isn’t really > accessible at that point.**** > > ** > I know it doesn't,

Actually, MCJIT doesn't perform relocations on debug sections. I'm not sure that would matter anyway. The place where I'm handling the debug information is outside MCJIT and the MCJIT relocation code isn't really accessible at that point. Right now, when MCJIT emits an object image, it broadcasts an event to any registered listeners indicating that an object was emitted, passing

...it.cpp for Release+Asserts build llvm[2]: Compiling Object.cpp for Release+Asserts build llvm[3]: Compiling DWARFDebugInfoEntry.cpp for Release+Asserts build llvm[2]: Compiling ObjectFile.cpp for Release+Asserts build llvm[2]: Compiling LiveRegMatrix.cpp for Release+Asserts build llvm[3]: Compiling DWARFDebugLine.cpp for Release+Asserts build llvm[2]: Compiling RecordStreamer.cpp for Release+Asserts build llvm[2]: Compiling MCDwarf.cpp for Release+Asserts build llvm[2]: Compiling SymbolSize.cpp for Release+Asserts build llvm[3]: Compiling DWARFDebugLoc.cpp for Release+Asserts build llvm[2]: Compiling LiveSt...