9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jacob Moody <moody@mail.posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] Re: [PATCH] game boy advance header target for 5l
Date: Thu, 2 Mar 2023 10:50:16 -0700	[thread overview]
Message-ID: <e9f6554c-32c0-5ab8-f1f5-36908821135c@posixcafe.org> (raw)
In-Reply-To: <B0D9B7C8FA67F0516F3698D6F8597F2B@felloff.net>

On 3/2/23 10:33, cinap_lenrek@felloff.net wrote:
> i dont think that a.out (arm) have relocatable code.
> 
> aout2uimage does not relocate the image (abslute addresses
> are encoded inside instruction immediates) but only
> changes the header and handles some padding stuff.
> 
> the load address (and entry point) all *MUST* stay the
> same no matter if it is wrapped in a.out or uimage.
> 
> this is why you need the -T flag for the linker. theres
> no relocation info in a.out as far as i remember.
> so writing a external tool to convert an a.out to ????
> requiering relocation will have a hard time.
> 
> --
> cinap

I dont want to do relocation, I just want to know
why external programs that only work under assumptions
of how the a.out was linked are preferable to just
having the linker output correct files.

I wrote it this way because there was some existing
precedent in 5l creating boot images for ipaq and ixp1200
in the code. If everyone else is in agreement that this kind of header
code should only be done in external programs, should that code also be moved
to be external or deleted?


  reply	other threads:[~2023-03-02 17:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02  6:56 [9front] " Jacob Moody
2023-03-02 11:15 ` [9front] " Anthony Martin
2023-03-02 16:08   ` Jacob Moody
2023-03-02 17:33     ` cinap_lenrek
2023-03-02 17:50       ` Jacob Moody [this message]
2023-03-03 20:59         ` cinap_lenrek
2023-03-03 21:18           ` Jacob Moody
2023-03-04 15:53             ` cinap_lenrek

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=e9f6554c-32c0-5ab8-f1f5-36908821135c@posixcafe.org \
    --to=moody@mail.posixcafe.org \
    --cc=9front@9front.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 NNTP newsgroup(s).