Xref: utzoo comp.unix.wizards:11101 comp.os.misc:516
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!rutgers!bellcore!jcricket!sjs
From: sjs@jcricket.ctt.bellcore.com (Stan Switzer)
Newsgroups: comp.unix.wizards,comp.os.misc
Subject: Re: shared libraries and dynamic relocation
Message-ID: <10149@bellcore.bellcore.com>
Date: 13 Sep 88 12:27:34 GMT
References: <21606@ccicpg.UUCP> <7622@boring.cwi.nl> <2040@cuuxb.ATT.COM> <7716@bigtex.uucp> <67440@sun.uucp> <7804@bigtex.uucp> <10358@tekecs.TEK.COM>
Sender: news@bellcore.bellcore.com
Reply-To: sjs@ctt.bellcore.com (Stan Switzer)
Organization: Computer Technology Transfer, Bellcore
Lines: 15

andrew@frip.gwd.tek.com (Andrew Klossner) writes:
> Note that AT&T has announced that, with system V release 4, they will
> also do dynamic loading on exec to support shared system calls.  They
> will also trash the COFF format in favor of yet another object file
> format, ELF.
> 

Can someone summarize this new ELF format, with advantages and
disadvantages listed.  I hope they took C++ needs into consideration
(especially debugging information).  Is there provision for sharing of
string literals (or other literals) across object module boundaries?
Is there a specific storage class for "consts" separate from text (on
some architectures this is important)?

Stan Switzer  sjs@ctt.bellcore.com