Displaying 9 results from an estimated 9 matches for "dwarfdebuglin".
Did you mean:
dwarfdebugline
2017 Jun 30
3
Building llvm with clang and lld on arm and the llvm arm backend relocation on position independent code
...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...
2017 Jun 28
2
Building llvm with clang and lld on arm and the llvm arm backend relocation on position independent code
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:
2013 Jan 11
2
[LLVMdev] DebugInfo library and relocations in the .debug_line section
...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 ju...
2013 Jan 11
0
[LLVMdev] DebugInfo library and relocations in the .debug_line section
...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 soun...
2017 Apr 27
2
[DWARFv5] The new line-table section header
...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...
2013 Feb 06
0
[LLVMdev] [llvm] r174463 - Initial support for DWARF CFI parsing and dumping in LLVM
...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;
>...
2013 Jan 10
0
[LLVMdev] DebugInfo library and relocations in the .debug_line section
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,
2013 Jan 10
2
[LLVMdev] DebugInfo library and relocations in the .debug_line section
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
2015 Jul 29
1
[LLVMdev] Error when i am using command make -j4 command in cygwin to compile safecode
...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 LiveS...