Why do stacks typically grow downwards?

by

As to the historic rationale, I can’t say for certain (because I didn’t design them). My thoughts on the matter are that early CPUs got their original program counter set to 0 and it was a natural desire to start the stack at the other end and grow downwards, since their code naturally grows upward.

As an aside, note that this setting of the program counter to 0 on reset is not the case for all early CPUs. For example, the Motorola 6809 would fetch the program counter from addresses 0xfffe/f so you could start running at an arbitrary location, depending on what was supplied at that address (usually, but by no means limited to, ROM).

One of the first things some historical systems would do would be to scan memory from the top until it found a location that would read back the same value written, so that it would know the actual RAM installed (e.g., a z80 with 64K address space didn’t necessarily have 64K or RAM, in fact 64K would have been massive in my early days). Once it found the top actual address, it would set the stack pointer appropriately and could then start calling subroutines. This scanning would generally be done by the CPU running code in ROM as part of start-up.

With regard to the stacks growth, not all of them grow downwards, see this answer for details.

More Related Contents:

  1. Logout: GET or POST?
  2. What’s the difference between “Layers” and “Tiers”?
  3. Component based game engine design [closed]
  4. Domain Driven Design: Domain Service, Application Service [closed]
  5. What is N-Tier architecture?
  6. Servicestack – architecture & reusing POCOs for everything
  7. what is a store buffer?
  8. When are you truly forced to use UUID as part of the design?
  9. On 32-bit CPUs, is an ‘integer’ type more efficient than a ‘short’ type?
  10. What am I not understanding about REST?
  11. Microservices – best practices to retrieve the related data to specific user from the other micro services with the minimal memory/time loss
  12. Best way to store Badge criteria?
  13. How do you organize your small reusable cffunctions?
  14. dma vs interrupt-driven i/o
  15. Difference between a “coroutine” and a “thread”?
  16. How to list supported target architectures in clang?
  17. What is opinionated software?
  18. What is a “feature flag”?
  19. How to detect target architecture using CMake?
  20. CMake Multiarchitecture Compilation
  21. DDD, Anti Corruption layer, how-to?
  22. Where should I store photos? File system or the database? [duplicate]
  23. What’s the difference between REST & RESTful
  24. When to Redis? When to MongoDB? [closed]
  25. Macro definition to determine big endian or little endian machine?
  26. When was the NULL macro not 0?
  27. design a stack such that getMinimum( ) should be O(1)
  28. Linux kernel ARM exception stack init
  29. List, IList, IEnumerable, IQueryable, ICollection, which is most flexible return type?
  30. Where does the practice “exists (select 1 from …)” come from?

Leave a Comment