From: Randolph Chung <tausq@debian.org>
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] volunteer sought for a binutils project
Date: Mon, 8 Apr 2002 21:38:55 -0700 [thread overview]
Message-ID: <20020409043855.GI7563@tausq.org> (raw)
When building 64-bit kernels, the linker puts dynamic sections into the
resulting vmlinux file. This is not harmful per se, but is nonetheless
wrong (and confuses some of the modutils tools). Alan Modra explains
the situation and how to fix it below. Anyone feel like give this a
shot?
randolph
----- Forwarded message from Alan Modra <amodra@bigpond.net.au> -----
Date: Mon, 8 Apr 2002 17:18:29 +0930
From: Alan Modra <amodra@bigpond.net.au>
To: Randolph Chung <tausq@debian.org>
Cc: dave@hiauly1.hia.nrc.ca
Subject: Re: unwind sections not sorted?
> legolas[19:30] t% readelf -d ./vmlinux-pa7
>
> Dynamic segment at offset 0x25ee30 contains 11 entries:
> Tag Type Name/Value
> 0x0000000000000004 (HASH) 0x102ee4e0
> 0x0000000000000005 (STRTAB) 0x102ee4d8
> 0x0000000000000006 (SYMTAB) 0x102ee4d8
> 0x000000000000000a (STRSZ) 1 (bytes)
> 0x000000000000000b (SYMENT) 24 (bytes)
> 0x0000000060000001 (<unknown>: 60000001) 0 0x0000000000000003 (PLTGOT) 0x10383470
> 0x0000000000000015 (DEBUG) 0x0
> 0x0000000060000002 (<unknown>: 60000002) 0x0 0x0000000060000000 (<unknown>: 60000000) 0x102f6000 0x0000000000000000 (NULL) 0x0
Hrrm. OK, another bug in elf64-hppa.c. elf64_hppa_check_relocs creates
_all_ the dynamic sections whether needed or not. It certainly shouldn't
be calling bfd_elf64_link_create_dynamic_sections, but rather call
elf64_hppa_create_dynamic_sections to create the sections the backend
needs. Then of course, elf64_hppa_create_dynamic_sections needs to be
modified to not duplicate sections.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
----- End forwarded message -----
reply other threads:[~2002-04-09 4:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020409043855.GI7563@tausq.org \
--to=tausq@debian.org \
--cc=parisc-linux@parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox