From: Chris Pinnock via TUHS <tuhs@tuhs.org>
To: Dan Cross <crossd@gmail.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 21:28:32 +0100 [thread overview]
Message-ID: <F3D3DD69-09F1-4A06-90A6-3459C63B92F9@mac.com> (raw)
In-Reply-To: <CAEoi9W4kuweQ-fB57G0-Swiy8i0MyZyntf0oQ=wK2mxk+O+iQQ@mail.gmail.com>
> On 12 Jun 2023, at 21:22, Dan Cross <crossd@gmail.com> wrote:
>
> 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").
Possibly - in this file http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/csu/README?rev=1.6&content-type=text/x-cvsweb-markup&only_with_tag=MAIN, the CSU and related files are referred to as the compiler runtime. But startoff is appropriate - because the file was usually included in the binary at the beginning to initialise stuff.
These days ELF formats and similar have specific sections for initing and terminating binaries - although I the crt name lives on with start and end:
servalan: {482} ls -la /usr/lib/crt*
-r--r--r-- 1 root wheel 4328 Jan 14 18:18 /usr/lib/crt0.o
-r--r--r-- 1 root wheel 2648 Jan 14 18:18 /usr/lib/crtbegin.o
-r--r--r-- 1 root wheel 2880 Jan 14 18:18 /usr/lib/crtbeginS.o
lrwxr-xr-x 1 root wheel 10 Jan 14 18:18 /usr/lib/crtbeginT.o -> crtbegin.o
-r--r--r-- 1 root wheel 1264 Jan 14 18:18 /usr/lib/crtend.o
lrwxr-xr-x 1 root wheel 8 Jan 14 18:18 /usr/lib/crtendS.o -> crtend.o
-r--r--r-- 1 root wheel 1488 Jan 14 18:18 /usr/lib/crti.o
-r--r--r-- 1 root wheel 1152 Jan 14 18:18 /usr/lib/crtn.o
>
>
> I thought it was pretty well known that it stands for, "Block Started
> (by) Symbol”?
I wrote a paper on a.out a year or so ago and concluded that I could not find an adequate answer - so avoided the issue with a non-commital footnote.
C
next prev parent reply other threads:[~2023-06-12 20:29 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 [this message]
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=F3D3DD69-09F1-4A06-90A6-3459C63B92F9@mac.com \
--to=tuhs@tuhs.org \
--cc=chris_pinnock@mac.com \
--cc=crossd@gmail.com \
--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).