public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: amodra@bigpond.net.au
Cc: binutils@sources.redhat.com
Subject: Re: relaxing vs section merging
Date: Tue, 27 Apr 2004 02:47:00 -0000	[thread overview]
Message-ID: <200404270247.i3R2lEwL032475@greed.delorie.com> (raw)
In-Reply-To: <20040427023506.GB2581@bubble.modra.org> (message from Alan Modra on Tue, 27 Apr 2004 12:05:06 +0930)


> 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.

Yeah, I added calls to _bfd_merged_section_offset (the mn10300
relocation code calls it indirectly).  That's when all the other
problems started happening; I think I mentioned that in my original
email.

  reply	other threads:[~2004-04-27  2:47 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
2004-04-27  2:47   ` DJ Delorie [this message]
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=200404270247.i3R2lEwL032475@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=amodra@bigpond.net.au \
    --cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).