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=unavailable autolearn_force=no version=3.4.4
X-Received: by 2002:a24:5907:: with SMTP id p7-v6mr488418itb.36.1525992660153;
        Thu, 10 May 2018 15:51:00 -0700 (PDT)
X-Received: by 2002:a9d:4712:: with SMTP id a18-v6mr154482otf.1.1525992660000;
 Thu, 10 May 2018 15:51:00 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.linkpendium.com!news.linkpendium.com!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!u74-v6no778951itb.0!news-out.google.com!f20-v6ni891itd.0!nntp.google.com!u74-v6no778946itb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 10 May 2018 15:50:59 -0700 (PDT)
In-Reply-To: <pd2hpg$egf$1@franka.jacob-sparre.dk>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=47.185.233.194;
 posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo
NNTP-Posting-Host: 47.185.233.194
References: <ec0145a4-9698-41f2-bc70-964dc1850e50@googlegroups.com>
 <ly4ljfgvim.fsf@pushface.org> <pd2hpg$egf$1@franka.jacob-sparre.dk>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <c3a4f872-7e24-4d66-a425-776a1aa063f5@googlegroups.com>
Subject: Re: AI12-0218:  What is the portable representation clause for
 processing IETF packets on little-endian machines?
From: "Dan'l Miller" <optikos@verizon.net>
Injection-Date: Thu, 10 May 2018 22:51:00 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: reader02.eternal-september.org comp.lang.ada:52226
Date: 2018-05-10T15:50:59-07:00
List-Id: <comp.lang.ada>

On Thursday, May 10, 2018 at 5:40:49 PM UTC-5, Randy Brukardt wrote:
> =E2=80=A6 If you just implement it in the front-end using code=20
> equivalent to unchecked_conversions, you're forcing all of the operations=
=20
> into memory

Wait, what is the actual extant-in-reality use-case for byte-swapping betwe=
en registers (within the same processor!) of (supposedly-)heterogenous endi=
anness?  (Not even the PDP-11's mixed endianness did that!)  Does any proce=
ssor exhibit such odd endianness within its own processor('s registers)?  M=
ethinks this is pure bicycle-shedding without any basis in reality.

> don't allow any hardware support to get used.

Hmmm, that one is somewhat more compelling if the processor has byte-swappi=
ng instructions.