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.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,7b60a2e8329f4e64
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
X-Received: by 10.181.13.205 with SMTP id fa13mr1719534wid.3.1358656058242;
        Sat, 19 Jan 2013 20:27:38 -0800 (PST)
Path: 
 i11ni8455wiw.0!nntp.google.com!feeder1.cambriumusenet.nl!feed.tweaknews.nl!194.109.133.86.MISMATCH!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!border4.nntp.ams.giganews.com!border2.nntp.ams.giganews.com!nntp.giganews.com!news.panservice.it!feeder.erje.net!eu.feeder.erje.net!news.ripco.com!news.glorb.com!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post02.iad.highwinds-media.com!news.flashnewsgroups.com-b7.4zTQh5tI3A!not-for-mail
From: Stephen Leake <stephen_leake@stephe-leake.org>
Newsgroups: comp.lang.ada
Subject: Re: GNAT 4.4.5 Record Bit_Order Endian issues
References: <20bda3de-b033-4b4e-8298-2ac47701b814@googlegroups.com>
Date: Tue, 15 Jan 2013 17:24:40 -0500
Message-ID: <85hamiulsn.fsf@stephe-leake.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (windows-nt)
Cancel-Lock: sha1:r8eQQkd6WeXmpS90He+sla1pU6M=
MIME-Version: 1.0
X-Complaints-To: abuse@flashnewsgroups.com
Organization: FlashNewsgroups.com
X-Trace: 9578a50f5d72be029e66132490
X-Received-Bytes: 1275
Content-Type: text/plain
Date: 2013-01-15T17:24:40-05:00
List-Id: <comp.lang.ada>

awdorrin <awdorrin@gmail.com> writes:

> I have a record with specification definition that starts, using big endian notation, with:
>
> for TRACK_RECORD_TYPE use
>  record
>   TRACK_ID at 0 range 0 .. 11;
>   TRACK_ID_CNT at 1 range 4 .. 9;
>    ...
>
>
> The meaning being that the first 12 bits hold a track id and the next
> 6 bits hold the Count value.

If you are allocating consecutive  bits, then do this:

for TRACK_RECORD_TYPE use
   record
     TRACK_ID     at 0 range  0 .. 11;
     TRACK_ID_CNT at 0 range 12 .. 17;
     ...


-- 
-- Stephe