The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: crt0 -- what's in that name?
Date: Mon, 12 Jun 2023 21:32:58 +0000	[thread overview]
Message-ID: <J9xDtmp4JsVOUARmbmnREts1jNn5GNxyz11fnxnZocn7HOEEV_ux_7kDbV1znHYX61C8kv50j2Bwada8gb_er468PlbMTz_51dHm2s65yXg=@protonmail.com> (raw)
In-Reply-To: <CABH=_VRoig4_KtB5r9T-uAV8pzsHkXjrMEa8EKv6mXBGCVWwXg@mail.gmail.com>

> It may be that crt stood for "compiler run time" back when C was the
> only compiler in town.
> 
> -Paul W.

I don't know about this, only given the fact that B was already there and had a brt1 and brt2, crt0 seems like a natural follow-on to this naming scheme and I would suspect the c in crt0 referring to the language, not "compiler" was probably there from the genesis.  These are the single letter associations I've found:

    - a - assembly as in liba.a
    - b - B lang as in libb.a, brt1, bilib
    - c - C lang as in libc.a, crt0
    - e - Explor as in libe.a
    - f - Fortran as in fc, f77, libf.a, fr0
    - l - LIL as in lc (LIL compiler)
    - m - m6 as in /sys/lang/mdir

Of course letters get reused for things, this logic would imply the LIL language would have a libl.l but that instead is the lex library as appears a little later on.  Y of course eventually gets associated with yacc.  Not affirmative proof but I would be more inclined to suspect the c there is a language reference than standing for "compiler"

- Matt G.

P.S. The "bss" definition that lives in my head is "block-sized storage" but frankly I can't recall where I picked that up.  I feel like I didn't just make that up but Google returns nothing.

  reply	other threads:[~2023-06-12 21:33 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
2023-06-12 20:28           ` Chris Pinnock via TUHS
2023-06-12 20:58             ` Paul Winalski
2023-06-12 21:32               ` segaloco via TUHS [this message]
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='J9xDtmp4JsVOUARmbmnREts1jNn5GNxyz11fnxnZocn7HOEEV_ux_7kDbV1znHYX61C8kv50j2Bwada8gb_er468PlbMTz_51dHm2s65yXg=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.com \
    /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).