public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Christian Eggers <ceggers@gmx.de>
Cc: binutils@sourceware.org
Subject: Re: [PATCH v3 0/2] Fix several mix up between octets and bytes in ELF program headers
Date: Thu, 20 Feb 2020 01:30:00 -0000	[thread overview]
Message-ID: <20200220012952.GW5570@bubble.grove.modra.org> (raw)
In-Reply-To: <5653117.1aehKcCLEe@zbook-opensuse.wgnetz.xx>

On Sun, Feb 16, 2020 at 08:37:43PM +0100, Christian Eggers wrote:
> But for the ELF file, every program handling it must know which information is
> in octets or in bytes. For luck, the sizes are already in octets, otherwise I
> had already trouble with external software. But probably everything should be
> stored in octets, at least this should resolve the trouble I already have with
> my external debugger. This debugger has only one symbol space for ARM and
> SDMA. Having symbols (and debug line info) in octets should make nasty
> workarounds needless.
> 
> What is your opinion?

Yes, that is what I'd be inclined to so.  In fact, if faced with
designing an ABI for your NXP SDMA processor from scratch I'd avoid
the octets_per_byte conversion entirely by using octets from assembly
onwards.  Addresses would always be multiples of two, and you'd design
relocations to suit.  Users of course would need to write ". + 2"
rather than ". + 1" and similarly in other expressions involving
addresses.

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2020-02-20  1:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-15 19:37 Christian Eggers
2020-02-16  8:22 ` Christian Eggers
2020-02-16 19:37   ` Christian Eggers
2020-02-20  1:30     ` Alan Modra [this message]
2020-02-22 16:32       ` Christian Eggers
2020-02-22 21:08       ` Christian Eggers
2020-02-23  9:07       ` Christian Eggers
2020-02-27  8:35         ` Alan Modra
2020-03-07 21:05           ` Christian Eggers
2020-02-23 18:35       ` Christian Eggers

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=20200220012952.GW5570@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=ceggers@gmx.de \
    /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).