From: Paul Winalski <paul.winalski@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:58:48 -0400 [thread overview]
Message-ID: <CABH=_VRoig4_KtB5r9T-uAV8pzsHkXjrMEa8EKv6mXBGCVWwXg@mail.gmail.com> (raw)
In-Reply-To: <F3D3DD69-09F1-4A06-90A6-3459C63B92F9@mac.com>
On 6/12/23, Chris Pinnock via TUHS <tuhs@tuhs.org> wrote:
>
>> 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.
It may be that crt stood for "compiler run time" back when C was the
only compiler in town. But once you get another language, such as
Fortran, that has its own, different runtime initialization
requirements, having the 'c' in crt0 mean "C" rather than "compiler"
because it's no longer common to all compiler run time libraries.
-Paul W.
next prev parent reply other threads:[~2023-06-12 20:58 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 [this message]
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='CABH=_VRoig4_KtB5r9T-uAV8pzsHkXjrMEa8EKv6mXBGCVWwXg@mail.gmail.com' \
--to=paul.winalski@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).