Actually, the POPS is full of "may or may not". I think the reason for th
at is that it gives the
designers of specific machines latitude to do things differently, not bei
ng constrained too much by
the architecture. This in turn should lower the cost of the machine.
The reason the "may or may n
On Fri, Oct 8, 2010 at 7:33 PM, Bill Holder wrote:
> I believe the reason for allowing some leeway has to do
> with hardware design concepts for things like pipelining,
> "reach ahead" and "out-of-order execution" - with the
> hardware in essence "speculatively" performing certain
> operations ah
I guess I can say I "have a clue", in that I can offer my
personal interpretation, as an operating system developer
and designer, though I cannot claim to officially speak
for the architects or IBM (so take this all with the
prerequisite grain of salt):
In my opinion, that paragraph is in th
PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Seinfeld's Contribution to the The Principles of Operation
There is only one place in z Architecture Principles of Operation where the
word substantially is used. Even more surprising than its use is the fact
that it appears immediately before the
There is only one place in z Architecture Principles of Operation where the
word substantially is used. Even more surprising than its use is the fact
that it appears immediately before the word "accurate". My interest in the
reference bit, though passing, is sincere since I would like to hang my h
