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-7-bit Received: by 10.66.81.170 with SMTP id b10mr3778263pay.31.1351026513460; Tue, 23 Oct 2012 14:08:33 -0700 (PDT) Received: by 10.68.229.231 with SMTP id st7mr4261356pbc.2.1351026513443; Tue, 23 Oct 2012 14:08:33 -0700 (PDT) Path: s9ni21683pbb.0!nntp.google.com!kt20no8491831pbb.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 23 Oct 2012 14:08:33 -0700 (PDT) In-Reply-To: <85e4a577-9219-4fbe-a2a1-1c1f1459792f@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=192.35.35.34; posting-account=YkFdLgoAAADpWnfCBA6ZXMWTz2zHNd0j NNTP-Posting-Host: 192.35.35.34 References: <85e4a577-9219-4fbe-a2a1-1c1f1459792f@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <758371db-86aa-41c0-8242-de10f1f2df43@googlegroups.com> Subject: Re: Endianness and Record Specification From: awdorrin Injection-Date: Tue, 23 Oct 2012 21:08:33 +0000 Content-Type: text/plain; charset=ISO-8859-1 Date: 2012-10-23T14:08:33-07:00 List-Id: On Saturday, September 22, 2012 3:43:54 AM UTC-4, Quentin Ochem wrote: > Side note on this topic, there's been a recent enhancement to GNAT to specify endianness as representation clauses: > > > > http://www.adacore.com/developers/development-log/NF-71-L207-008-gnat/ > > http://docs.adacore.com/gnat-unw-docs/html/gnat_rm_3.html#SEC181 > > > Will do the thing that you expect automatically ;-) I finally have had a chance to get back into this code (been side-tracked on another part of this migration effort. What version of GNAT/GCC support this new Scalar_Storage_Order functionality? Sounds like it could save me a lot of effort if I can simply define records as 'big endian format' and let the compiler generate all the byte swapping code for me. Thanks