From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 8738 invoked from network); 3 Jun 2022 02:10:17 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 3 Jun 2022 02:10:17 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 2613940996; Fri, 3 Jun 2022 12:10:13 +1000 (AEST) Received: from mail-ua1-x933.google.com (mail-ua1-x933.google.com [IPv6:2607:f8b0:4864:20::933]) by minnie.tuhs.org (Postfix) with ESMTPS id 8020C4097F for ; Fri, 3 Jun 2022 12:10:07 +1000 (AEST) Received: by mail-ua1-x933.google.com with SMTP id 63so2136427uaw.10 for ; Thu, 02 Jun 2022 19:10:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sSz9t2PgQ7AcfRp70LoxelqycY6HqNKBnd2YQY9dQCo=; b=5+LB3jJSdxDKPYF0OiGGOfzx6N/pRsf5t3AFNqBnrhoGBZweaUD1BiGlA26df98Tkv 0yN2NwKL8Y0VpSvkEtcRFGEBoBGnq5Rib1mwC7zYF2BS975Qjzo3ru1ynGvYPkZQDWGP qFuYIqiSKhCc6xFGPU7YSX0VZ5V4K93JDpPIhrT8Q4rW371WyeOPkCCQ8jhPbw3jI5p1 QbPcRByYAtr26Mdfu4/ohS62hOMHwj9ZGwjjvG+Stm5U3sxIvemvTeW6gbgJmIPxqItD 0m+V3K922T92AuTeNPqmsarZMNiD5ep9OGbhtsbnQ/gaKbQ2WoR1V0rK6bbSg48Jy2au ovsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sSz9t2PgQ7AcfRp70LoxelqycY6HqNKBnd2YQY9dQCo=; b=T2KTme7kRi/ukVF2ritsQXCZkRpLR7h0xDsTVhxjpN26DDSgvSrPMA0wqX89qOhtvZ m9bBlvfRC5vO38odtYehqKkWXdS9/0BYYd0gkTXTM5V2isOnPE9R4klHRN22YpLub1Ir DwACMb4zYyjwxKsIqrQDPQtROApeVb2REYOEhNduANh43AXt4tyeIENM64AeXDDuyF7g LnvSZR3T9X8rpx1+0EJcpzXXP/PX01a2ut2N7gZ9kBXEXmGkjONA638aeIGXMzsbbubB syNPT2vW+UC1CZoPd3odcV3pzGoIcK8RIRPYZ+MMtKpiCPaOyOLjohkNnyJYMNaKAkLZ XMMg== X-Gm-Message-State: AOAM531rlQvUpjyAFVq5MqElNl6s6nFXSb8WpICQMDCQ5Yn1CDLm7eBj qTctFGYuS9VlQUorcypAgw32iTZfCeMbAXL9uzT9fQ== X-Google-Smtp-Source: ABdhPJyoHcNyjn1+Y2t1Bqg32O2sWh7PJ+NN006Svd+bGbkjxRBCQMk1QEQTJlC4l2lO1tppeuk+oce7D4gj/dBrZbk= X-Received: by 2002:a05:6130:90:b0:362:891c:edef with SMTP id x16-20020a056130009000b00362891cedefmr26827461uaf.106.1654222206239; Thu, 02 Jun 2022 19:10:06 -0700 (PDT) MIME-Version: 1.0 References: <64EEED76-2EBB-4D55-ADE4-DEDFAC391322@planet.nl> <66ae3ff2-bd07-e192-a00f-f9c701d857c8@spamtrap.tnetconsulting.net> <9F17E4E7-37F3-43B7-A090-CEAFB2F51EDF@eschatologist.net> In-Reply-To: <9F17E4E7-37F3-43B7-A090-CEAFB2F51EDF@eschatologist.net> From: Warner Losh Date: Thu, 2 Jun 2022 20:09:55 -0600 Message-ID: To: Chris Hanson Content-Type: multipart/alternative; boundary="000000000000fb98c005e0819e8f" Message-ID-Hash: LTRON5WK44W6QAI7HNACM7E3L4HZIDRM X-Message-ID-Hash: LTRON5WK44W6QAI7HNACM7E3L4HZIDRM X-MailFrom: wlosh@bsdimp.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Grant Taylor , The Eunuchs Hysterical Society X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: Historical application software List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000fb98c005e0819e8f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jun 2, 2022, 8:00 PM Chris Hanson wrote: > On May 28, 2022, at 5:57 PM, Warner Losh 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 fo= r > 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 Pow= er > Macintosh. Apple's Preferred Executable Format was essentially a mechanic= al > translation away from IBM's XCOFF; the initial toolchains produced .o fil= es > 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 f= or > BeOS on PowerPC. > > And then there's the "b.out" format used by i960=E2=80=A6 > There were a number of b.out formats used by PC C compilers... Warner -- Chris > > --000000000000fb98c005e0819e8f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Jun 2, 2022, 8:00 PM Chris Hanson <cmhanson@eschatologist.net> w= rote:
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 snowfla= ke.

HP initially used its own object file format for 32-bit PA-RISC, whether ru= nning 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 Po= wer Macintosh. Apple's Preferred Executable Format was essentially a me= chanical translation away from IBM's XCOFF; the initial toolchains prod= uced .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=E2=80=A6
=

Ther= e were a number of b.out formats used by PC C compilers...

Warner=C2=A0

=
=C2=A0 -- Chris

--000000000000fb98c005e0819e8f--