dewster

10 ms·

1. 61.▲
   by dewster 10y ago

   I'm not sure why more processors aren't tightly integrated into memory (and vice versa). Physically separating processor and memory with slow package pins means caches and all the real-time headaches and complexity and die size &
2. 62.▲
   by dewster 10y ago

   People who design stack processors like to say they're Forth or Java machines. IMO it's more buzz-word than anything else. I think we know now that tailoring a processor to a particular language isn't particularly efficient
3. 63.▲
   by dewster 10y ago

   "...has anyone asked and tried to analytically answer what primitive operations an ALU ought to have?" Very good question. I think this is where the "art" of computer design starts, and it generally gets short shrift.
4. 64.▲
   by dewster 10y ago

   Thanks for the link to that thesis! Appendix E describes I believe what Hive does: a separate bit associated with the operand selector is used to control pop behavior. I'll have to credit this paper in mine (nothing ever really new un
5. 65.▲
   by dewster 10y ago

   Thanks for the blog pointer, an interesting read. As the blog author points out, local variables are a huge issue on a stack machine because they lead to stack thrash. ANY stack manipulation must be seen as fundamentally inefficient, and t
6. 66.▲
   by dewster 10y ago

   Or try my Hive soft processor core: http://opencores.org/project,hive I need to update the paper and code, the core is at v9.03 and the simulator can now parse assembly code as input. IMO canonical stack processors aren&#x2
7. 67.▲
   by dewster 11y ago

   This article is a poster child for what's wrong with modern HW & SW. Cortex-M0+ has no CLZ?!? WTF they thinking? And all the bugfixes around wrappers around enigmas are a joke. Computing shouldn't be this arcane.