From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] too good to pass up (SRB Comments)
Date: Mon, 1 May 2006 10:21:47 +0100 [thread overview]
Message-ID: <a3265d0f74986b0f2ab4539e19a53ced@hamnavoe.com> (raw)
In-Reply-To: <0235beb8cfc35ad17c89ddf4b39a6cc7@collyer.net>
> Did you modify all the `stak'
> macros and functions also to increase the break as needed?
I must have done.
On the other hand, the C stack (for all programs, not just sh)
had a fixed size determined at ld time, because I decided to
have the stack grow downwards as it did on the pdp11, even though
the interdata could only extend memory segments upwards. I was
worried that all sorts of things might break if the stack went
the other way, but in hindsight this was probably the biggest
mistake I made in that project.
next prev parent reply other threads:[~2006-05-01 9:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 13:30 erik quanstrom
2006-04-28 21:13 ` geoff
2006-04-28 21:06 ` quanstro
2006-04-30 10:35 ` Richard Miller
2006-05-01 1:01 ` geoff
2006-05-01 9:21 ` Richard Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-28 13:01 [9fans] too good to pass up erik quanstrom
2006-04-28 13:10 ` [9fans] too good to pass up (SRB Comments) Brantley Coile
2006-05-02 6:32 ` Roman Shaposhnik
2006-05-01 21:22 ` Taj Khattra
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=a3265d0f74986b0f2ab4539e19a53ced@hamnavoe.com \
--to=9fans@hamnavoe.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).