From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] long lived programs
Date: Fri, 23 Mar 2018 13:31:49 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.02.1803231329210.43710@frieza.hoshinet.org> (raw)
In-Reply-To: <C18A05EC-8E01-4716-9B99-51AD7AF4D420@serissa.com>
On Fri, 23 Mar 2018, Lawrence Stewart wrote:
> Suppose we define a machine architecture not for building hardware, but
> specifically for itself being easy to emulate?
>
> This is by analogy to para-virtualized device drivers, which are not
> there to model real devices, but to be easy to support in a virtual
> machine environment.
I've had an idea to create a sort of idealized VM for running C in (like a
JVM designed specifically for C) and a full VM-OS type thing as well - but
I couldn't figure out how to go about implementing it. Still...sounds
similar to what you propose, which might not be a bad idea.
-uso.
next prev parent reply other threads:[~2018-03-23 17:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 15:51 Ron Natalie
2018-03-23 15:57 ` Clem Cole
2018-03-23 16:25 ` Lars Brinkhoff
2018-03-23 16:59 ` Lawrence Stewart
2018-03-23 17:31 ` Steve Nickolas [this message]
2018-03-23 16:32 ` Ron Natalie
2018-03-23 18:27 [TUHS] long lived programs (was Re: RIP John Backus Bakul Shah
2018-03-23 20:50 ` [TUHS] long lived programs Steve Johnson
2018-03-23 21:07 ` Clem Cole
2018-04-05 21:03 Norman Wilson
2018-04-05 21:23 ` Clem Cole
2018-04-05 21:38 ` Bakul Shah
2018-04-06 2:03 ` Random832
2018-04-06 4:27 ` Warner Losh
2018-04-06 4:31 ` Jon Steinhart
2018-04-06 4:58 ` Steve Nickolas
2018-04-06 5:02 ` Jon Steinhart
2018-04-06 4:29 ` Steve Johnson
2018-04-06 5:57 ` Bakul Shah
2018-04-06 21:52 ` Peter Jeremy
2018-04-05 22:46 ` Arthur Krewat
2018-04-05 23:23 ` Paul Winalski
2018-04-05 23:33 ` Arthur Krewat
2018-04-06 0:05 ` Toby Thain
2018-04-06 4:51 ` Dave Horsfall
2018-04-06 15:00 ` Tony Finch
2018-04-07 20:41 ` Paul Winalski
2018-04-06 22:33 Doug McIlroy
2018-04-07 1:01 ` Paul Winalski
2018-04-07 1:09 ` Larry McVoy
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=alpine.BSF.2.02.1803231329210.43710@frieza.hoshinet.org \
--to=usotsuki@buric.co \
/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).