From: Warner Losh <imp@bsdimp.com>
To: Chris Hanson <cmhanson@eschatologist.net>
Cc: Grant Taylor <gtaylor@tnetconsulting.net>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Historical application software
Date: Thu, 2 Jun 2022 20:09:55 -0600 [thread overview]
Message-ID: <CANCZdfpS0ZDnm=-vzLAA7jo9D5LogiF=6mBf5kaaEJiD3im+ZQ@mail.gmail.com> (raw)
In-Reply-To: <9F17E4E7-37F3-43B7-A090-CEAFB2F51EDF@eschatologist.net>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
On Thu, Jun 2, 2022, 8:00 PM Chris Hanson <cmhanson@eschatologist.net>
wrote:
> On May 28, 2022, at 5:57 PM, Warner Losh <imp@bsdimp.com> wrote:
> >
> > HP-UX had a weird form of COFF in the early days. IBM AIX had its own
> thing that wasn't quite COFF, nor was it quite a.out. Apollo also had a
> variation on COFF that wasn't quite standard. I wrote a symbol mangler for
> all of these in the early 90s and each one was its own special snowflake.
>
> HP initially used its own object file format for 32-bit PA-RISC, whether
> running HP-UX or MPE. I believe it's still the format the ROM expects for
> anything bootable, at least it is for my MPE-capable A400.
>
> IBM's COFF for AIX on POWER and PowerPC was XCOFF, which was also used as
> the initial object file format (though not executable format) for the Power
> Macintosh. Apple's Preferred Executable Format was essentially a mechanical
> translation away from IBM's XCOFF; the initial toolchains produced .o files
> and then a "final" binary in XCOFF format, and then ran a MakePEF tool on
> that to produce the PEF binary for an executable or shared library. I
> believe Be, due in part to their heritage and toolchains, also used PEF for
> BeOS on PowerPC.
>
> And then there's the "b.out" format used by i960…
>
There were a number of b.out formats used by PC C compilers...
Warner
-- Chris
>
>
[-- Attachment #2: Type: text/html, Size: 2082 bytes --]
next prev parent reply other threads:[~2022-06-03 2:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 11:57 [TUHS] " Paul Ruizendaal
2022-05-27 17:00 ` [TUHS] " Grant Taylor via TUHS
2022-05-27 17:29 ` Warner Losh
2022-05-28 15:30 ` Paul Winalski
2022-05-29 0:57 ` Warner Losh
2022-05-29 9:43 ` Ralph Corderoy
2022-06-03 2:00 ` Chris Hanson
2022-06-03 2:09 ` Warner Losh [this message]
2022-06-03 2:02 ` Chris Hanson
2022-05-28 22:06 ` [TUHS] Anyone have an interest in really old analog multimeters and a vacuum tube tested circa 1960s or 1950s? Kenneth Goodwin
2022-05-28 22:09 ` [TUHS] " Kenneth Goodwin
2022-05-28 23:31 ` Ed Cashin
2022-05-28 23:45 ` Clem Cole
2022-05-29 2:11 ` Kenneth Goodwin
2022-05-29 2:18 ` Kenneth Goodwin
[not found] ` <99E8871E-035C-4A58-8091-189EDE4689BA@common-sense.com>
[not found] ` <CAMQbRb2uPTaqCrZCnVQuBtHhnFZWPpyZ_fHxs-4h8WGoOCrGJQ@mail.gmail.com>
2022-05-29 13:05 ` Kenneth Goodwin
2022-05-29 2:08 ` Kenneth Goodwin
2022-05-29 2:10 ` Kenneth Goodwin
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='CANCZdfpS0ZDnm=-vzLAA7jo9D5LogiF=6mBf5kaaEJiD3im+ZQ@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=cmhanson@eschatologist.net \
--cc=gtaylor@tnetconsulting.net \
--cc=tuhs@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).