search for: stacklings

Hi Duncan, It doesn't appear to be what I'm looking for as there is copying of the old stack to the new stack. Additionally, according to the LLVM docs on segmented stacks (http://llvm.org/releases/3.0/docs/SegmentedStacks.html) the stacklings are allocated memory from the heap. Since this places them all on the same memory segment, a read/write from one stackling could technically overflow to read/write another stackling ... unless there is something I've overlooked or is undocumented. What I've been looking at currently is a s...

...rent.gregory.roth at gmail.com> wrote: > Hi Duncan, > > It doesn't appear to be what I'm looking for as there is copying of the old stack to the new stack. Additionally, according to the LLVM docs on segmented stacks (http://llvm.org/releases/3.0/docs/SegmentedStacks.html) the stacklings are allocated memory from the heap. Since this places them all on the same memory segment, a read/write from one stackling could technically overflow to read/write another stackling ... unless there is something I've overlooked or is undocumented. > > What I've been looking at curren...

Hi Brent, On 03/06/13 14:32, Brent Gregory Roth wrote: > Hi Duncan, > > Are the segmented stacks actually on separate memory segments? My intended > purpose for placing different datatypes on separate stacks is such that memory > accesses to one datatype won't be allowed to overflow to another datatype. > > If they aren't, in fact, on separate memory segments, are you

Hi Duncan, Are the segmented stacks actually on separate memory segments? My intended purpose for placing different datatypes on separate stacks is such that memory accesses to one datatype won't be allowed to overflow to another datatype. If they aren't, in fact, on separate memory segments, are you aware of a way to place a non-readable/-writable segment in between two other stack