From: James Cownie <jcownie@etnus.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: libc-alpha@sources.redhat.com, binutils@sources.redhat.com,
gdb@sources.redhat.com
Subject: Re: RFC: ELF prelinker - 0.1.1
Date: Thu, 05 Jul 2001 06:08:00 -0000 [thread overview]
Message-ID: <15I8rE-1D5-00@etnus.com> (raw)
In-Reply-To: <20010705080214.O32061@devserv.devel.redhat.com>
> Anyway, from my initial look at DWARF2, DWARF2 relocation will be fairly
> easy as that format is nicely designed. Nothing in LEB128 format needs to be
> relocated, essentially:
> - nothing in .debug_abbrev
> - don't have to care about .eh_frame, since it is SHF_ALLOC and has its REL{,A} section
> - no addresses which need relocation, can be in LEB128 format (how would
> static linker work in that case?), there is nothing like R_IA64_ULEB128,
> is it? From my current brief look at DWARF2, DW_FORM_addr format
> attributes will have to be adjusted, plus DW_OP_addr's, will need to check
> some more if I haven't missed something
> - will need to figure out what to do about the rest of .debug_* sections -
> but the prelinker will certainly just bail out if it finds a debug section
> or its format which it does not recognize.
OK, you'll need to look at (at least) .debug_line and .debug_info.
Good luck !
-- Jim
James Cownie <jcownie@etnus.com>
Etnus, LLC. +44 117 9071438
http://www.etnus.com
next prev parent reply other threads:[~2001-07-05 6:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010705125600.Q737@sunsite.ms.mff.cuni.cz>
2001-07-05 4:31 ` James Cownie
2001-07-05 5:02 ` Jakub Jelinek
2001-07-05 6:08 ` James Cownie [this message]
2001-07-05 8:42 ` Daniel Berlin
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=15I8rE-1D5-00@etnus.com \
--to=jcownie@etnus.com \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jakub@redhat.com \
--cc=libc-alpha@sources.redhat.com \
/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