From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 19891 invoked from network); 18 Jan 2021 05:50:51 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 18 Jan 2021 05:50:51 -0000 Received: from mimir.eigenstate.org ([206.124.132.107]) by 1ess; Mon Jan 18 00:20:51 -0500 2021 Received: from abbatoir.fios-router.home (pool-74-101-2-6.nycmny.fios.verizon.net [74.101.2.6]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id d8466261 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO) for <9front@9front.org>; Sun, 17 Jan 2021 21:20:40 -0800 (PST) Message-ID: <756C95B55C2DABF6755FCB63F332F045@eigenstate.org> To: 9front@9front.org Date: Sun, 17 Jan 2021 21:20:38 -0800 From: ori@eigenstate.org In-Reply-To: <9fef5273-8e1c-4d3e-9c62-790ae227103d@pixelhero.dev> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: RESTful configuration-scale pipelining-scale core hypervisor dependency hypervisor Subject: Re: [9front] Weird >>= operator behaviour in 5c/5l Reply-To: 9front@9front.org Precedence: bulk Quoth Noam Preil : > It could just be architecture specific behavior. > It's a bug. Two, actually. 1) a shift of zero should be optimized out by the compiler; cinap has a change for this in the works already. This fix should hide the second bug. 2) a shift by a literal zero is miscompiled by the assembler into a shift by 32, because of a missed special case in the instruction. encoding. I'm working on fixing the assembler.