From: Steve Nickolas <usotsuki@buric.co>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: crt0 -- what's in that name?
Date: Mon, 12 Jun 2023 16:25:31 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2306121624280.30250@sd-119843.dedibox.fr> (raw)
In-Reply-To: <8DE09E23-5348-496B-B1CF-EDE9C47983B2@mac.com>
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
On Mon, 12 Jun 2023, Chris Pinnock via TUHS 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.
I always understood crt to stand for "C runtime".
-uso.
next prev parent reply other threads:[~2023-06-12 20:25 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 [this message]
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=alpine.DEB.2.21.2306121624280.30250@sd-119843.dedibox.fr \
--to=usotsuki@buric.co \
--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).