Re: Proposed addition of malloc_size_np()
- From: "Poul-Henning Kamp" <phk@xxxxxxxxxxxxxx>
- Date: Tue, 28 Mar 2006 13:11:56 +0200
In message <20060328105833.GE87799@xxxxxxxxxxxxxxxxxx>, Andrew Reilly writes:
On Tue, Mar 28, 2006 at 12:39:06PM +0200, Poul-Henning Kamp wrote:
Nope, not even close.
What Recursiv did was novel in that the objects lived in hardware
and microcode, there were no way to overrun an array, because you
simply couldn't index it outside it's bounds. Not even in the
operating system.
How is that different from all of the preceding segmented
machines like (to quote your .sig) the Z8001+MMU?
On segmented architectures, all the way back, you put multiple
objects in one segment.
The traditional UNIX way had two or three segments, all of the code
in one and all of the data (+/- the stack) in another.
What Rekursiv did was to put each single variable or object
in its own segment.
int i;
int j;
would take two objects (or segments if you like).
This is not merely segmentation, this is object oriented memory.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@xxxxxxxxxxx | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: Proposed addition of malloc_size_np()
- From: Andrew Reilly
- Re: Proposed addition of malloc_size_np()
- References:
- Re: Proposed addition of malloc_size_np()
- From: Andrew Reilly
- Re: Proposed addition of malloc_size_np()
- Prev by Date: Re: Proposed addition of malloc_size_np()
- Next by Date: Re: Proposed addition of malloc_size_np()
- Previous by thread: Re: Proposed addition of malloc_size_np()
- Next by thread: Re: Proposed addition of malloc_size_np()
- Index(es):
Relevant Pages
- Re: Confusion between Stack and Data segment
... int main ... Does variable " j " get stored in the data segment as it
is ... Does variable " i " get stored in the stack segment or bss ... automatic
storage duration starts to live when the function defining ... (comp.unix.programmer) - Are VBOs the answer to my speed problem ?
... I'm developing an Interactive Earth program similar to Google Earth. ... The
inner loop just goes round and round until each latitude/longitude pair in the segment is drawn.
... Each time the outer loop goes round a glBeginis executed. ... int nSegment;
... (comp.graphics.api.opengl) - [patch 3/6] s390: dcss segments cleanup.
... Cleanup segment load/unload infrastructure. ... -static void inline dcss_mkname
... +dcss_diag_translate_rc (int vm_rc) { ... * Load a DCSS segment via the
diag 0x64. ... (Linux-Kernel) - [patch 3/6] s390: dcss segments.
... - Restore previous segment state if reload fails. ... +static inline int
... * this function modifies the shared state of a DCSS segment. ... * print appropriate
error message for segment_load/segment_info ... (Linux-Kernel) - Re: Confusion between Stack and Data segment
... int main ... Does variable " j " get stored in the data segment as it
is ... automatic storage duration starts to live when the function defining ...
(comp.unix.programmer)