From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Sat, 10 Jun 2006 01:37:28 -0300 From: "=?ISO-8859-1?Q?Iruat=E3_Souza_(muzgo)?=" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] gcc on plan9 In-Reply-To: <20060610010019.GE2291@submarine> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8ccc8ba40606091433x10906535x6ade0c3f4ce7a199@mail.gmail.com> <20060609222222.E4AFD294C1@mail.bitblocks.com> <20060610010019.GE2291@submarine> Topicbox-Message-UUID: 6720094a-ead1-11e9-9d60-3106f5b1d025 > * there's no sane way to map LISP into modern hardware. Whether > we like it or not, the modern CPUs are really C language VMs > all the MMU business is there only to support a particular language > construct called pointers, yet let more than one process run > on a system. Sun has done some pretty cool things with trying > to build a hardware version of JavaVM and that thing had a > potential: no MMU, etc. but it got hit with a different evolutionary > artifact of the modern hardware -- the cache. Basically there > were no sane way to map the Garbage Collection into the hardware. I don't know if this is a silly question but could you explain me (privately if so you wish) what's is the big issue with that (GC hardware mapping)? > * LISP makes it harder for nonLISP things to reuse system components. > Or at least it feels that way to me: suppose we end up with an ultra > efficient hardware implementation of a LISP system -- but can we build > a Java layer on top of it ? What about /bin/rc layer ? What about > awk layer ? How would these three talk to each other on such a system ? > What do you mean by 'layer'? Does a prolog interpreter written is Lisp satisfies your definition? I have somewhere in my bookmarks an emulator of the MIT CADR Lisp Machine for x86 machines (for UN*X I guess). Let me know if you want that link to answer some of your questions. iru (muzgo)