From: Warner Losh <imp@bsdimp.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Fwd: non-Bell C compiler
Date: Mon, 11 Mar 2024 15:25:18 -0600 [thread overview]
Message-ID: <CANCZdfpr9Rx3h2HKGF-6qsw8YhP=g3bqbyxyO8dZuTFNX=FMzw@mail.gmail.com> (raw)
In-Reply-To: <202403110824.42B8Ociv054561@critter.freebsd.dk>
[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]
Perspective from a friend...
Warner
---------- Forwarded message ---------
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Mon, Mar 11, 2024 at 2:24 AM
Subject: non-Bell C compiler
To: <imp@freebsd.org>
I noticed the "non-bell C" thread on TUHS and can add a data point
from datamuseum.dk:
The Danish Company "Christian Rovsing A/S" evidently had a C-compiler
for their CR80 mini computer, and my guess is that they created it
in order to qualify for DoD contracts in the POSIX regime.
Example C source:
https://datamuseum.dk/aa//cr80/80/802c73092.html
Listing file from the compiler:
https://datamuseum.dk/aa//cr80/ef/ef65339dc.html
Listing file from the assembler:
http://datamuseum.dk/aa/cr80/32/32ef5456f.html
Listing from the linker:
https://datamuseum.dk/aa//cr80/17/170304129.html
So far we have not spotted the actual compiler anywhere
in the media we have read.
Mention of C being used for project delivery:
http://datamuseum.dk/aa/cr80/1c/1c0b47f0e.html
And btw: That one is from a CDC disc-pack which a father+son
team has read by building a SMD-USB converter.
That project may be interesting in the TUHS domain as well:
https://github.com/Datamuseum-DK/pico-smd-controller
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
[-- Attachment #2: Type: text/html, Size: 2715 bytes --]
parent reply other threads:[~2024-03-11 21:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <202403110824.42B8Ociv054561@critter.freebsd.dk>]
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='CANCZdfpr9Rx3h2HKGF-6qsw8YhP=g3bqbyxyO8dZuTFNX=FMzw@mail.gmail.com' \
--to=imp@bsdimp.com \
--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).