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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,bb163c965c676b88 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Received: by 10.66.72.73 with SMTP id b9mr2142589pav.9.1348454690391; Sun, 23 Sep 2012 19:44:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.232.230 with SMTP id tr6mr2449867pbc.16.1348454690376; Sun, 23 Sep 2012 19:44:50 -0700 (PDT) Path: t10ni7124914pbh.0!nntp.google.com!4no8885731pbn.1!postnews.google.com!k3g2000pbr.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sun, 23 Sep 2012 19:44:50 -0700 (PDT) Complaints-To: groups-abuse@google.com Injection-Info: k3g2000pbr.googlegroups.com; posting-host=123.2.70.40; posting-account=S_MdrwoAAAD7T2pxG2e393dk6y0tc0Le NNTP-Posting-Host: 123.2.70.40 References: <17h1nrxowrnce$.1k4efgoidl6gc.dlg@40tude.net> User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20100101 Firefox/13.0.1,gzip(gfe) Message-ID: Subject: Re: Endianness and Record Specification From: Robin Vowels Injection-Date: Mon, 24 Sep 2012 02:44:50 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: 2012-09-23T19:44:50-07:00 List-Id: On Sep 22, 7:59=A0pm, "Dmitry A. Kazakov" wrote: > On Sat, 22 Sep 2012 02:32:17 -0700 (PDT), Robin Vowels wrote: > > This won't help your problem, but > > PL/I bit strings are stored in correct order regardless > > of big-endian or little-endian machine on which the program runs. > > The memory image is identical for both machine types. > > This does not make any sense. > > 1. Anything a language stores it does in the correct order, unless the > compiler in broken. Just per definition, the correct order is the order > used by the language. I pointed out that in PL/I the order in which the bits are stored is the same regardless of endian-ness. Endian-ness came many years after the introduction of PL/I. It shouldn't be an issue with Ada either. > 2. As for logical order of bits, that depends exclusively on the hardware= . > As an example consider an A/D converter card which maps its registers ont= o > certain physical addresses of the host machine. The compiler has no > whatsoever influence on the bit, byte, word etc orders of the register as > perceived by the host machine hardware. That isn't relevant in determining the endian-ness. An A-D converter isn't the processor, it's an attachment.