The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Chris Pinnock <chris_pinnock@mac.com>
Cc: segaloco <segaloco@protonmail.com>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: crt0 -- what's in that name?
Date: Mon, 12 Jun 2023 16:22:20 -0400	[thread overview]
Message-ID: <CAEoi9W4kuweQ-fB57G0-Swiy8i0MyZyntf0oQ=wK2mxk+O+iQQ@mail.gmail.com> (raw)
In-Reply-To: <8DE09E23-5348-496B-B1CF-EDE9C47983B2@mac.com>

On Mon, Jun 12, 2023 at 4:04 PM Chris Pinnock via TUHS <tuhs@tuhs.org> wrote:
> I had thought that crt stood for “compiler runtime”. You’ll find files on a NetBSD (and other BSDs) in /usr/lib/csu called crt0, crtbegin, crtend (etc) which are included in the compiled binaries at build time and are used to include machine dependent things need to initialise programs.

Hmm. The comment at the top of `crt0.s` from 2nd Edition says, "C
runtime startoff", which seems pretty clear. Whether that has changed
over time is, of course, another matter (like how GCC changed to "GNU
Compiler Collection").

> (The acronym could be wrong of course - bss is the notorious one, where even the man page for a.out has this has a bug: "Nobody seems to agree on what bss stands for.”)

Huh. That seems to have come into the man page sometime after
4.3BSD-Taho; it's in Reno and Net/2, but not before (nor in other
systems, that I can see).

I thought it was pretty well known that it stands for, "Block Started
(by) Symbol"?

        - Dan C.

> > On 12 Jun 2023, at 20:45, segaloco via TUHS <tuhs@tuhs.org> wrote:
> >
> > Probably derivative of /etc/brt1 and /etc/brt2.  If there's a <lang>rt<digit> convention before that I can't say. If they're going for UNIX-y nomenclature though bootloaders were mboot, tboot, uboot, etc.  As an aside, Sega used the nomenclature "icd_blkX" where X is a digit to number 128-byte blocks of their initial loader, icd I presume standing for something like initial code. I feel like I've seen "icd" used elsewhere, but couldn't say where. In any case, I'm sure a lot could be devoted to running down the history of names like crt0, mch, mdec, icd, uboot, and so on. Unfortunately those sorts of trivia haven't bubbled up in my manual studies.
> >
> > - Matt G.
> > ------- Original Message -------
> > On Monday, June 12th, 2023 at 11:53 AM, Clem Cole <clemc@ccc.com> wrote:
> >
> >> This makes sense since there was B runtime to start, and Dennis was messing with things. No idea but I wonder if that was the impetus for the rename from B to newB to C - when he introduced a new runtime?
> >> ᐧ
> >>
> >> On Mon, Jun 12, 2023 at 2:30 PM Dan Cross <crossd@gmail.com> wrote:
> >> On Mon, Jun 12, 2023 at 2:22 PM ron minnich <rminnich@gmail.com> wrote:
> >> > This came up lately in the riscv firmware universe. Someone named early boot bt0, I mentioned crt0, and ... when did that name first appear? I first saw it in v6 but I'm sure it was long before.
> >>
> >> The Unix tree shows it in 2nd Edition:
> >> https://www.tuhs.org/cgi-bin/utree.pl?file=V2/lib/crt0.s
> >> That would suggest it was more or less contemporaneous with C itself.
> >>
> >> - Dan C.
> >
>

  reply	other threads:[~2023-06-12 20:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 18:22 [TUHS] " ron minnich
2023-06-12 18:29 ` [TUHS] " Dan Cross
2023-06-12 18:53   ` Clem Cole
2023-06-12 19:45     ` segaloco via TUHS
2023-06-12 20:03       ` Chris Pinnock via TUHS
2023-06-12 20:22         ` Dan Cross [this message]
2023-06-12 20:28           ` Chris Pinnock via TUHS
2023-06-12 20:58             ` Paul Winalski
2023-06-12 21:32               ` segaloco via TUHS
2023-06-12 21:28             ` Anthony Martin
2023-06-12 20:25         ` Steve Nickolas
2023-06-12 20:17   ` Dave Horsfall
2023-06-12 21:31     ` Clem Cole
2023-06-12 21:39       ` G. Branden Robinson
2023-06-12 22:39         ` Clem Cole
2023-06-12 22:50           ` G. Branden Robinson
2023-06-12 23:04           ` Paul Winalski
     [not found]             ` <20230612234953.pwu7oi6hyglsaqzs@illithid>
     [not found]               ` <CABH=_VTv1g76MnHQpkOPXRu9WFe2Kc8qchJbAgTCMpv0bFzUrQ@mail.gmail.com>
2023-06-14  1:59                 ` [TUHS] Re: [COFF] " Adam Thornton
2023-06-12 22:09       ` [TUHS] " Paul Winalski
2023-06-13  5:28       ` Dave Horsfall
2023-06-13 16:37         ` ron minnich
2023-06-13  0:46 Douglas McIlroy
2023-06-13  1:37 Norman Wilson
2023-06-13  1:41 ` Rob Pike
2023-06-13  1:48 ` Dan Cross
2023-06-13 10:03 Rudi Blom
2023-06-13 12:10 Douglas McIlroy

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='CAEoi9W4kuweQ-fB57G0-Swiy8i0MyZyntf0oQ=wK2mxk+O+iQQ@mail.gmail.com' \
    --to=crossd@gmail.com \
    --cc=chris_pinnock@mac.com \
    --cc=segaloco@protonmail.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).