cfallin

33 ms·

301.
by cfallin 13y ago
I think while interesting, the semantic gap is probably too large. E.g. the machine stores machine words on the stack, but the JVM stores Java values. And the instruction set of the JVM is much richer, and it knows about many more concepts
302.
by cfallin 13y ago
This is certainly an interesting read, and stack machines have a long history among alternative CPU architectures. But I think that the complaints this (admittedly 18-year-old) article levels against mainstream CPUs are largely unfounded wi
303.
by cfallin 13y ago
In addition to what others said about the overhead of context switching just for a DRAM access stall (at today's DRAM latencies, which are ~200 to 400 cycles), there's an architectural issue with the idea, too. Consider that from
304.
by cfallin 14y ago
I think the discussion here is missing the fact that "long boot time" is on the order of milliseconds. From the article: the average time for a ucode update on the test machine was 489k cycles, which at 2.53GHz is 193 microseconds. I hardly
305.
by cfallin 14y ago
GPUs use dynamic RAM too (though discrete cards usually have GDDR rather than DDR, which gives higher bandwidth). The most fundamental difference between a CPU and GPU isn't the memory hierarchy (modern GPUs are growing cache hierarchies as
306.
by cfallin 14y ago
The commands you want are "stepi" (single-step one instruction), "disass" (disassemble at the current point in the program), and "info registers" (show you what's in all of the registers). These work equally well for hand-written assembly a