From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: ** X-Spam-Status: No, score=2.7 required=5.0 tests=BAYES_00, FREEMAIL_FORGED_REPLYTO,HK_RANDOM_FROM,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,aa67018f272e5dda X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-03-29 01:53:36 PST Path: supernews.google.com!sn-xit-02!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: DPH Newsgroups: comp.lang.ada Subject: Re: Green Hills 64 Bit Float Problem on PowerPC 603 Date: Thu, 29 Mar 2001 04:53:35 -0500 Organization: Posted via Supernews, http://www.supernews.com Message-ID: <3AC3061F.584053EE@kg.hsanet.net> Reply-To: rally2xs@compuserve.com X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en,pdf MIME-Version: 1.0 References: <3AC264E3.742D050E@kg.hsanet.net> <3ac2e5ba@pull.gecm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: newsabuse@supernews.com Xref: supernews.google.com comp.lang.ada:6198 Date: 2001-03-29T04:53:35-05:00 List-Id: Martin Dowie wrote: > Just guessing, but has it choosen 424 bytes as this is "mod 8 = 0" long, > long word aligned? Not sure. I really gotta find out where it stuck those extra 4 bytes, tho, and what logic it used when it placed them wherever it did. If at the end of the message, then fine - it won't hurt how the tool picks up data from the file. If it stuck it in somewhere in the middle, then the tool will be finding wrong data after that... until I figure out how to predict the anomaly and compensate for it. > Isn't the simplest way to resolve this question just to insert a few known > values do some > maths and check the results? Well, its a real time system. Inserting anything isn't exactly the easiest thing to do. None of the code for it is mine - I'd have to get someone to make a special build, maybe init a long float to a certain value and then capture it. It'd involve a special lab run at a lab that's a matter of a half hour or so to bring on line, etc. No, the easiest thing would be for someone here with specific knowledge of how a Power PC chip on an MVME board treats long floats to gimmie a clue about it! Dave Head > DPH wrote in message > news:3AC264E3.742D050E@kg.hsanet.net... > [snip] > > Complicating the analysis is the fact that the message is 4 bytes longer > > than it should be. That is, representation specifications say it should > > be 420 bytes long, but it is 424 bytes long. No, I haven't been able to > > figure out where the extra 4 bytes are located.