From: Iruata Souza <iru.muzgo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 8l(1) PUSH/POP
Date: Fri, 6 Nov 2009 11:58:15 -0200 [thread overview]
Message-ID: <d1c554290911060558vbab3e89le6d45c1aa2565bce@mail.gmail.com> (raw)
In-Reply-To: <c9d8315c2fde6c8dea928f2ae0ac3f10@brasstown.quanstro.net>
On Fri, Nov 6, 2009 at 11:24 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>> what is the reason behind 8l(1) not allowing unbalanced PUSH/POP?
>
> i'm not sure of the original reason, but unbalanced
> push/pop could conflict with the linker's automatic
> stack management. also, i'm not sure what the
> general application would be unless you want to do
> continuations.
>
> what's the application?
>
> if you're setting up a first process, i believe you can
> still modify the stack pointer directly and do a stack-
> relative move.
>
the application is a pbs. for now i'm doing a stack-relative move, but
i'd rather use a pop.
disabling the restriction has shown no regressions in the pbs yet.
and i couldn't seem to find the same restriction in vl(1) for example.
iru
next prev parent reply other threads:[~2009-11-06 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<d1c554290911060422q45dd90cq4a37ec9a9c6ecce6@mail.gmail.com>
2009-11-06 13:24 ` erik quanstrom
2009-11-06 13:50 ` Bruce Ellis
2009-11-06 13:58 ` Iruata Souza [this message]
[not found] <<d1c554290911060558vbab3e89le6d45c1aa2565bce@mail.gmail.com>
2009-11-06 14:09 ` erik quanstrom
2009-11-06 14:25 ` Iruata Souza
[not found] <<775b8d190911060550u49d33fcaj193f053657e55159@mail.gmail.com>
2009-11-06 14:08 ` erik quanstrom
2009-11-06 14:49 ` Bruce Ellis
2009-11-06 12:22 Iruata Souza
2009-11-06 14:33 ` Eris Discordia
2009-11-06 16:58 ` Charles Forsyth
2009-11-06 17:02 ` Iruata Souza
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=d1c554290911060558vbab3e89le6d45c1aa2565bce@mail.gmail.com \
--to=iru.muzgo@gmail.com \
--cc=9fans@9fans.net \
/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).