public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Stephen Casner <casner@acm.org>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: Problem with ld for PDP-11
Date: Mon, 17 Feb 2020 21:06:00 -0000	[thread overview]
Message-ID: <alpine.OSX.2.21.9999.2002171305400.65600@auge.attlocal.net> (raw)
In-Reply-To: <alpine.OSX.2.21.9999.2002141608300.60060@auge.attlocal.net>

I have submitted bug 25569 with a patch for this proposed fix.

                                                        -- Steve

On Fri, 14 Feb 2020, Stephen Casner wrote:

> On Thu, 13 Feb 2020, Alan Modra wrote:
>
> > The correct fix then is to add a check that the original data size was
> > odd.  That might not be easy as you may have lost the original data
> > size by the time this code runs.  The AOUT code is a bit of a mess.
>
> Here's an alternative idea, if it would not be a logical scope
> violation to access the "where" member:  check abfd->where to see if
> an odd byte has been written, and if so add a padding byte.
>
> > Oh, and if there is no data then it's the text section that might need
> > extending.
>
> That should not be a concern because PDP11 instruction must always be
> a multiple of words long.
>
>                                                         -- Steve

      reply	other threads:[~2020-02-17 21:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12 20:30 Stephen Casner
2020-02-13  0:26 ` Alan Modra
2020-02-13  6:02   ` Stephen Casner
2020-02-13  6:58     ` Alan Modra
2020-02-13  7:18       ` Stephen Casner
2020-02-13  7:50         ` Alan Modra
2020-02-14 23:42           ` Stephen Casner
2020-02-15  0:11   ` Stephen Casner
2020-02-17 21:06     ` Stephen Casner [this message]

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=alpine.OSX.2.21.9999.2002171305400.65600@auge.attlocal.net \
    --to=casner@acm.org \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    /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).