|
If we write our own MI compiler, all scalars could be unlimited in size. Which is the way it should be. -Steve -----Original Message----- From: Hall, Philip <phall@spss.com> To: MI400@midrange.com <MI400@midrange.com> Date: Wednesday, July 04, 2001 8:42 PM Subject: RE: LONG, LONG math - aka 64bit math.... >In answer to your original question about when they came in OS/400, the C++ >support brought them in to play. We, as end users, got 'legal' access them >using VisualAge C++ for OS/400. > >-----Original Message----- >From: Don >Sent: Wed 7/4/2001 10:53 AM >To: MI400@midrange.com >Cc: >Subject: Re: LONG, LONG math - aka 64bit math.... > > > > > >Agreed that this is the MI list and the concern arose from a crypto >routine written in C and ported to the 400...but the question still stands >and also, it would be interesting as to how far down this implementation >actually went in the MI vs simulating 64 bit math with 32bit op codes..:) > >Thanks Leif.... > > >DOn > > > > >On Wed, 4 Jul 2001, Leif Svalgaard wrote: > >> From: Don <dr2@cssas400.com> >> > Dumb question: >> > >> > I told that in effect we didn't have 64bit math ops on this machine >until >> > v4r5/v5r1. This is to say that "long long" variables didn't exist until > >> > they finally wokeup and got serious about terabyte space and gave us >64bit >> > math.... >> > >> > Can anyone confirm this for me? >> >> dumb answer: >> MI only had BIN(2) and BIN(4) (i.e. 16-bit and 32-bit) binary variables >> at least through v4r5; don't know about v5R1, but I doubt it. >> Packed and zoned variables go to 31 digits (much beyond 64-bit). >> Float has always had FLT(4) (32-bit) and FLT(8) (64-bit), but >> since floats are IEEE standard, that's no news. >> Other languages may vary. >> But this is the MI list, right? >> >> >> +--- >> | This is the MI Programmers Mailing List! >> | To submit a new message, send your mail to MI400@midrange.com. >> | To subscribe to this list send email to MI400-SUB@midrange.com. >> | To unsubscribe from this list send email to MI400-UNSUB@midrange.com. >> | Questions should be directed to the list owner/operator: >dr2@cssas400.com >> +--- >> > >+--- >| This is the MI Programmers Mailing List! >| To submit a new message, send your mail to MI400@midrange.com. >| To subscribe to this list send email to MI400-SUB@midrange.com. >| To unsubscribe from this list send email to MI400-UNSUB@midrange.com. >| Questions should be directed to the list owner/operator: dr2@cssas400.com >+--- > > > +--- | This is the MI Programmers Mailing List! | To submit a new message, send your mail to MI400@midrange.com. | To subscribe to this list send email to MI400-SUB@midrange.com. | To unsubscribe from this list send email to MI400-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: dr2@cssas400.com +---
As an Amazon Associate we earn from qualifying purchases.
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.