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.8 required=5.0 tests=DATE_IN_PAST_12_24 autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 13632 invoked from network); 3 Jun 2021 08:12:05 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 3 Jun 2021 08:12:05 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 1ess; Wed Jun 2 10:46:07 -0400 2021 Message-ID: <28CA9BCE9BFD944A25F28B2454085A76@felloff.net> Date: Wed, 02 Jun 2021 16:45:57 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: 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: leveraged event strategy dependency table-aware interface Subject: Re: [9front] [PATCH] sha3 but fixed the code style Reply-To: 9front@9front.org Precedence: bulk hm.... are you sure you should use 64-bit *SIGNED* integers here? wouldnt that screw up the bit rotations because of the sign bit replication on down shift? > can fulton test if this actually works? the right thing todo is to provide unit test with test vectors from the spec... it doesnt need to be in the mkfile... just like sha2test.c and chachatest.c. -- cinap