The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: sauer@technologists.com (Charles H. Sauer)
Subject: [TUHS] shared objects in Unix
Date: Thu, 29 Mar 2018 21:34:09 -0500	[thread overview]
Message-ID: <1D00C2FE-B36F-4CC3-8548-6FB677443C39@technologists.com> (raw)
In-Reply-To: <20180330021016.GK8921@mcvoy.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2913 bytes --]



> On Mar 29, 2018, at 9:10 PM, Larry McVoy <lm at mcvoy.com> wrote:
> 
> On Thu, Mar 29, 2018 at 08:35:50PM -0500, Charles H. Sauer wrote:
>> 
>> 
>>> On Mar 29, 2018, at 7:40 PM, Clem Cole <clemc at ccc.com> wrote:
>>> 
>>> 
>>> 
>>> On Thu, Mar 29, 2018 at 5:37 PM, Paul Winalski <paul.winalski at gmail.com <mailto:paul.winalski at gmail.com>> wrote:
>>> Also, when was symbol preemption invented?  Traditional shared library
>>> designs such as in IBM System/370, VMS, and Windows NT doesn't have
>>> it.  As one who worked on optimizations in compilers, I came to hate
>>> symbol preemption because it prohibits many useful optimizations.  ELF
>>> does provide a way to turn it off, but it's on by default--you have to
>>> explicitly declare symbols as protected or hidden via source language
>>> pragmas to get rid of it.
>>> 
>>> ???Unless it came from a place like Sun or Sun where Larry or Charlie might remember, I suspect that Steve Johnson is probably best to answer this part of your question -- assuming that it was created during his time in the compiler team in Summit.
>>> 
>>> But, I don't remember when it came on to the scene frankly because it did not effect me.   I think it might have been in the original COFF which came from those days, but its possible its from one of the many bastardization of COFF that occurred after its birth.    I don't remember it being in any of the a.out flavors and I don't think macho has it.
>>> 
>>> As an OS guy, all I remember about it frankly is you and some the compiler folks b*tching about it as a misfeature of UNIX at lunch ;-)
>>> 
>>> ???
>>> ???
>> 
>> 
>> I???m not sure if Clem meant to type ???Sun or IBM where Larry or Charlie??? ??? 
>> 
>> I don???t readily find any documentation or history older than AIX 4.2, well beyond my tenure, but I believe we had shared libraries from the very beginning with AIX on the RT, presumably based on a.out. My recollection is that this was driven by (late) Larry Loucks, with assistance from Jack O???Quin and several of the ISC folks.
> 
> What was the underlying technology that enabled them in AIX?

I didn’t pay much attention to this at the time, and don’t remember specifics. 

Given the change in focus from RT to RS/6000 in the transition from AIX 2 to AIX 3, and all of the other changes that occurred in AIX 3, I assume we started with something very primitive in AIX 1 and re-implemented for AIX 3. 

I’ve sent Jack a note about this discussion. Unless he or ISC folks chime in, or I find someone else to comment or provide documentation, I probably can’t add more. Rick Simpson wrote an article for Byte that might have something about this. He probably contributed to the initial design and (presumed) re-design.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180329/2e86423c/attachment.html>


  reply	other threads:[~2018-03-30  2:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29 21:37 Paul Winalski
2018-03-29 22:01 ` Henry Bent
2018-03-29 22:26 ` Warner Losh
2018-03-29 23:11 ` Dave Horsfall
2018-03-29 23:22   ` Warner Losh
2018-03-29 23:24   ` Larry McVoy
2018-03-30  0:22     ` Clem Cole
2018-03-30  1:46       ` Larry McVoy
2018-03-30  4:28         ` Clem cole
2018-03-30 20:52           ` Jon Forrest
2018-03-30 22:42             ` Clem Cole
2018-03-30 23:29               ` Paul Winalski
2018-04-03 15:49               ` Derek Fawcus
2018-03-30  1:20   ` Lyndon Nerenberg
2018-03-30  0:40 ` Clem Cole
2018-03-30  1:35   ` Charles H. Sauer
2018-03-30  2:10     ` Larry McVoy
2018-03-30  2:34       ` Charles H. Sauer [this message]
2018-03-30  3:04         ` Warner Losh
2018-03-30 20:33         ` Charles H Sauer
2018-03-30  3:00   ` Ron Natalie
2018-03-30 21:53   ` Steve Johnson

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=1D00C2FE-B36F-4CC3-8548-6FB677443C39@technologists.com \
    --to=sauer@technologists.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 NNTP newsgroup(s).