From: Dmitry Diky <ddiky@alarity.com>
To: hp@bitrange.com, binutils@sourceware.org, rth@redhat.com
Subject: Re: dwarf2 and linker relaxation problem
Date: Mon, 05 Sep 2005 21:47:00 -0000 [thread overview]
Message-ID: <200509051057.04858.ddiky@alarity.com> (raw)
In-Reply-To: <m31x47fbik.fsf@gossamer.airs.com>
Ian,
I have checked sh_elf_relax_delete_bytes() in elf32-sh.c file.
It seems that relaxation does not touch .debug_line section at all, cause
there are no references from .debug_line section into debuggable .text
section. Also, as it seems to me, dwarf2 generator does not emit something
like '.word .l1 - .l2' in executable section suitable for further relocation
by linker. Am I correct?
Thanks,
Dmitry.
> > There are no relocations possible here. The linker will have to
> > completely parse and re-emit the .debug_line section, the
> > .debug_frame section, and the .eh_frame section.
>
> Well, no, relocations are possible, but you do generally need to
> define new relocation types, and you need to force the assembler to
> generate them.
next prev parent reply other threads:[~2005-09-05 6:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 16:36 Dmitry Diky
2005-09-01 17:48 ` Ian Lance Taylor
2005-09-01 23:30 ` Jim Blandy
2005-09-02 2:51 ` Ian Lance Taylor
2005-09-02 7:44 ` Dmitry Diky
2005-09-02 8:43 ` Nick Clifton
2005-09-02 9:28 ` Dmitry Diky
2005-09-02 9:35 ` Dmitry Diky
2005-09-02 9:58 ` Nick Clifton
2005-09-02 11:17 ` Nick Clifton
2005-09-02 16:52 ` Hans-Peter Nilsson
2005-09-02 17:02 ` Dmitry Diky
2005-09-02 18:42 ` Hans-Peter Nilsson
2005-09-02 18:53 ` Dmitry Diky
2005-09-02 19:21 ` Ian Lance Taylor
2005-09-02 21:27 ` Richard Henderson
2005-09-03 4:35 ` Ian Lance Taylor
2005-09-05 21:47 ` Dmitry Diky [this message]
2005-09-02 17:23 ` Ian Lance Taylor
2005-09-06 19:32 ` Jim Blandy
2005-09-06 20:15 ` Ian Lance Taylor
2005-09-07 11:39 ` Dmitry Diky
2005-09-07 18:11 ` Richard Henderson
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=200509051057.04858.ddiky@alarity.com \
--to=ddiky@alarity.com \
--cc=binutils@sourceware.org \
--cc=hp@bitrange.com \
--cc=rth@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).