The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: crt0 -- what's in that name?
Date: Mon, 12 Jun 2023 17:31:20 -0400	[thread overview]
Message-ID: <CAC20D2PiOh-p48G83ChUYZnfHTdNXROcJsewwmbM1xnyrt4c9w@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2306130615560.16633@aneurin.horsfall.org>

[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]

On Mon, Jun 12, 2023 at 4:17 PM Dave Horsfall <dave@horsfall.org> wrote:

> On Mon, 12 Jun 2023, Dan Cross wrote:
>
> > 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.
>
> I've always thought of it as "C run time stage 0".
>
crt - C RunTme.   I always heard it expressed as C  runtime SYSTEM or START

WRT to BSS -- Block Start Symbol (and sometimes Block End Symbol in some
later assemblers) I believe was (were) part of the original 704 assemblers
from United Aircraft reserving a labeled block of uninitialized space in a
"DUMMY SECTION" (or DSECT) for a hunk of storage.  The OS is going to load
everything together. So, a big feature of the United Aircraft assembler was
to help control memory layout and collect like (common) hunks of things
together (i.e., code vs data).  The whole idea of BSS was to get the loader
to reserve space that did not have to initialized.  As I understand it, the
standard IBM FORTRAN (FAP) and Assembler (MAP) for the 709 and 7090/94
picked it up, with the new FORTRAN compiler being the big driver.
ᐧ

[-- Attachment #2: Type: text/html, Size: 2374 bytes --]

  reply	other threads:[~2023-06-12 21:32 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
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 [this message]
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=CAC20D2PiOh-p48G83ChUYZnfHTdNXROcJsewwmbM1xnyrt4c9w@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=dave@horsfall.org \
    --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).