Hacker News Reader

Comment by WallWextra | Hacker News Reader

Sometimes I wonder how much better off we'd be with something exactly like x86, but with a stack that grows upwards.

A stack that grows upwards means that you exploit the return address of called functions instead of your current function.

    void dangerous() {
      char buf[10];
      gets(buf);  // the return in gets could be redirected
    }

If the buffer is on the stack and being overflowed by the function that declared it, not some callee.

not much, wouldn't matter.

what you REALLY should wonder is, something like x86, but with code pointers stored in a separate address space.

We kinda already had this with the old segmented memory model. That AMD mostly dropped support for it in x86_64 should tell you something.