From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: What's the spec for emacs lisp virtual machine ?
Date: Mon, 02 Aug 2010 15:35:41 -0400 [thread overview]
Message-ID: <barmar-CA87E6.15354102082010@reserved-multicast-range-not-delegated.example.com> (raw)
In-Reply-To: 80cc90dc-d66b-4d93-9ff9-dccacec01770@c10g2000yqi.googlegroups.com
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
In article
<80cc90dc-d66b-4d93-9ff9-dccacec01770@c10g2000yqi.googlegroups.com>,
Fren Zeee <frenzeee@gmail.com> wrote:
> On Jul 29, 8:51 pm, mdj <mdj....@gmail.com> wrote:
> > Thirdly, it is relatively straightforward to implement a portable
> > bytecode interpreter in C that will then compile on any architecture
> > for which one has a C compiler. This is a great deal less work than
> > developing a 'to-machine-code' compiler for every architecture out
> > there.
>
> Why is it less than porting the C compiler ? How would it be written ?
> assembler ?
It isn't less, it's very similar. But since someone has already done
the C compiler, you don't need to do it at all. You can simply write a
byte-code interpreter once, and it will run on all the machines that
have C compilers.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
prev parent reply other threads:[~2010-08-02 19:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 6:12 What's the spec for emacs lisp virtual machine ? Fren Zeee
2010-07-23 8:34 ` Pascal J. Bourguignon
2010-07-23 15:59 ` Fren Zeee
2010-07-23 16:01 ` Fren Zeee
2010-07-23 16:03 ` Fren Zeee
2010-07-23 16:41 ` Pascal J. Bourguignon
2010-07-23 17:57 ` Barry Margolin
2010-07-23 16:40 ` Pascal J. Bourguignon
2010-07-30 3:51 ` mdj
2010-07-30 5:01 ` Fren Zeee
2010-07-30 5:28 ` mdj
2010-07-30 5:41 ` Fren Zeee
2010-08-02 19:35 ` Barry Margolin [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=barmar-CA87E6.15354102082010@reserved-multicast-range-not-delegated.example.com \
--to=barmar@alum.mit.edu \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).