× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: instruction pointers
  • From: "Steve Richter" <srichter@xxxxxxxxxxxxx>
  • Date: Thu, 7 Jun 2001 12:35:40 -0400

 
You cannot add to them or setip to a variable label name.
===> this is on purpose. You can only brabch to an existing static label.
 
Too bad. I wonder what ibm's purpose is?
Being able to variably chg the exec path of a pgm is a very useful debug and error recovery tool.
I can see limiting the ability to branch outside of the pgm, but not inside of it.
 
 
Does the powerpc risc have the ability to branch to code in another pgm?
===> yes, but the MI architecture does not support it directly.
(also a security risk)
 
What specifically would not work? I can think of the following:
 
"DCL EXCM" exception handling probably would not work.
 
And the linkage between the MI instruction table and the risc code would corrupted.
 
So, when you WrkJob and display the pgm stack, the system would probably flip out.
 
But, would the code be able to execute and then return to the branched from pgm and resume normal operations?
 
 
===> if you patch the program you can arrange to branch to
a parameter. This gives you the ability to execute RISC
instructions that are part of your data (and therefore are
under your control).
 
So you could execute risc code in a usrspc?
 
 
thank you,
Steve Richter
 

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.