* Record Rep specs, endian: big -> little, Storage_Unit: 8 -> 16
@ 1996-10-17 0:00 Vernon Brown
0 siblings, 0 replies; only message in thread
From: Vernon Brown @ 1996-10-17 0:00 UTC (permalink / raw)
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~1996-10-17 0:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1996-10-17 0:00 Record Rep specs, endian: big -> little, Storage_Unit: 8 -> 16 Vernon Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox