From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!news2.kpn.net!news.kpn.net!nslave.kpnqwest.net!nloc2.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader2.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: TAoCP (MMIX) was Re: new to lisp References: <87ofhivcg9.fsf@darkstar.cartan> <3225694045810240@naggum.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3225738779151315@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 24 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Mar 2002 22:32:46 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader2.kpnqwest.net 1016749966 193.71.199.50 (Thu, 21 Mar 2002 23:32:46 MET) NNTP-Posting-Date: Thu, 21 Mar 2002 23:32:46 MET Xref: archiver1.google.com comp.lang.lisp:29776 * "Geoff Summerhayes" | Have you taken a look at his new toy, MMIX? No, I have not even heard about it. Is it used in the next edition of TAoCP and the remaining volumes? | 256 64-bit gp registers, 32 special registers, and 2^64 bytes VM. Heh, I like. That probably also means Unicode characters, instead of the rather bizarre character set used in MIX. :) It might be more work to implement an emulator, however. A MIX emulator is not that easy, either, due to the TeX-like random complexity. | Some posters in c.l.forth are livid about register overkill, lack of | `proper' stack support (the J register is alive and well), combining | float and integer support in a register, not to mention the number of | transitors it would take to implement the design. I would worry more about the cost of context switching on this design. /// -- In a fight against something, the fight has value, victory has none. In a fight for something, the fight is a loss, victory merely relief.