Architectures with a non-contiguous stack?

From: Adam Warner (usenet_at_consulting.net.nz)
Date: 01/31/05 

Date: Mon, 31 Jan 2005 17:02:49 +1300

Hi all,

If I write an otherwise conforming ISO C program that makes a single
non-portable assumption--that the stack is contiguous (in order to cheaply
distinguish addresses into the stack from addresses of explicitly malloc'd
or mmap'd memory)--are there any architectures in common use where my
program may break?

So far I've only found the Acorn Archimedes has a non-contiguous stack,
which for my purposes is merely of historical interest.

Many thanks,
Adam

Relevant Pages

  • Re: Architectures with a non-contiguous stack?
    ... Dave Vandervies wrote: ... >> If I write an otherwise conforming ISO C program that makes a ... Why do you want to distinguish stack from ... the broken "Reply" link at the bottom of the article. ...
    (comp.programming)
  • Re: Architectures with a non-contiguous stack?
    ... >>If I write an otherwise conforming ISO C program that makes a single ... >>distinguish addresses into the stack from addresses of explicitly malloc'd ... I somehow doubt that a program running in these environments would look ...
    (comp.programming)
  • Re: Architectures with a non-contiguous stack?
    ... Adam Warner wrote: ... >If I write an otherwise conforming ISO C program that makes a single ... >distinguish addresses into the stack from addresses of explicitly malloc'd ... There are a number of programming environments, ...
    (comp.programming)
  • Re: Architectures with a non-contiguous stack?
    ... Adam Warner wrote: ... >If I write an otherwise conforming ISO C program that makes a single ... Implementations on some IBM mainframes use heap-allocated stack frames, ... its inexact as well as being inexact. ...
    (comp.programming)