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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,438f2856ab36a026 X-Google-Attributes: gid103376,public From: "Corey Ashford" Subject: Re: 83/95 issue, bad code or compiler bug Date: 1998/11/19 Message-ID: <732via$auf$1@usenet.rational.com>#1/1 X-Deja-AN: 413769287 References: <732veo$aga$1@usenet.rational.com> X-Priority: 3 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 Organization: Rational Software X-MSMail-Priority: Normal Newsgroups: comp.lang.ada Date: 1998-11-19T00:00:00+00:00 List-Id: Corey Ashford wrote in message news:732veo$aga$1@usenet.rational.com... > >Tucker Taft wrote in message news:F2ozE4.FLJ.0.-s@inmet.camb.inmet.com... >>Jeff Creem (jeffrey.m.creem@lmco.com) wrote: >[snip] >>: with the old compiler the My_Subtype was still using all 32 bits so >>: that if we had a record with My_Field := 1 and Other_Field := 2 and >>: we looked at the bytes in memory associated with this record we would see >> >> >>: 00 00 00 01 >>: 00 00 00 02 >> >>: But with this new compiler (happens to be ada 95) I get >> >>: 01 00 00 00 >>: 00 00 00 02 >[snip] > >>This is a bug. You should ask your compiler vendor whether a fix >>is available. The repclause clearly indicates that My_Field should occupy >>4 bytes, and that means it should not just be using the high 8 bits of >>the word. > > >If this is a little-endian machine, then I would think that the >latter representation shown above is correct and expected. > >- Corey oops... never mind. It's obviously not a little-endian machine because of the representation of the integer 2. Sorry for the confusion. - Corey