From: Roland McGrath <roland@hack.frob.com>
To: hegdesmailbox@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: <20160610212256.D5A772C39F7@topped-with-meat.com> (raw)
In-Reply-To: Suprateeka R Hegde's message of Sunday, 5 June 2016 12:57:44 +0530 <7160c0e3-b49c-1ab8-c0d3-cee12355f895@gmail.com>
> What is the reason why we emit OSABI value as "UNIX - System V"
> (ELFOSABI_SYSV) even on GNU/Linux systems? Shouldn't it be just "GNU"
> (ELFOSABI_GNU)?
In GNU systems the use of this field is specifically to indicate that
certain GNU extensions to ELF are used in the particular object. In
particular, if any .dynsym entries use STT_GNU_IFUNC o STB_GNU_UNIQUE,
then e_ident[EI_OSABI] must be ELFOSABI_GNU. Otherwise, it can be
ELFOSABI_NONE (aka ELFOSABI_SYSV). In fact, it should be, and the
tools (linkers) implement that distinction. This makes it possible
for current tools (without special switches or whatnot) to produce
binaries that are compatible with older dynamic linker implementations
that did not support these GNU extensions to ELF.
This is arguably a bad overloading of the original instead of
EI_OSABI, but it's what's been done for GNU systems and so now it's an
unchangeable part of the GNU ELF gABI.
next prev parent reply other threads:[~2016-06-10 21:23 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 [this message]
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
2016-01-01 0:00 ` Suprateeka R Hegde
2016-01-01 0:00 ` Carlos O'Donell
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=20160610212256.D5A772C39F7@topped-with-meat.com \
--to=roland@hack.frob.com \
--cc=gnu-gabi@sourceware.org \
--cc=hegdesmailbox@gmail.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).