Re: modifying constants in Fortran and elsewhere

gah4 <gah4@u.washington.edu>
Sun, 16 Jul 2023 19:17:22 -0700

          From comp.compilers

Related articles
modifying constants in Fortran and elsewhere gah4@u.washington.edu (gah4) (2023-07-10)
Re: modifying constants in Fortran and elsewhere tkoenig@netcologne.de (Thomas Koenig) (2023-07-15)
Re: modifying constants in Fortran and elsewhere DrDiettrich1@netscape.net (Hans-Peter Diettrich) (2023-07-16)
Re: modifying constants in Fortran and elsewhere tkoenig@netcologne.de (Thomas Koenig) (2023-07-16)
Re: modifying constants in Fortran and elsewhere gah4@u.washington.edu (gah4) (2023-07-16)
Re: modifying constants in Fortran and elsewhere gah4@u.washington.edu (gah4) (2023-07-16)
Re: modifying constants in Fortran and elsewhere david.brown@hesbynett.no (David Brown) (2023-07-17)
Re: modifying constants in Fortran and elsewhere gah4@u.washington.edu (gah4) (2023-07-17)
| List of all articles for this month |
From: gah4 <gah4@u.washington.edu>
Newsgroups: comp.compilers
Date: Sun, 16 Jul 2023 19:17:22 -0700
Organization: Compilers Central
References: 23-07-003 23-07-006 23-07-008
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="80711"; mail-complaints-to="abuse@iecc.com"
Keywords: architecture, history
Posted-Date: 17 Jul 2023 12:18:21 EDT
In-Reply-To: 23-07-008

> Our esteemed moderator wrote:


(snip)


> I was there, I actually used this stuff. Re abuse of the upper byte, as the size of
> OS/360 exploded way past what they expected, programmers were under pressure to make
> every bit and byte count, hence overloading the high byte. -John]


Funny how history repeats itself. (As the saying goes.)


In this case, it was only the one bit, and with 31 bit addressing, it could
still be used. Though the compile doesn't actually check for the end of
the argument list.


Much of OS/360, at all levels, uses the high byte of addresses.
Most important, in the DCB used for much I/O. With the transition to 31 bit
and 64 bit addressing, much of the old control blocks are still there.
The DCB is in user address space, and so not easily replaced.


Much of that is still true in OS/390 and z/OS, the 31 bit and 64 bit OS.


And then years later, Apple creates the Macintosh, and (original) MacOS.
And with 24 bit addressing on the 68000, uses the high byte of addresses.


Then with the 68020, there were programs known to be 32 bit clean,
and those that were not.


I suspect that all the hard learned lessons from the mainframe days were
relearned in the microcomputer days.


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.