public inbox for gnu-gabi@sourceware.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Florian Weimer <fweimer@redhat.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Szabolcs Nagy <nsz@port70.net>,
	    Jan Beulich <JBeulich@suse.com>,
	Rich Felker <dalias@libc.org>,
	    Binutils <binutils@sourceware.org>,
	gnu-gabi@sourceware.org
Subject: Re: RFC: Add SHT_GNU_PHDRS
Date: Mon, 01 Jan 2018 00:00:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.21.1809281304530.7867@wotan.suse.de> (raw)
In-Reply-To: <87lg7llr99.fsf@oldenburg.str.redhat.com>

Hi,

On Fri, 28 Sep 2018, Florian Weimer wrote:

> > This section hack isn't necessary at all for what we need.  The link 
> > editor merely needs to ensure that the program headers are part of 
> > some loadable segment, either by placing it not at the start of the 
> > file (though that would mean the ELF header isn't part of the loaded 
> > image, which is desirable to have), or by creating such loadble 
> > segment if necessary.
> >
> > No gABI extensions are needed.
> 
> That would certainly be nice.
> 
> Can we try to update the ELF specification to clarify this?

Maybe.

> That should give us additional feedback whether this reading of the 
> specification is correct.

Well, at least the part about sections being purely optional is undeniably 
true.  The section headers themself were never part of the loaded 
image (nor part of any section for that matter).

Now the but: I would agree that it would be nice if all file contents 
would be covered by some section if section headers are in the file at 
all, simply because the named sections are easier for humans to deal with 
than numbered program headers, so that their use in tools (like e.g. 
readelf -x) is comfortable.  But that's independend and outside of what's 
required by ELF.  If we go down that route then we should go the full way 
and cover the ELF header, the program headers and the section headers with 
sections as well.  I don't see why they would need their own type though, 
PROGBITS is just fine.  And again, all that would be optional and a pure 
QoI issue.


Ciao,
Michael.

  reply	other threads:[~2018-09-28 13:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-01  0:00 H.J. Lu
2018-01-01  0:00 ` Carlos O'Donell
2018-01-01  0:00   ` H.J. Lu
     [not found] ` <CAORpzuOWtHeqBLEE+MMN4-TZyp6Z1r-MdmyNv7Zj-BhxMstr=g@mail.gmail.com>
2018-01-01  0:00   ` H.J. Lu
2018-01-01  0:00 ` Florian Weimer
2018-01-01  0:00   ` Jan Beulich
2018-01-01  0:00     ` Florian Weimer
2018-01-01  0:00       ` Szabolcs Nagy
2018-01-01  0:00         ` H.J. Lu
2018-01-01  0:00           ` Florian Weimer
2018-01-01  0:00             ` H.J. Lu
2018-01-01  0:00               ` Florian Weimer
2018-01-01  0:00                 ` Carlos O'Donell
2018-01-01  0:00                   ` H.J. Lu
2018-01-01  0:00                     ` Carlos O'Donell
2018-01-01  0:00                       ` H.J. Lu
2018-01-01  0:00                         ` Carlos O'Donell
2018-01-01  0:00                   ` Cary Coutant
2018-01-01  0:00                     ` H.J. Lu
2018-01-01  0:00                       ` Rich Felker
2018-01-01  0:00                 ` Michael Matz
2018-01-01  0:00                   ` Florian Weimer
2018-01-01  0:00                     ` Michael Matz [this message]
2018-01-01  0:00         ` Florian Weimer
2018-01-01  0:00           ` Cary Coutant

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.LSU.2.21.1809281304530.7867@wotan.suse.de \
    --to=matz@suse.de \
    --cc=JBeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=dalias@libc.org \
    --cc=fweimer@redhat.com \
    --cc=gnu-gabi@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=nsz@port70.net \
    /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).