News for hackers. Stuff that matters.
Re:To reinvent the processor by h2odragon on Saturday May 11, 2019 @12:29PM (#19886944)
I almost understand some of these words :) Truly this is fascinating and makes me want to learn about the many things i do not grasp yet. Thank you.

> Register hazards are an unavoidable consequence from using a limited number of names to refer to an unbounded to number of source-level values

yet I seem to recall seeing compiler writers lament the paucity of registers too. Perhaps "registers" itself as a concept is something we should trade in for named memory spaces or something.

gimme instruction level access to all of what is now cache. (chuck all the cache handler logic btw). let me page in and out sections of that to main memory or the inter cpu or io busses, but otherwise its all storage and the real difference is latency.

if we want to burn hardware there could be special graded coherency memory areas or transactional or content addressable.

Re:To reinvent the processor by deepnotderp on Saturday May 11, 2019 @12:54PM (#19887110)
> Perhaps "registers" itself as a concept is something we should trade in for named memory spaces or something

Please no, however hard you think register renaming is, memory disambiguation is harder.

Re:To reinvent the processor by h2odragon on Saturday May 11, 2019 @01:05PM (#19887173)
Hey I'll argue for self modifying code if you let me :). Don't let it be ambiguous. I may be trying to express "don't add abstractions" let the hardware limits show, in ignorance of what the hardware limits are.