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=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 16012 invoked from network); 15 Aug 2021 21:49:13 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 15 Aug 2021 21:49:13 -0000 Received: (qmail 28488 invoked by uid 550); 15 Aug 2021 21:49:11 -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 28466 invoked from network); 15 Aug 2021 21:49:11 -0000 Date: Sun, 15 Aug 2021 17:48:58 -0400 From: Rich Felker To: Stefan Kanthak Cc: Szabolcs Nagy , musl@lists.openwall.com Message-ID: <20210815214857.GK13220@brightrain.aerifal.cx> References: <20210810213455.GB37904@port70.net> <20210814234612.GH37904@port70.net> <367A4018B58A4E308E2A95404362CBFB@H270> <20210815145614.GI37904@port70.net> <1F3569BD7D6E45889B7518DC9BE5004B@H270> <20210815154843.GH13220@brightrain.aerifal.cx> <20210815164903.GJ13220@brightrain.aerifal.cx> <24DD1FF8BAC240228EB53467118A6F90@H270> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <24DD1FF8BAC240228EB53467118A6F90@H270> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] [PATCH #2] Properly simplified nextafter() On Sun, Aug 15, 2021 at 10:52:24PM +0200, Stefan Kanthak wrote: > Rich Felker wrote: > > > I really have better things to be doing than putting up with repeated > > toxic interactions for the sake of a supposed miniscule improvement in > > something nobody has identified as having any problem to begin with. > > Nobody as in "Niemand hat die Absicht eine Mauer zu bauen"? > Or just nobody EXCEPT ME bothered to take a look at the code of your > nextafter() and noticed its performance deficit (at least on AMD64 > and i386)? I guess I missed your initial report about what software you were running that was spending more than 1% of its execution time in nextafter. As I understand it, what happened was that you were reading the code and thought "I bet I could do better". Maybe you can. But can you do sufficiently better that it makes any practical difference, to be worth the time spent reviewing that it's correct? Probably not. But now, in your case, the bar is even higher. It's: Can you do sufficiently better to be worth subjecting our good contributors to someone who wants to insult and abuse them and demand their time doing unproductive things? Given how fast the function already is, and how improbable it is that it makes any difference to the run time of any real code, the answer is most certainly no. You've raised the bar for your own contribution so high that it can't be met. > JFTR: your implementation is NON-COMPLIANT! > I recommend to read the ISO C standard and follow it by the word. Making unspecific claims lik that to waste our time trying to figure out what you mean is not making that bar any lower. > > If you want to engage constructively, you're welcome to. This is not > > it. > > You are most obviously NOT interested in performance improvement, or > just to stubborn: choose what you like better. I am not interested in further subjecting the authors of our existing code to your abuse. Please leave. Rich