From: Alan Modra <amodra@bigpond.net.au>
To: DJ Delorie <dj@redhat.com>
Cc: binutils@sources.redhat.com
Subject: Re: relaxing vs section merging
Date: Tue, 27 Apr 2004 02:35:00 -0000 [thread overview]
Message-ID: <20040427023506.GB2581@bubble.modra.org> (raw)
In-Reply-To: <200404261945.i3QJjJRS026862@greed.delorie.com>
On Mon, Apr 26, 2004 at 03:45:19PM -0400, DJ Delorie wrote:
> What I'm seeing is that the relaxation code uses the pre-merge value
> of LC1a, but the relocation uses the post-merge value and thus fails
> (reloc overflow). I've verified that merging happens before relaxing.
I would guess that the mn10300 symbol reading code needs to look like
that in elflink.c:elf_link_input_bfd. I don't see
_bfd_merged_section_offset being called anywhere in elf-m10300.c.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2004-04-27 2:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 19:54 DJ Delorie
2004-04-27 2:35 ` Alan Modra [this message]
2004-04-27 2:47 ` DJ Delorie
2004-04-27 3:39 ` Alan Modra
2004-04-27 18:03 ` DJ Delorie
2004-04-27 21:39 ` Dave Korn
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=20040427023506.GB2581@bubble.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=dj@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).