According to Thomas Koenig <tkoenig@netcologne.de>:
DEC F77 used a stack and allowed recursion if you were careful
whereas IBM F77 did not (it used static allocation for all local
variables so recursion stomped on their values).
OS/360 calling conventions is one thing they got wrong.
My PDP-11 Unix F77 used the C compiler's back end, so recursion
worked fine. I made variables automatic (stack) unless you used
a SAVE statement, which made sense in the PDP-11's limited address space.
It is quite possible to do recursion with the OS/360 calling convention. Their PL/I compilers did it and I believe the various ALGOL compilers,
which had to support recursion, also used the standard calling sequence.
On 20/10/2026 04:50, John Levine wrote:
According to Thomas Koenig <tkoenig@netcologne.de>:
DEC F77 used a stack and allowed recursion if you were careful
whereas IBM F77 did not (it used static allocation for all local
variables so recursion stomped on their values).
OS/360 calling conventions is one thing they got wrong.
My PDP-11 Unix F77 used the C compiler's back end, so recursion
worked fine. I made variables automatic (stack) unless you used
a SAVE statement, which made sense in the PDP-11's limited address space.
It is quite possible to do recursion with the OS/360 calling convention.
Their PL/I compilers did it and I believe the various ALGOL compilers,
which had to support recursion, also used the standard calling sequence.
Brian Wichmann (of Whetstone Benchmark fame) gives the following
figures for Ackermann's function, a stress test for recursion.
ALGOL-a60,-aby-aarchitecture,-amean orders/call,-a*-a=-aestimate
Bill Findlay <findlaybill@blueyonder.co.uk> schrieb:
On 20/10/2026 04:50, John Levine wrote:
According to Thomas Koenig <tkoenig@netcologne.de>:
DEC F77 used a stack and allowed recursion if you were careful
whereas IBM F77 did not (it used static allocation for all local
variables so recursion stomped on their values).
OS/360 calling conventions is one thing they got wrong.
My PDP-11 Unix F77 used the C compiler's back end, so recursion
worked fine. I made variables automatic (stack) unless you used
a SAVE statement, which made sense in the PDP-11's limited address space. >>>
It is quite possible to do recursion with the OS/360 calling convention. >>> Their PL/I compilers did it and I believe the various ALGOL compilers,
which had to support recursion, also used the standard calling sequence. >>>
Brian Wichmann (of Whetstone Benchmark fame) gives the following
figures for Ackermann's function, a stress test for recursion.
ALGOL-a60,-aby-aarchitecture,-amean orders/call,-a*-a=-aestimate
I understand "ALGOL 60", but not the rest.
What orders?
Archaic terminology for "instructions".
The early Burroughs systems (Electrodata 220, Burroughs 300,
B3500) all called them 'orders' rather than instructions.
In fact, the processor test suite for the B3500 and successors
was called all-orders.
System/3?0, by language and compiler
ALGOL 60, Edinburgh Uni. /360 21.0
PL/I OPT v1.2.1, IBM /360 61 *
ALGOL W, Stanford Uni. /360 74 *
ALGOL 60, Delft Uni. /360 142 *
PL/I F level v5.4, IBM /360 212 *
ALGOL 60, IBM F level /360 820 *
ALGOL F seems to have been written with the
attitude, you want an Algol compiler? Here's an Algol compiler, suck it up.
On Wed, 21 Oct 2026 03:28:44 -0000 (UTC), John Levine
<johnl@taugh.com> wrote:
ALGOL F seems to have been written with the
attitude, you want an Algol compiler? Here's an Algol compiler, suck it up.
Yes. Unlike ALGOL W you had to indicate the keywords by putting quote
marks around them - although some halfway-serious ALGOL 60 compilers
for other architectures also did this.
In article <6ad8c6dc.5749031@news.eternal-september.org>,
John Savard <quadibloc@invalid.com> wrote:
On Wed, 21 Oct 2026 03:28:44 -0000 (UTC), John Levine
<johnl@taugh.com> wrote:
ALGOL F seems to have been written with theYes. Unlike ALGOL W you had to indicate the keywords by putting quote
attitude, you want an Algol compiler? Here's an Algol compiler, suck it up. >>
marks around them - although some halfway-serious ALGOL 60 compilers
for other architectures also did this.
I don't believe that is true. The descriptions of AGOL W that
are publicly available do not indicate that quote marks were
required around keywords; I have only seen that on Algol 60
code.
On Tue, 20 Oct 2026 20:44:45 GMT, scott@slp53.sl.home (Scott Lurndal)The US-centrism is strong in these replies.
wrote:
Archaic terminology for "instructions".
The early Burroughs systems (Electrodata 220, Burroughs 300,
B3500) all called them 'orders' rather than instructions.
In fact, the processor test suite for the B3500 and successors
was called all-orders.
At one time, the _instruction set_ of a computer was instead referred
to as its "order code".
On 20/10/2026 23:49, John Savard wrote:
On Tue, 20 Oct 2026 20:44:45 GMT, scott@slp53.sl.home (Scott Lurndal)The US-centrism is strong in these replies.
wrote:
Archaic terminology for "instructions".
The early Burroughs systems (Electrodata 220, Burroughs 300,
B3500) all called them 'orders' rather than instructions.
In fact, the processor test suite for the B3500 and successors
was called all-orders.
At one time, the _instruction set_ of a computer was instead referred
to as its "order code".
Sigh. (I have taken that over from Nick.)
Bill Findlay <findlaybill@blueyonder.co.uk> writes:
On 20/10/2026 23:49, John Savard wrote:
On Tue, 20 Oct 2026 20:44:45 GMT, scott@slp53.sl.home (Scott Lurndal)The US-centrism is strong in these replies.
wrote:
Archaic terminology for "instructions".
The early Burroughs systems (Electrodata 220, Burroughs 300,
B3500) all called them 'orders' rather than instructions.
In fact, the processor test suite for the B3500 and successors
was called all-orders.
At one time, the _instruction set_ of a computer was instead referred
to as its "order code".
Sigh. (I have taken that over from Nick.)
Perhaps you might, then, enlighten your yank
cousins by providing the UK viewpoint.
On 22/10/2026 01:02, Scott Lurndal wrote:
Bill Findlay <findlaybill@blueyonder.co.uk> writes:
On 20/10/2026 23:49, John Savard wrote:
On Tue, 20 Oct 2026 20:44:45 GMT, scott@slp53.sl.home (Scott Lurndal)The US-centrism is strong in these replies.
wrote:
Archaic terminology for "instructions".
The early Burroughs systems (Electrodata 220, Burroughs 300,
B3500) all called them 'orders' rather than instructions.
In fact, the processor test suite for the B3500 and successors
was called all-orders.
At one time, the _instruction set_ of a computer was instead referred
to as its "order code".
Sigh. (I have taken that over from Nick.)
Perhaps you might, then, enlighten your yank
cousins by providing the UK viewpoint.
I do, from time to time, and am generally ignored.
Bill Findlay <findlaybill@blueyonder.co.uk> posted:
On 22/10/2026 01:02, Scott Lurndal wrote:
Bill Findlay <findlaybill@blueyonder.co.uk> writes:
On 20/10/2026 23:49, John Savard wrote:
On Tue, 20 Oct 2026 20:44:45 GMT, scott@slp53.sl.home (Scott Lurndal) >>>>> wrote:The US-centrism is strong in these replies.
Archaic terminology for "instructions".
The early Burroughs systems (Electrodata 220, Burroughs 300,
B3500) all called them 'orders' rather than instructions.
In fact, the processor test suite for the B3500 and successors
was called all-orders.
At one time, the _instruction set_ of a computer was instead referred >>>>> to as its "order code".
Sigh. (I have taken that over from Nick.)
Perhaps you might, then, enlighten your yank
cousins by providing the UK viewpoint.
I do, from time to time, and am generally ignored.
That is ALMOST the Casandra Syndrome:: "always tell the truth,
nobody ever believes"
On 23/10/2026 01:27, MitchAlsup wrote:
Bill Findlay <findlaybill@blueyonder.co.uk> posted:
On 22/10/2026 01:02, Scott Lurndal wrote:
Bill Findlay <findlaybill@blueyonder.co.uk> writes:
On 20/10/2026 23:49, John Savard wrote:
On Tue, 20 Oct 2026 20:44:45 GMT, scott@slp53.sl.home (ScottThe US-centrism is strong in these replies.
Lurndal) wrote:
Archaic terminology for "instructions".
The early Burroughs systems (Electrodata 220, Burroughs 300,
B3500) all called them 'orders' rather than instructions.
In fact, the processor test suite for the B3500 and successors
was called all-orders.
At one time, the _instruction set_ of a computer was instead
referred to as its "order code".
Sigh. (I have taken that over from Nick.)
Perhaps you might, then, enlighten your yank
cousins by providing the UK viewpoint.
I do, from time to time, and am generally ignored.
That is ALMOST the Casandra Syndrome:: "always tell the truth,
nobody ever believes"
Quite so.
However, it all goes into an archive and will continue
being available to those with curiosity and broad minds.
On 23/10/2026 01:27, MitchAlsup wrote:
Bill Findlay <findlaybill@blueyonder.co.uk> posted:
On 22/10/2026 01:02, Scott Lurndal wrote:
Bill Findlay <findlaybill@blueyonder.co.uk> writes:
On 20/10/2026 23:49, John Savard wrote:
On Tue, 20 Oct 2026 20:44:45 GMT, scott@slp53.sl.home (Scott Lurndal) >>>>>> wrote:The US-centrism is strong in these replies.
Archaic terminology for "instructions".
The early Burroughs systems (Electrodata 220, Burroughs 300,
B3500) all called them 'orders' rather than instructions.
In fact, the processor test suite for the B3500 and successors
was called all-orders.
At one time, the _instruction set_ of a computer was instead referred >>>>>> to as its "order code".
Sigh. (I have taken that over from Nick.)
Perhaps you might, then, enlighten your yank
cousins by providing the UK viewpoint.
I do, from time to time, and am generally ignored.
That is ALMOST the Casandra Syndrome:: "always tell the truth,
nobody ever believes"
Quite so.
However, it all goes into an archive and will continue
being available to those with curiosity and broad minds.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:48:53 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,582 |