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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham 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-31 13:30:05 PST Path: supernews.google.com!sn-xit-03!supernews.com!logbridge.uoregon.edu!newsfeed.skycache.com!Cidera!cyclone.tampabay.rr.com!news-post.tampabay.rr.com!typhoon.tampabay.rr.com.POSTED!not-for-mail From: "Gleason" Newsgroups: comp.lang.ada References: <3AC264E3.742D050E@kg.hsanet.net> <3ac2e5ba@pull.gecm.com> <3AC3061F.584053EE@kg.hsanet.net> Subject: Re: Green Hills 64 Bit Float Problem on PowerPC 603 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Message-ID: Date: Sat, 31 Mar 2001 21:29:14 GMT NNTP-Posting-Host: 65.32.128.221 X-Complaints-To: abuse@rr.com X-Trace: typhoon.tampabay.rr.com 986074154 65.32.128.221 (Sat, 31 Mar 2001 16:29:14 EST) NNTP-Posting-Date: Sat, 31 Mar 2001 16:29:14 EST Organization: RoadRunner - TampaBay Xref: supernews.google.com comp.lang.ada:6299 Date: 2001-03-31T21:29:14+00:00 List-Id: DPH wrote: > 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. > Why not read the assembly code? With the Green Hills tools there are two ways to get an interspersed source and assembly view. One is with the debugger, the other is through the compiler's assembly listing. By using your existing code or designing a simple test case that accesses every field of the record, you should be able to easily read the assembly code and figure out how the record is layed out. Hope this helps. Jim Gleason