Re: Semiprivileged instructions, part 1 (3)

2011-12-31 Thread Shmuel Metz (Seymour J.)
In cakxahqw_nnqu8pqfsy+fqowj0jtqhistds+pbw20sryo3he...@mail.gmail.com, on 12/30/2011 at 01:20 PM, Chris Craddock crashlu...@gmail.com said: Additional *SOFTWARE* architectural conditions may have to be satisfied in order for the instruction to complete, ITYM that additional software

Re: Semiprivileged instructions, part 1 (3)

2011-12-30 Thread Peter Relson
I have noted a couple of omissions in the PoPs that I will submit a Readers Comment for I didn't notice that any of the things you mentioned regarding the PoOp are necessarily omissions or things to be corrected (but I might have missed it). You questioned the list of semiprivileged

Re: Semiprivileged instructions, part 1 (3)

2011-12-30 Thread Steve Comstock
On 12/30/2011 5:52 AM, Peter Relson wrote: I have noted a couple of omissions in the PoPs that I will submit a Readers Comment for I didn't notice that any of the things you mentioned regarding the PoOp are necessarily omissions or things to be corrected (but I might have missed it). You

Re: Semiprivileged instructions, part 1 (3)

2011-12-30 Thread Chris Craddock
Steve, Peter is (of course) right. You're struggling with cases where most people generally miss the distinction between the hardware architecture and the software architecture implemented by any given control program. The hardware knows nothing at all about what you would think of as

Re: Semiprivileged instructions, part 1 (3)

2011-12-30 Thread Shmuel Metz (Seymour J.)
In 4efdc456.2050...@trainersfriend.com, on 12/30/2011 at 07:01 AM, Steve Comstock st...@trainersfriend.com said: the consistency is not what I, personally, would like. I don't see the inconsistency in what you mentioned. I agree that the definitions should precede the use, or, at the least, a