search for: assignvirtualaddress

...correct output: >> >> [17] .tbss NOBITS 0000000000410dec 00000dec >> 000000000000001c 0000000000000000 WAT 0 0 4 >> >> My initial idea is that 'lib/ReaderWriter/ELF/SegmentChunks.cpp' / >> Segment<ELFT>::assignVirtualAddress is setting wrong slice values, however >> playing with this I could not find a correct logic to handle the TBSS. >> >> Any ideas where lld is possible messing the TBSS segments sizes?

...egment, not all from all objects. ld generates a correct output: [17] .tbss NOBITS 0000000000410dec 00000dec 000000000000001c 0000000000000000 WAT 0 0 4 My initial idea is that 'lib/ReaderWriter/ELF/SegmentChunks.cpp' / Segment<ELFT>::assignVirtualAddress is setting wrong slice values, however playing with this I could not find a correct logic to handle the TBSS. Any ideas where lld is possible messing the TBSS segments sizes?

...ed, and that the atoms within are never added to the _atomToAddressMap. However, we can't just add them to that map with their virtual address, as they don't have a virtual address. We need to use the symbol value, which is the offset into the section. My current hack to fix this is to call assignVirtualAddresses(-fileoffset) and then explicitly added them to the _atomToAddressMap. Any ideas for the proper fix here? - Michael Spencer -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130916/956a47ec/attachment.html&g...

...t; within are never added to the _atomToAddressMap. However, we can't just add > them to that map with their virtual address, as they don't have a virtual > address. We need to use the symbol value, which is the offset into the > section. My current hack to fix this is to call > assignVirtualAddresses(-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),...

Hi, Thanks a lot for your answer. It seems lld is still the best solution, even if it does not work "right out of the box" for us today. We already have a solution for the "objcopy" part (added the required output format to llvm-objdump). The ScriptLayout class seems to be empty for now (on the master branch at least), but we do not need linker scripts today. All that is

...t; within are never added to the _atomToAddressMap. However, we can't just add > them to that map with their virtual address, as they don't have a virtual > address. We need to use the symbol value, which is the offset into the > section. My current hack to fix this is to call > assignVirtualAddresses(-fileoffset) and then explicitly added them to the > _atomToAddressMap. > > Any ideas for the proper fix here? > This seems like a problem that will be solved along the way of implementing `ld -r`, so the "proper" solution will probably be something in the general direction...

...to the _atomToAddressMap. However, we can't just >> add >> them to that map with their virtual address, as they don't have a virtual >> address. We need to use the symbol value, which is the offset into the >> section. My current hack to fix this is to call >> assignVirtualAddresses(-**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 s...