comp.lang.ada
 help / color / mirror / Atom feed
From: Dmitry A. Kazakov <mailbox@dmitry-kazakov.de>
Subject: Re: Interoperability: differing storage units and/or endianess
Date: Fri, 20 Feb 2004 14:55:26 +0100
Date: 2004-02-20T14:55:26+01:00	[thread overview]
Message-ID: <u24c309om3sbt37imujp1lpnqarucdgric@4ax.com> (raw)
In-Reply-To: c14p0a$40s$1@online.de

On Fri, 20 Feb 2004 11:54:02 +0100, Michael Paus
<pausnospam@nospamib-paus.com> wrote:

>Stephen Leake wrote:
>
>> Michael Paus <pausnospam@nospamib-paus.com> writes:
>> 
>>>Bibb Latting wrote:
>>>
>>>>Hi, I am working on a distributed application where the processors
>>>>have differing storage unit sizes and/or endianess.  My problem is how
>>>>to handle the specification of memory contents and the delivery of
>>>>data to applications with minimal variation between implementations.
>>>>I'd like to know what solutions have worked well for others.
>>>
>>>And I'd like to know which currently used processors have a storage
>>>unit size other than 8.
>> 
>> Many DSPs use 16 bit words.
>
>Interesting! I haven't worked with DSPs for a very long time. Could
>you tell me how they map, e.g. a character. Does it always have
>16 bits or don't they have the type character at all anymore?

Do you mean Ada or C? In Ada the type Character need not to be
aliased. As for C, I remotely remember a DSP compiler that used 32
bits per char. It is allowed in ANSI C, AFAIK.

--
Regards,
Dmitry A. Kazakov
www.dmitry-kazakov.de



  reply	other threads:[~2004-02-20 13:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19 12:29 Interoperability: differing storage units and/or endianess Bibb Latting
2004-02-19 17:23 ` Jeffrey Carter
2004-02-20 13:52   ` Martin Dowie
2004-02-20  7:41 ` Michael Paus
2004-02-20  8:56   ` Stephen Leake
2004-02-20 10:54     ` Michael Paus
2004-02-20 13:55       ` Dmitry A. Kazakov [this message]
2004-02-20 12:43   ` Petter Fryklund
2004-02-20 20:24     ` Randy Brukardt
2004-02-21  5:34 ` Steve
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox