Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!news.misty.com!news.iecc.com!.POSTED!nerds-end From: glen herrmannsfeldt Newsgroups: comp.compilers Subject: Re: Question about inter-thread stack references Date: Sat, 17 Jan 2015 18:46:17 +0000 (UTC) Organization: Aioe.org NNTP Server Lines: 25 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <15-01-026@comp.compilers> References: <15-01-015@comp.compilers> <15-01-024@comp.compilers> NNTP-Posting-Host: news.iecc.com X-Trace: miucha.iecc.com 1421524358 77774 2001:470:1f07:1126:0:676f:7373:6970 (17 Jan 2015 19:52:38 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Sat, 17 Jan 2015 19:52:38 +0000 (UTC) Keywords: architecture, history, comment Posted-Date: 17 Jan 2015 14:52:38 EST X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:1483 Louis Krupp wrote: > On Thu, 15 Jan 2015 23:54:57 -0800, Ivan Godard (snip) >>Is anyone aware of language/thread package/hardware rules about required >>semantics for such usage? Is it explicitly permitted, explicitly banned, >>stated to be implementation defined, stated to be undefined, or simply >>not mentioned? > This sounds a bit like what was once known as Burroughs Large Systems > (then Unisys A-Series and now Clearpath or something) architecture. It > had processes, not threads, but processes can be related and can share > data. Every process has a stack, one stack can have a reference into > another stack, and unfortunately, that's about all I can remember at > the moment. Is this the one that depends on the compiler for its security? That is, there is no memory protection, but the compiler will only compile programs that can't access things that they are not supposed to. Only programs supplied by the system, or compiled by compilers supplied by the system, are allowed to run. (No downloading apps!) -- glen [Downloading? This was the 1960s. The security issue was about making sure that backups kept the security info intact, and you couldn't install a bad program by loading it from a fake backup tape. -John]