News for hackers. Stuff that matters.
Re:The Burroughs B5000 - 20 Years Later and Still Ahead of t... by tedunangst on Tuesday May 22, 2012 @06:33PM (#4010477)
I would love to know what that benchmark is. I feel pretty confident I could cherry pick a benchmark that runs a lot faster than 50x on modern hardware. Some variant of Amdahl's law probably applies here.
Re:The Burroughs B5000 - 20 Years Later and Still Ahead of t... by DanBC on Tuesday May 22, 2012 @07:50PM (#4010723)
Maybe this email list has some details?

(http://lists.canonical.org/pipermail/kragen-tol/2007-March/0...)

Here's a mildly interesting rant:

(http://www.yosefk.com/blog/the-high-level-cpu-challenge.html)

This post doesn't give any details of the benchmark, but describes another test (boot, load word processor, open document, close wp, shut down) and compares an old mac and a (at the time) modern laptop.

(http://tekkie.wordpress.com/2009/08/12/does-computer-science...)

Re:The Burroughs B5000 - 20 Years Later and Still Ahead of t... by tedunangst on Tuesday May 22, 2012 @08:07PM (#4010779)
Thank you. Looks like I'm not the first to ask. Doubt I'll be the first to get an answer.

Wrt the last post, I'll note my openbsd laptop can complete that challenge before many other machines have made it past post, so all hope is not lost.

And we had wysiwyg HTML editors eons ago. The switch to online markdown editors was a trade off, but it's not like the secrets of the ancients were lost when the library of parc was burned to the ground.

Re:The Burroughs B5000 - 20 Years Later and Still Ahead of t... by ScottBurson on Tuesday May 22, 2012 @09:54PM (#4011107)
I'll hazard a guess as to what's going on here. The OP mentions the B5000's use of descriptors. I think it's decoding a descriptor and doing bounds checking on every array access. That would certainly slow down a machine that didn't have hardware support for these operations.
Re:The Burroughs B5000 - 20 Years Later and Still Ahead of t... by tedunangst on Tuesday May 22, 2012 @10:54PM (#4011286)
That's a fairly trivial optimization for a jit to perform. And a 1000x penalty for bounds checking? No way, that would literally require your bounds check to take a minimum of 1000 instructions, even assuming your inner loop didn't do anything meaningful with the accessed value.