Displaying 3 results from an estimated 3 matches for "hasoutputseg".
2013 Sep 17
1
[LLVMdev] [lld] Handling non SHF_ALLOC sections.
...o
>> the
>> _atomToAddressMap.
>>
>> Any ideas for the proper fix here?
>>
> There is a way that we can handle this without lot of tweaks.
>
> a) Assign the debug sections part of a linker internal segment(the segment
> would not appear in the output file), hasOutputSegment will return true for
> a debug section.
>
> b) Around lines 623, in DefaultLayout, we find out if the section is
> associated with the special debug section, we add this sepecial segment to
> the list of segments
>
The problem with this is that it's not just debug. We nee...
2013 Sep 17
0
[LLVMdev] [lld] Handling non SHF_ALLOC sections.
...es(-fileoffset) and then explicitly added them to the
> _atomToAddressMap.
>
> Any ideas for the proper fix here?
There is a way that we can handle this without lot of tweaks.
a) Assign the debug sections part of a linker internal segment(the
segment would not appear in the output file), hasOutputSegment will
return true for a debug section.
b) Around lines 623, in DefaultLayout, we find out if the section is
associated with the special debug section, we add this sepecial segment
to the list of segments
c) Around lines 731 in DefaultLayout.h, we compare the segment type
against the linker...
2013 Sep 17
5
[LLVMdev] [lld] Handling non SHF_ALLOC sections.
Debug info linking is currently broken due to how we handle reading and
laying out non SHF_ALLOC sections. I posted a patch that partially fixes
this, but it's both the wrong approach and doesn't handle multiple input
files with debug info (wrong relocation values).
The first issue is representing non SHF_ALLOC atoms in the Atom model. We
currently don't have a type for this, and