News for hackers. Stuff that matters.
Re:MakerLisp Machine by mruts on Wednesday February 27, 2019 @09:49AM (#19263550)
A Lisp machine isn't just some hardware with Lisp on top. You can do that today with x86. A Lisp machine is supposed to have support for lisp primitives at a hardware level.
Re:MakerLisp Machine by rjsw on Wednesday February 27, 2019 @10:54AM (#19263966)
The MIT Lisp Machine didn't have lisp primitives in hardware. It had two extra hardware features, it could fetch two 16bit instructions at a time, and a fast multi-way branch instruction. Other than that it looked very much like a modern RISC architecture.

I would say that the main feature of a Lisp Machine is that you do everything from within Lisp.

Re:MakerLisp Machine by lispm on Wednesday February 27, 2019 @11:41AM (#19264344)
The architecture the developer saw on a Lisp Machine like a Symbolics was tagged, 36 or 40 bit, mostly stack oriented and had lots of primitive Lisp functionality, type checking /dispatching, some GC support, etc.
Re:MakerLisp Machine by rjsw on Wednesday February 27, 2019 @11:58AM (#19264595)
That was all done in software on the MIT/LMI/TI machines.

I don't know of any papers on the Symbolics hardware that are not behind the ACM paywall, how much did it really differ from the other Lisp Machines ?

Re:MakerLisp Machine by pinewurst on Wednesday February 27, 2019 @12:04PM (#19264676)
Re:MakerLisp Machine by lispm on Wednesday February 27, 2019 @01:55PM (#19265877)
Re:MakerLisp Machine by mruts on Wednesday February 27, 2019 @12:55PM (#19265298)
If that was the case, why are we talking about lisp machines vs a lisp OS?
Re:MakerLisp Machine by Y_Y on Wednesday February 27, 2019 @09:59AM (#19263601)
What about microcode? I thought the point of this whole computing thing was that we could abstract away the fine details and solve problems on the level they're posed at. Who gives a damn if there's a single atom representing a cons or not?

Lisp is good as a language for humans, and it used to be used in hardware because that was necessary to run lisp code fast. That hasn't been the case for ages.

Re:MakerLisp Machine by stcredzero on Wednesday February 27, 2019 @12:24PM (#19264922)
Who gives a damn if there's a single atom representing a cons or not?

Hipsters?

Re:MakerLisp Machine by qubex on Wednesday February 27, 2019 @10:25AM (#19263771)
The stated processor (Zilog/Z80) is not suitable for that and isn’t suitable for emulating such an architecture in real time or instantiating suitable virtual machines.
Re:MakerLisp Machine by andreer on Wednesday February 27, 2019 @10:27AM (#19263786)
I find this to be an interesting question. Given a modern, high-performance compiling lisp implementation on a modern CPU, say SBCL on x86_64.

What modification or addition to the CPU (or wider computer architecture) would be most effective in making typical lisp programs run faster?

Re:MakerLisp Machine by m463 on Thursday February 28, 2019 @12:37AM (#19269178)
So it needs an Address register and a Data register?

Or does it need hardware parenthesis support too? ;)

Re:MakerLisp Machine by qubex on Wednesday February 27, 2019 @10:23AM (#19263753)
Yup. As soon as I reached “Zilog/Z80” I thought “yeah, uhm, nope”.
Re:MakerLisp Machine by 4thaccount on Wednesday February 27, 2019 @12:47PM (#19265191)
It's fine as a toy, but yea I'd prefer a powerhouse chip to make it worthwhile.
Re:MakerLisp Machine by CoolGuySteve on Wednesday February 27, 2019 @12:30PM (#19264995)
What instruction extensions would you have to add to something like RISC-V to accelerate Lisp Machines?
Re:MakerLisp Machine by jecel on Wednesday February 27, 2019 @02:26PM (#19266152)
The previous design, RISC-IV (named SPUR), was a Lisp machine.

http://pages.cs.wisc.edu/~markhill/papers/computer86_spur.pd...

The basic instructions (Table 3) are close enough to RISC-V but it also had a few Lisp specific instructions (Table 4). Though the name J Extension for RISC-V might lead you to think it is only about Java or Javascript, the group working on it is also interested in making it as good as possible for Lisp.