Displaying 3 results from an estimated 3 matches for "gotsection".
Did you mean:
getsection
2016 Oct 18
3
RFC: LLD: creating linker-generated sections as input sections instead of output sections
...view thread for https://reviews.llvm.org/D25627
.
Problem:
Currently, LLD creates special sections that are not just concatenations of
input sections but need link-time data generation, such as .got, .plt,
interp, .mips.options, etc., as output sections. We have OutputSectionBase
subclasses (e.g. GotSection, PltSection, etc.) to create data. Even though
this scheme works in most cases, there are a few situations that doesn't
work well as you may have noticed. Here are a issues.
- You cannot mix special sections with other types of sections.
For example, using linker scripts, you can instruct...
2016 Oct 19
2
LLD: creating linker-generated sections as input sections instead of output sections
...>Problem:
>>
>>Currently, LLD creates special sections that are not just concatenations of
>> input sections but need link-time data generation, such as .got, .plt,
>> interp, .mips.options, >etc., as output sections. We have OutputSectionBase
>> subclasses (e.g. GotSection, PltSection, etc.) to create data. Even though
>> this scheme works in most cases, >there are a few situations that doesn't
>> work well as you may have noticed. Here are a issues.
>>
> >- You cannot mix special sections with other types of sections.
>>
>>...
2016 Oct 19
3
LLD: creating linker-generated sections as input sections instead of output sections
...ly, LLD creates special sections that are not just
> concatenations of
> >>> input sections but need link-time data generation, such as .got, .plt,
> >>> interp, .mips.options, >etc., as output sections. We have
> OutputSectionBase
> >>> subclasses (e.g. GotSection, PltSection, etc.) to create data. Even
> though
> >>> this scheme works in most cases, >there are a few situations that
> doesn't
> >>> work well as you may have noticed. Here are a issues.
> >>>
> >> >- You cannot mix special sections...