This is the mail archive of the
mailing list for the binutils project.
RE: [committed, PATCH] Always create dynsym section with dynamic sections
- From: Faraz Shahbazker <Faraz dot Shahbazker at imgtec dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: Binutils <binutils at sourceware dot org>
- Date: Fri, 22 Apr 2016 21:49:28 +0000
- Subject: RE: [committed, PATCH] Always create dynsym section with dynamic sections
- Authentication-results: sourceware.org; auth=none
- References: <20160223003208 dot GA30022 at intel dot com> <571A59A8 dot 4000700 at imgtec dot com> <CAMe9rOqr+E11vmpMV4Fo8Js_nCdsrcKpWKXQCUy+qSjjod=_hg at mail dot gmail dot com> <571A73BE dot 4000709 at imgtec dot com>,<CAMe9rOp4nZHfL2=st5-fap84C7zOnnyjrU7e0_+QWe1jYhK6cw at mail dot gmail dot com>
On 04/22/2016 12:28 PM, H.J. Lu wrote:
> On Fri, Apr 22, 2016 at 11:55 AM, Faraz Shahbazker
>> + if (dynsymcount != 0 || elf_hash_table (info)->dynamic_sections_created)
>> + ++dynsymcount;
> Are you saying dynamic_sections_created is 0 for MIPS here
> and will become 1 later?
No, it will remain 0. The link is static, but the hash_table is still used to
record global symbols that have GOT relocations against them. Ofc, this
hash_table does not result in creation of a dynsym section, because well,
dynamic_sections_created is 0.
Check the list of callers to bfd_elf_link_record_dynamic_symbol(), a number of
architectures use the link_hash_table in situations where it is not clear whether it is
being used to track dynamic symbols for a dynamic executable, as it is for x86.