Path: csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch
Newsgroups: comp.arch
Subject: Re: endian history
Date: Fri, 02 Oct 2026 21:31:26 -0700
Organization: A noiseless patient Spider
Lines: 35
Message-ID: <86bj9bo15t.fsf@linuxsc.com>
References: <10uks4f$1dqo$1@gal.iecc.com> <118dl5f$37cfv$1@dont-email.me> <118e8kg$3f05h$1@dont-email.me> <868q4zuhz4.fsf@linuxsc.com> <118jitv$1cm6b$1@dont-email.me> <86ik42tcf4.fsf@linuxsc.com> <118uf6m$12tta$1@dont-email.me> <86ld8srnq9.fsf@linuxsc.com> <1790188863-5857@newsgrouper.org> <86cxu3sp11.fsf@linuxsc.com> <1790269240-5857@newsgrouper.org> <119hf66$3nmbu$1@dont-email.me> <86ld8hplkd.fsf@linuxsc.com> <2026Oct1.172040@mips.complang.tuwien.ac.at> <864if5pfby.fsf@linuxsc.com> <20261001192324.00004a9b@yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Date: Sat, 03 Oct 2026 04:31:29 +0000 (UTC)
Injection-Info: dont-email.me; logging-data="2834329"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18aJo7vw4PWLAsAe15LSnIbgBIUoiiTNO4="; posting-host="b0e28b4afc9fd8b2450f610d134fbfb4"
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:0SXTTqeegyz/NUS6xTSZ1GrMbHw= sha1:9wV8angET8iZ9z0DzfPumvb+d54= sha256:W4KUr56wvI8w9bv6TbNzuhEUTQZsKZwAivNS5oimkQs= sha1:lZ/ohINhJ5z14+sJn5/eGF4II08= sha256:STU9jJELnPQl/1ROvNCbCLBzz2TCs8N3CM2/1sRod0M=
Xref: csiph.com comp.arch:118414
Michael S writes:
> On Thu, 01 Oct 2026 09:15:29 -0700
> Tim Rentsch wrote:
>
>> anton@mips.complang.tuwien.ac.at (Anton Ertl) writes:
>>
>>> Tim Rentsch writes:
>>>
>>>>> With wrapping signed arithmetic, all of the semantics of
>>>>> unsigned arithmetic is the same, except for right shift and
>>>>> division operations.
>>>>
>>>> Also left shift
>>>
>>> No. The funny thing is that AMD64 has both SHL and SAL
>>> mnemonics, but they encode the same opcodes. E.g.:
>>>
>>> D3 /4 SAL r/m32, CL
>>> D3 /4 SHL r/m32, CL
>>
>> That may be true for AMD64. It is not true for other
>> two's complement architectures.
>
> I would think that it is true on all twoc architectures that don't
> trap on signed integer overflow.
Did you embark on any research to reach this characterization, or
is it just speculation?
> Also it is a defenition guaranteed on all supported targets by gcc.
I don't know what that has to do with the question here, which is
more about machine architectures and/or Java, and at first blush
has nothing to do with gcc.