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,ab5f30ff85561544,start X-Google-Attributes: gid103376,public From: Vernon Brown Subject: Record Rep specs, endian: big -> little, Storage_Unit: 8 -> 16 Date: 1996/10/17 Message-ID: <32665D2C.20431CA7@az.honeywell.com>#1/1 X-Deja-AN: 190222241 content-type: text/plain; charset=us-ascii organization: Honeywell CAS mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 3.0 (X11; I; SunOS 4.1.4 sun4m) Date: 1996-10-17T00:00:00+00:00 List-Id: I am porting a large avionics application from a big-endian processor, AMD-29050, to a little endian processor, Intel-P5. The compiler for the 29050 has a System.Storage_Unit of 8 bits, but the compiler I'm using for the port to Intel has a Storage_Unit of 16 bits. The application has many record rep specs that map onto external byte streams of data. Is there any chance that I can write rep specs that will work in both environments, and if not, what rules could I apply when modifying the rep specs? An example record rep spec is: for Leg_Fault_Record_Type use record Time_First at 0 range 0 .. 15; Flight_Phase at 2 range 0 .. 7; System_Mode at 3 range 0 .. 7; Test_ID at 4 range 0 .. 7; Fault_ID at 5 range 0 .. 15; Fault_Type at 7 range 0 .. 7; Intermittent_Count at 8 range 0 .. 7; Time_Recent at 9 range 0 .. 15; Isolation_Data at 11 range 0 .. 127; Detail_Data_Indicator at 27 range 0 .. 7; Reserved at 28 range 0 .. 31; end record; Please email me as well as posting to the news group, as my news reader sometimes gets behind by 3 or 4 days. -- Vernon Brown X6-3057 email: brownv@AZ.Honeywell.com