From: "Douglas A. Gwyn" <gwyn@arl.army.mil>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] the declaration of main()
Date: Thu, 26 Apr 2001 16:05:15 +0000 [thread overview]
Message-ID: <3AE840B1.17EF07D7@arl.army.mil> (raw)
In-Reply-To: <006a01c0ccb7$5990b0b0$95b9c6d4@SOMA>
Boyd Roberts wrote:
> yep, IIRC, sounds like the 7th ed /lib/crt0.s which eventually
> called _exit() [the syscall]. exit() was a library function
> which did the above and then called _exit().
I think there was a linker trick (similar to the floating-point
trick) to get the appropriate runtime startup behavior depending
on whether stdio functions had been invoked or not; at least,
when I tried the experiment on 7th Ed. UNIX at the time I
posted (to make sure I remembered correctly), the flushing
version of exit() got invoked from the startup function.
Note that in PDP-11 UNIX C, C externs have an underscore
prefixed to them at the linker level; so _exit in assembler
corresponds to exit() in C. There is also _exit() in C, i.e.
__exit in assembler, which is the plain system call you
described, but from assembler one would not call that extern
function but would rather use a "sys" (TRAP) instruction
with the proper subcode to select the exit syscall. There
were (optional) assembler macros for the syscall subcodes.
next prev parent reply other threads:[~2001-04-26 16:05 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 11:09 forsyth
2001-04-23 11:31 ` Boyd Roberts
2001-04-24 9:02 ` Douglas A. Gwyn
2001-04-24 12:09 ` Boyd Roberts
2001-04-26 16:05 ` Douglas A. Gwyn [this message]
2001-04-26 18:12 ` Boyd Roberts
2001-04-26 23:55 ` Boyd Roberts
2001-04-24 17:43 ` Greg Hudson
2001-04-26 15:55 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2001-04-30 12:05 rob pike
2001-04-30 10:44 forsyth
2001-04-28 18:44 forsyth
2001-04-30 9:24 ` Douglas A. Gwyn
2001-04-28 17:57 forsyth
2001-04-28 22:28 ` Dan Cross
2001-04-30 9:25 ` Douglas A. Gwyn
2001-04-27 6:57 nemo
2001-04-26 20:58 forsyth
2001-04-27 9:13 ` Douglas A. Gwyn
2001-04-27 14:48 ` Boyd Roberts
2001-04-27 16:22 ` Douglas A. Gwyn
2001-04-27 18:24 ` William K. Josephson
2001-04-30 9:23 ` Douglas A. Gwyn
2001-04-27 19:38 ` Boyd Roberts
2001-04-28 15:54 ` Greg Hudson
2001-04-28 16:39 ` Dan Cross
2001-04-28 17:06 ` Boyd Roberts
2001-04-30 9:25 ` Douglas A. Gwyn
2001-04-26 19:42 Russ Cox
2001-04-26 20:32 ` Dan Cross
2001-04-26 22:03 ` Boyd Roberts
2001-04-27 9:13 ` Douglas A. Gwyn
2001-04-26 18:23 forsyth
2001-04-26 19:17 ` Mike Haertel
2001-04-26 23:50 ` Boyd Roberts
2001-04-27 14:41 ` Douglas A. Gwyn
2001-04-27 15:40 ` Boyd Roberts
2001-04-27 9:12 ` Douglas A. Gwyn
2001-04-24 10:32 rog
2001-04-24 18:03 ` Steve Kilbane
2001-04-24 8:10 forsyth
2001-04-26 15:55 ` Douglas A. Gwyn
2001-04-24 0:59 okamoto
2001-04-24 3:08 ` Boyd Roberts
2001-04-23 19:33 dmr
2001-04-12 6:28 okamoto
2001-04-23 8:44 ` Douglas A. Gwyn
2001-04-23 8:48 ` Boyd Roberts
2001-04-12 6:22 YAMANASHI Takeshi
2001-04-12 6:25 ` andrey mirtchovski
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=3AE840B1.17EF07D7@arl.army.mil \
--to=gwyn@arl.army.mil \
--cc=9fans@cse.psu.edu \
/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).