Having multiple memory references in the same instruction requires this to be done multiple times, which is a massive slowdown, source of hardware complexity, and can make it incredibly hard to guarantee forward progress in the first place. (It's already being done at least 2x,
Maybe you can't _actually_ ever make that work in any kind of efficient way that isn't worse than just using explicit save and restore on thread switches, but I'm not sure I get why.
-
-
In much the same way that "self modifying code" is no longer a thing, "writing to the register memory without calling it a register" could also not be a thing, right - we do that sort of thing all the time.
-
Etc., etc.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.