From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.0 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.2 Received: from mother.openwall.net (mother.openwall.net [195.42.179.200]) by inbox.vuxu.org (OpenSMTPD) with SMTP id 6fbbbf80 for ; Sat, 22 Feb 2020 19:59:40 +0000 (UTC) Received: (qmail 29968 invoked by uid 550); 22 Feb 2020 19:59:38 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 29950 invoked from network); 22 Feb 2020 19:59:38 -0000 Date: Sat, 22 Feb 2020 14:59:25 -0500 From: Rich Felker To: musl@lists.openwall.com Message-ID: <20200222195925.GK1663@brightrain.aerifal.cx> References: <20200114185058.GV23985@port70.net> <20200114185835.GG30412@brightrain.aerifal.cx> <20200206145156.GF1663@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] Q: dealing with missing removal of excess precision On Thu, Feb 06, 2020 at 08:15:30PM +0300, Alexander Monakov wrote: > On Thu, 6 Feb 2020, Rich Felker wrote: > > > I think I might like to go ahead and apply these patches now, or at > > least some of them -- the ones fixing excess precision -- rather > > waiting, because I got a report of a nasty bug stemming from excess > > precision of the inverse trig functions: > > That might be exactly the empty set of patches, as I did not yet post > any for functions that might return with excess precision. > > Be advised that I found bugs in my patches, so given that no one so far > has pointed them out on the mailing list indicates that either nobody > bothered to review, or people are keeping the findings to themselves. Can you comment on these bugs? Now that the 1.2.0 release is out I'd like to follow up with reviewing/merging these. Rich