From: Kevin Bowling <kevin.bowling@kev009.com>
To: Charles H Sauer <sauer@technologists.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] two AIX items [was Re: History of symbol preemption
Date: Tue, 14 Jan 2020 16:22:38 -0700 [thread overview]
Message-ID: <CAK7dMtChcnOWitg4zjMDKM1+R8FPKA548mQW9T9o8Kof-z1dfg@mail.gmail.com> (raw)
In-Reply-To: <e7f59486-228b-54b6-2b20-1df152441476@technologists.com>
I've got a bunch of paper AIX internals documentation outside the
usual, most interesting from memory is one describing the 4.1 work
where it gained SMP support, pthreads, and a bunch of other things. I
need to get some kind of scanning setup if you are interested.
On Tue, Jan 14, 2020 at 12:29 PM Charles H Sauer
<sauer@technologists.com> wrote:
>
>
>
> On 1/13/2020 1:58 PM, Paul Winalski wrote:
>
> > ... LInux, AIX and probably other implementations of ELF have a
> > feature in the runtime loader called symbol preemption. When loading
>
> As far as I know, AIX has never used ELF.
>
> On the RT, AIX 1 & 2 used a.out enhanced for basic shared library
> support, designed by Larry Loucks with help from ISC, probably John
> Levine, if I recall correctly.
>
> Starting with AIX 3, AIX used an extended COFF. See Auslander et al,
> "Dynamic Linking and Loading in the AIX System", SA23-2619 RISC
> System/6000 Technology p. 151. (I don't have/know of PDF of SA23-2619.)
> See, also, https://en.wikipedia.org/wiki/XCOFF.
>
> It seems likely that AIX XCOFF supported symbol preemption, I haven't
> tried to determine one way or the other.
>
> AIX on 386 & 370 probably used a.out. Clem probably knows.
>
> An IBM retirees group on Facebook led me to IBM AIX Enhancements and
> Modernization at http://www.redbooks.ibm.com/abstracts/sg248453.html,
> just available yesterday. I tend to think of AIX as abandoned by IBM in
> favor of Linux, but, of course, that isn't really true. I've downloaded
> the PDF, but not looked inside.
>
> Charlie
>
> --
> voice: +1.512.784.7526 e-mail: sauer@technologists.com
> fax: +1.512.346.5240 Web: https://technologists.com/sauer/
> Facebook/Google/Skype/Twitter: CharlesHSauer
next prev parent reply other threads:[~2020-01-14 23:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 19:58 [TUHS] " Paul Winalski
2020-01-13 20:46 ` Rico Pajarola
2020-01-13 21:04 ` Clem Cole
2020-01-13 21:40 ` Rico Pajarola
2020-01-13 21:44 ` Paul Winalski
2020-01-13 21:45 ` Rico Pajarola
2020-01-13 22:20 ` Larry McVoy
2020-01-13 21:42 ` Paul Winalski
2020-01-13 22:53 ` Henry Bent
2020-01-14 0:31 ` Clem Cole
2020-01-14 2:53 ` Rob Gingell
2020-01-14 19:21 ` [TUHS] two AIX items [was " Charles H Sauer
2020-01-14 20:31 ` Clem Cole
2020-01-14 23:22 ` Kevin Bowling [this message]
2020-01-15 16:41 ` Paul Winalski
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=CAK7dMtChcnOWitg4zjMDKM1+R8FPKA548mQW9T9o8Kof-z1dfg@mail.gmail.com \
--to=kevin.bowling@kev009.com \
--cc=sauer@technologists.com \
--cc=tuhs@minnie.tuhs.org \
/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).