From: erik quanstrom <quanstro@quanstro.net>
To: weigelt@metux.de, 9fans@9fans.net
Subject: Re: [9fans] GNU/Linux/Plan 9 disto
Date: Sun, 21 Aug 2011 13:27:47 -0400 [thread overview]
Message-ID: <d1057ce75c0f57e849006a0e13310721@ladd.quanstro.net> (raw)
In-Reply-To: <20110821162029.GB18887@nibiru.local>
> * Charles Forsyth <forsyth@terzarima.net> wrote:
> > >waserror() depends on callee-save.
> >
> > caller-save, and a few other conventions (or rather, no need for more conventions).
> > specifically, it's enough to save the pc and stack. all variables will
> > have the right values on non-zero return from setjmp, regardless of the
> > presence or absence of "volatile", and that return can be done by
> > simply setting the pc and the stack pointer to the values in the jmp_buf.
>
> What exactly is different between these calling conventions ?
http://en.wikipedia.org/wiki/Calling_convention
> How much does the Plan9 code depend on them ?
since you haven't specified a unit with which to measure
this dependency, i'll give it as 1.773 µdirac/tatum·fortnight.
alternatively, i've seen this specified as 6.773 Mlenat·emacs.
(it just looks stupendous when you think of it that way.)
in other words, it's not a deep dependency, but a pervasive
and difficult to dislodge one. without the convention, waserror()
becomes too subtile and quick to anger to be of any use to
mortal programmers.
- erik
next prev parent reply other threads:[~2011-08-21 17:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 16:05 rbnsw-plan9
2011-07-11 16:41 ` Jens Staal
2011-07-11 16:59 ` Gorka Guardiola
2011-07-11 19:31 ` Charles Forsyth
2011-07-12 5:59 ` Pavel Zholkover
2011-07-12 15:13 ` [9fans] Plan 9 Go (Was: GNU/Linux/Plan 9 disto) Lucio De Re
2011-07-12 18:35 ` Francisco J Ballesteros
2011-07-13 18:31 ` Lucio De Re
2011-07-13 18:45 ` Lucio De Re
2011-07-14 18:59 ` stephano zanzin
2011-07-14 20:21 ` Lucio De Re
2011-07-14 20:35 ` Iruatã Souza
2011-07-15 2:37 ` Fazlul Shahriar
2011-07-22 4:40 ` Lucio De Re
2011-07-22 14:37 ` Ethan Grammatikidis
2011-07-27 2:55 ` kokamoto
2011-07-12 18:44 ` Skip Tavakkolian
2011-07-12 12:35 ` [9fans] GNU/Linux/Plan 9 disto Ethan Grammatikidis
2011-07-12 5:50 ` Jens Staal
[not found] ` <CACm3i_j1dxqY=sfunozAXRY+uhO83BnTodfpWvNb+4rSNouC_g@mail.gmail.c>
2011-07-11 17:43 ` erik quanstrom
2011-07-11 19:29 ` Charles Forsyth
2011-08-21 16:20 ` Enrico Weigelt
2011-08-21 17:27 ` erik quanstrom [this message]
2011-08-21 16:16 ` Enrico Weigelt
2011-07-11 17:56 ` hiro
[not found] ` <CAFSF3XO7ejhGBq5Zqj1oL7UnnPf7naTtwbG56hN4k1fz3koxBw@mail.gmail.c>
2011-07-11 18:12 ` erik quanstrom
2011-07-12 0:10 ` hiro
2011-07-12 13:35 ` Ethan Grammatikidis
2011-07-12 17:18 ` hiro
2011-07-12 18:09 ` Richard Miller
2011-07-12 19:08 ` Ethan Grammatikidis
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=d1057ce75c0f57e849006a0e13310721@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=weigelt@metux.de \
/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).