× 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:Using RISC as development, sending to CISC. Any problems forseen ?
  • From: "Ilena E. Ayala" <Ilena@xxxxxxxxxxxxxx>
  • Date: Tue, 30 Jun 1998 15:54:41 -0400

>We did some testing today and it seems if you compile an object on a
>RISC box as V3R2, and run it, it does not get converted to RISC (or
>already is RISC).  We can send it to a CISC box and it seems to run
>without problems.

Right, the V3R2 is the target release, but it will still be in "RISC" form
until it is converted
back on the CISC box.  

What you need to look out for is how many releases you need to jump back
for the CISC boxes.
The earliest release you can specify as a target release when compiling
under V4R2 is V3R7 or V3R2.
V3R6 is not supported as a target release from V4R2M0. V4R1 or earlier
releases can compile with a target release of V3R1.

I believe the rule of thumb is the current release you are on and the two
prior releases.  Just keep in mind that V3R6 is considered to be an earlier
release than V3R2, despite the names.

-Ilena Ayala
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.