search for: assignvirtualaddresses

Hi, Yes, ldd is generating wrong tbss size. It is just considering one tbss section and not calculating all sections from all objects. The following example on x86_64 shows the issue: --- t0.c --- #include <stdio.h> extern __thread int t0; extern __thread int t1; extern __thread int t2; extern __thread int t3; __thread int t4; __thread int t5; __thread int t6; __thread int t7; int

Hi, I am tracking some TLS issues with lld and found that it is generating wrong tbss size for case where multiple modules have non initialized threads variables. For instance: -- t0.c -- __thread int x0; __thread int x1; __thread int x2; extern __thread int e0; extern __thread int e1; extern __thread int e2; extern __thread int e3; int foo0 () { return x0; } int main () { return x0; }

...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>

...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), ha...

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 o...

...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 seg...