public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew.lunn@ascom.ch>
To: amodra@bigpond.net.au
Cc: binutils@sources.redhat.com
Subject: Re: Change in .ld syntax or a bug?
Date: Fri, 16 Sep 2005 08:25:00 -0000	[thread overview]
Message-ID: <20050916073239.GS11369@donkey.ma.tech.ascom.ch> (raw)
In-Reply-To: <20050916022647.GT18783@bubble.grove.modra.org>

On Fri, Sep 16, 2005 at 11:56:47AM +0930, Alan Modra wrote:
> On Thu, Sep 15, 2005 at 03:33:22PM +0200, Andrew Lunn wrote:
> > On Thu, Sep 15, 2005 at 10:50:26PM +0930, Alan Modra wrote:
> > > On Thu, Sep 15, 2005 at 02:17:08PM +0200, Andrew Lunn wrote:
> > > > It looks like ld is happy with sections which explicit set there
> > > > address, eg .vectors and .data, but sections which just follow on from
> > > > the previous section it is not happy with and seems to put them
> > > > outside of memory.
> > > > 
> > > > Has there recently been a change in syntax? Or is this a bug?
> > > 
> > > A bug, I suspect.  Do you have anything in .vectors?
> > 
> > Humm, interesting. No, its empty according to --print-map.
> > 
> > I edited target.ld and removed the .vectors section and gave .text a
> > fixed start address. It then linked happily. 
> > 
> > So it looks like ld cannot correctly follow on from an empty section.
> 
> Would you mind checking whether mainline CVS has this bug?  If you find
> it does, I'll see about fixing the problem.

I just tried anoncvs trunk and it has the same problem.

  Thanks
    Andrew

  reply	other threads:[~2005-09-16  7:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15 13:01 Andrew Lunn
2005-09-15 13:39 ` Alan Modra
2005-09-15 13:43   ` Andrew Lunn
2005-09-16  5:36     ` Alan Modra
2005-09-16  8:25       ` Andrew Lunn [this message]
2005-09-19  7:44         ` Alan Modra
2005-09-19 14:23           ` Andrew Lunn
2005-09-20  2:59             ` Alan Modra

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=20050916073239.GS11369@donkey.ma.tech.ascom.ch \
    --to=andrew.lunn@ascom.ch \
    --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).