From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Creating a custom jmp_buf; libthread implementation question
Date: Tue, 14 Nov 2006 07:34:50 -0500 [thread overview]
Message-ID: <ee9e417a0611140434m13221df3l2b3583bf7b52196b@mail.gmail.com> (raw)
In-Reply-To: <775b8d190611140139i4e28842dndd5bede4255b4b11@mail.gmail.com>
Newthread is creating a bunch of data structures.
You really care about _threadinitstack (386.c) and setjmp(2).
"tos" means top of stack.
Russ
next prev parent reply other threads:[~2006-11-14 12:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 3:23 Joel Salomon
2006-11-14 3:33 ` Joel Salomon
2006-11-14 9:39 ` Bruce Ellis
2006-11-14 12:34 ` Russ Cox [this message]
2006-11-14 16:15 ` Joel Salomon
2006-11-21 3:03 ` Joel Salomon
2006-11-21 3:03 ` William Josephson
2006-11-21 3:08 ` Russ Cox
2006-11-14 9:58 ` Gorka guardiola
2006-11-14 16:25 ` Joel Salomon
2006-11-14 16:38 ` Joel Salomon
2006-11-14 19:44 ` Taj Khattra
2006-11-14 5:44 ` [9fans] Skip Tavakkolian
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=ee9e417a0611140434m13221df3l2b3583bf7b52196b@mail.gmail.com \
--to=rsc@swtch.com \
--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).