From: Carlos O'Donell <carlos@redhat.com>
To: hegdesmailbox@gmail.com, Roland McGrath <roland@hack.frob.com>,
"H.J. Lu" <hjl.tools@gmail.com>
Cc: gnu-gabi@sourceware.org
Subject: Re: OSABI on Linux Distros
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <a679aa7e-0fc3-b271-ed65-4c26c5fe0cb8@redhat.com> (raw)
In-Reply-To: <03e8b45f-f334-f480-1432-096c08c0ee3a@gmail.com>
On 06/13/2016 11:57 AM, Suprateeka R Hegde wrote:
> It depends on what you are considering here. You considered only
> dynamic linker. I consider even non-GNU tools that reads ELF. When
> such a tool encounters SYSV as the ABI, it cannot do much. However,
> if the tool can see that the ELF has GNU extensions, then it can do
> better job of dumping GNU specific ELF details.
>
> My actual question is what is the harm if we mark GNU ABI for *any*
> GNU extension and not restrict it to a partial list.
That's a much better question, but still doesn't yet get at the crux
of your argument.
It might be said that it should be possible to identify the OS from
the OSABI value in order to aid in the processing of PT_LOOS to
PT_HIOS entries (GNU_EH_FRAME, GNU_STACK, GNU_RELRO)?
Is that what you are thinking?
I expect that entries between PT_LOOS to PT_HIOS are allowed to
overlap between OSs?
--
Cheers,
Carlos.
next prev parent reply other threads:[~2016-06-13 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 Suprateeka R Hegde
2016-01-01 0:00 ` Roland McGrath
2016-01-01 0:00 ` Carlos O'Donell
2016-01-01 0:00 ` Suprateeka R Hegde
2016-01-01 0:00 ` Suprateeka R Hegde
2016-01-01 0:00 ` Carlos O'Donell
2016-01-01 0:00 ` Suprateeka R Hegde
2016-01-01 0:00 ` Carlos O'Donell [this message]
2016-01-01 0:00 ` Suprateeka R Hegde
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=a679aa7e-0fc3-b271-ed65-4c26c5fe0cb8@redhat.com \
--to=carlos@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=hegdesmailbox@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=roland@hack.frob.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).