From: Alexander Graf <agraf@suse.de>
To: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
Cc: Stefan Reinauer <stepan@coresystems.de>,
The OpenBIOS Mailinglist <openbios@openbios.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] M68K Or PPC Status Update to Run Mac OS in Qemu
Date: Tue, 22 Dec 2009 14:56:50 +0100 [thread overview]
Message-ID: <4B30D022.6050400@suse.de> (raw)
In-Reply-To: <4B30CD18.7050401@siriusit.co.uk>
Mark Cave-Ayland wrote:
> Alexander Graf wrote:
>
>> OpenBIOS is missing an implementation for local variables. See this
>> thread:
>> http://www.openfirmware.info/pipermail/openbios/2009-July/003796.html
>>
>> Alex
>
> How do local variables work? Are they just substitutions for stack
> places?
I seriously am the last person to know anything about Forth :-). But I'm
sure Stefan can help out here. He's been looking into that before.
> If you can point me towards a specification for this, I can have a
> look and see how feasible it would be to add this to OpenBIOS.
1)
http://www.complang.tuwien.ac.at/viewcvs/cgi-bin/viewcvs.cgi/gforth/locals.fs?rev=1.8&view=markup
2) http://www.openfirmware.info/FCODE_suite
-> see "local value support"
-> has an incompatible license
-> contains links to documentation IIRC
3) http://www.forthos.org/
-> claims to have local value support, haven't found the sources yet
The code BootX executes:
http://www.openfirmware.info/pipermail/openbios/2009-July/003812.html
Alex
next prev parent reply other threads:[~2009-12-22 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4b2f2099.9d53f10a.2eb2.4a1dSMTPIN_ADDED@mx.google.com>
2009-12-21 17:37 ` [Qemu-devel] M68K Or PPC Status Update to Run Mac OS in Qemu G 3
2009-12-21 17:59 ` Alexander Graf
2009-12-22 13:43 ` Mark Cave-Ayland
2009-12-22 13:56 ` Alexander Graf [this message]
2009-12-20 20:32 Leo B
2009-12-20 22:23 ` Alexander Graf
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=4B30D022.6050400@suse.de \
--to=agraf@suse.de \
--cc=mark.cave-ayland@siriusit.co.uk \
--cc=openbios@openbios.org \
--cc=qemu-devel@nongnu.org \
--cc=stepan@coresystems.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).