Re: IEANTRT troubles

Article View: bit.listserv.asm370

Article #379

Back to bit.listserv.asm370 Previous Next

#379

From: glen herrmannsfeldt
Date: Tue, 20 Sep 2005 20:10

22 lines
2775 bytes

Gary Weinhold <weinhold@dkl.com> wrote:

> One of our developers had the concept of "mostly reentrant", which lead
> to an interesting discussion of the theoretical (if not
> implementational) difference between reentrancy and refreshability.  He
> used the term paene-reentrant to define a program that modified itself,
> but did it in a way that the modification was exactly the same no matter
> which execution instance modified it.  (It was a pointer to a common
> memory block, set by the first execution instance to compare and swap it
> from zeros to an address).

There have been examples, such as initializing a table of
constants and setting a flag to indicate that it has been done.
It might even be done with self modifying code.  Reentrant,
but not read only.

As far as I understand refreshability it might have been
used to allow the system to reread a module if a parity error
occurred where it was loaded in memory.  I don't know if
it still means that, though.

-- glen

Technical Details

Message-ID: <43306CD0.mailxDD411LDQ1@seniti.ugcs.caltech.edu>

Path:

arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news4.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!nx02.iad01.newshosting.com!newshosting.com!newsfeed.news2me.com!newsfeed2.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!sn-xit-02!sn-xit-10!sn-xit-06!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!ugcs.caltech.edu!gah

References:

<!~ !UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAYIraNz2UkUSflTk98hv0JO KAAAAQAAAAynd20rfrqUaKY4oRxbFXlgEAAAAA@lerctr.org> <43306305.39B581@dkl.com>

Show Full Headers

Complete Article Headers

X-Google-Thread: fcdcb,72645f6509f487f6
X-Google-Attributes: gidfcdcb,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news4.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!nx02.iad01.newshosting.com!newshosting.com!newsfeed.news2me.com!newsfeed2.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!sn-xit-02!sn-xit-10!sn-xit-06!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!ugcs.caltech.edu!gah
From: glen herrmannsfeldt <gah@ugcs.caltech.edu>
Newsgroups: bit.listserv.asm370
Subject: Re: IEANTRT troubles
Date: Tue, 20 Sep 2005 13:10:56 -0700
Organization: SAS Inc.
Lines: 22
Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
Message-ID: <43306CD0.mailxDD411LDQ1@seniti.ugcs.caltech.edu>
References: <!~
            !UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAYIraNz2UkUSflTk98hv0JO
            KAAAAQAAAAynd20rfrqUaKY4oRxbFXlgEAAAAA@lerctr.org>
            <43306305.39B581@dkl.com>
NNTP-Posting-Host: mozart.unx.sas.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: foggy.unx.sas.com 1127247401 3897 10.19.150.41 (20 Sep 2005 20:16:41 GMT)
X-Complaints-To: usenet@unx.sas.com
NNTP-Posting-Date: Tue, 20 Sep 2005 20:16:41 +0000 (UTC)
Comments: Gated by NETNEWS@VM.SAS.COM
Return-Path: <owner-assembler-list@LISTSERV.UGA.EDU>
User-Agent: nail 9.30 2/20/02
Approved-By: glen herrmannsfeldt <gah@UGCS.CALTECH.EDU>
In-Reply-To: <43306305.39B581@dkl.com>
Return-Path: owner-assembler-list@LISTSERV.UGA.EDU
X-OriginalArrivalTime: 20 Sep 2005 20:16:36.0378 (UTC)
                       FILETIME=[339857A0:01C5BE20]
Originator: daemon@mozart.unx.sas.com

Reply to Parent Message