From: Geoff Keating <geoffk@ozemail.com.au>
To: roland@frob.com
Cc: ian@cygnus.com, gas2@cygnus.com, libc-hacker@cygnus.com
Subject: Re: Has anyone looked at ELF 4.1?
Date: Tue, 11 Aug 1998 20:43:00 -0000 [thread overview]
Message-ID: <199808120338.NAA00513@geoffk.wattle.id.au> (raw)
In-Reply-To: <199808110743.DAA24061@baalperazim.frob.com>
> Date: Tue, 11 Aug 1998 03:43:58 -0400
> From: Roland McGrath <roland@frob.com>
> I'm now going to proceed on the assumption that EI_OSABI is intended to
> indicate the operating system ABI expected by the program. I make this
> assumption both because of its name, and because adding two fields whose
> sole meaning is "yes, really, the same file format spec" is just plain
> idiotic and I'm giving SCO a little (perhaps too much) credit for not being
> chalk full of complete idiots.
Have you noticed that the file format now defines OS-specific ranges
for many of the constants?
For instance,
SHT_LOOS 0x60000000
SHT_HIOS 0x6fffffff
Now, if you're going to have such things, it's good to have a tag in
the file format that says what a value of, say, 0x6fffffff means.
In the GNU toolchain, it means 'SHT_GNU_versym'; in Sun's or SGI's
implementation, it might mean something else. So I imagine that this
is one of the things that EI_OSABI selects.
--
Geoffrey Keating <geoffk@ozemail.com.au>
prev parent reply other threads:[~1998-08-11 20:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-08 7:20 H.J. Lu
1998-08-08 10:02 ` Ulrich Drepper
1998-08-08 23:43 ` H.J. Lu
1998-08-10 13:51 ` Ian Lance Taylor
1998-08-10 16:54 ` H.J. Lu
1998-08-11 0:51 ` Roland McGrath
1998-08-11 9:22 ` Ian Lance Taylor
1998-08-16 18:10 ` H.J. Lu
1998-08-16 18:32 ` Ian Lance Taylor
1998-08-16 19:30 ` H.J. Lu
1998-08-16 20:01 ` Ian Lance Taylor
1998-08-17 13:14 ` Ulrich Drepper
1998-08-18 7:40 ` H.J. Lu
1998-08-18 8:04 ` Ulrich Drepper
1998-08-11 0:51 ` Roland McGrath
1998-08-11 20:43 ` Geoff Keating [this message]
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=199808120338.NAA00513@geoffk.wattle.id.au \
--to=geoffk@ozemail.com.au \
--cc=gas2@cygnus.com \
--cc=ian@cygnus.com \
--cc=libc-hacker@cygnus.com \
--cc=roland@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).