News for hackers. Stuff that matters.
Re:Design and Implementation of a 256-Core BrainFuck Compute... by Someone on Saturday October 15, 2016 @03:01PM (#12715220)
Why is the author consistently mixing up " "instructions per cycle" with "instructions per second"?

Surely, phrases such as "We observed the following Instructions per Second (IPC)" and "assuming a perfect 1 instruction per second on the general purpose processor" should have activated some neurons in some brain, even assuming it got distorted by doing this research?

Re:Design and Implementation of a 256-Core BrainFuck Compute... by sitkack on Saturday October 15, 2016 @03:55PM (#12715426)
Maybe working on a 256 core BF computer has BF'd his brain? Have some empathy.
Re:Design and Implementation of a 256-Core BrainFuck Compute... by nickpsecurity on Saturday October 15, 2016 @07:42PM (#12716144)
That's my guess. It's one of the few projects that I thought actually would damage my brain. I avoided it. Unlambda language is another one like that. Although I have considered trying to implement that one, esp in hardware.
Re:Design and Implementation of a 256-Core BrainFuck Compute... by troels on Saturday October 15, 2016 @04:34PM (#12715551)
Depending on the clock speed, it may be accurate enough?
Re:Design and Implementation of a 256-Core BrainFuck Compute... by jsjohnst on Sunday October 16, 2016 @01:26AM (#12717124)
This greatly annoyed me too. It's IPC not IPS after all. I'm surprised this didn't get caught by literally anyone who reviewed this paper before hitting submit.