From: "John Ratcliff" <jratcliff@verant.com>
To: <gcc-help@gcc.gnu.org>
Subject: GCC question
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <000701bf573c$ee44be00$47294b0c@amd> (raw)
Message-ID: <20000401000000.dkeXAN8wCMSO76hh9kKLsJ0PXiXL0mDuQZ2VBK1jrXU@z> (raw)
In-Reply-To: <947048956.20674.ezmlm@gcc.gnu.org>
Quick question. I'm looking to put an embedded VM inside my application.
What I want is a C++ compiler that will produce an OS neutral byte code and
I will have a VM to interpret it. I want the VM to be 100% ANSI complient,
OS neutral C or C++ code.
Java seems like the likely candidate, however the Java VM implementations I
have seen are rather huge. One approach would be to have GCC produce, say
80386 code, and then write a C implementation of an 80386 emulator.
Actually not a bad idea....anybody got one laying around?
Is there a version of the GCC compiler that produces OS neutral VM byte code
and a corresponding *small* (very small) byte code interpreter for it,
written in C or C++?
What I want to accomplish is to download OS neutral binaries over the
internet to an application running on completely different processors. One
is a Pentium but the other is a console machine that I am not at liberty to
discuss. As well, there might be more processors I would support in the
future. I want to be able to download and execute these binaries on any of
the machines. I don't need a JIT compiler, that's overkill since this isn't
performance oriented code, mostly high level game logic calling high speed
native routines.
It there a solution short of including the rather massive, huge, and fat,
Java VM? Or, is there a thin, skinny, small Java VM implementation?
Thanks,
John W. Ratcliff
Senior Software Engineer
Verant Interactive
next parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <947048956.20674.ezmlm@gcc.gnu.org>
2000-01-04 21:22 ` John Ratcliff [this message]
2000-04-01 0:00 ` John Ratcliff
2000-01-06 15:46 Black, Christopher T
2000-04-01 0:00 ` Black, Christopher T
2000-04-10 7:46 Gibson, Terry
2000-04-10 8:12 ` Alexandre Oliva
2000-08-13 19:34 gcc question tao tong
2001-07-20 4:35 Steve Kieu
2002-06-12 9:29 j y
2002-06-12 11:16 ` Shawn Starr
2006-02-26 22:53 Brendan Darrer
2006-02-26 23:52 ` Ernest L. Williams Jr.
2006-02-27 15:29 ` Brian Budge
2021-09-08 15:06 HON LUU
2021-09-08 16:20 ` Segher Boessenkool
2021-09-08 16:26 ` HON LUU
2021-09-08 16:27 ` HON LUU
2021-09-08 17:05 ` HON LUU
2021-09-08 23:13 ` HON LUU
2021-09-10 17:58 ` HON LUU
2021-09-10 18:36 ` Segher Boessenkool
2021-09-11 21:08 ` HON LUU
2021-09-13 19:10 ` HON LUU
2021-09-13 19:22 ` Florian Weimer
2021-09-13 19:40 ` HON LUU
2021-09-13 19:42 ` Florian Weimer
2021-09-13 19:50 ` HON LUU
2021-09-13 19:51 ` Florian Weimer
2021-09-13 19:52 ` HON LUU
2021-09-13 19:42 ` HON LUU
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='000701bf573c$ee44be00$47294b0c@amd' \
--to=jratcliff@verant.com \
--cc=gcc-help@gcc.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).