From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: from second.openwall.net (second.openwall.net [193.110.157.125]) by inbox.vuxu.org (Postfix) with SMTP id DAFE22DAB9 for ; Wed, 28 Aug 2024 22:32:16 +0200 (CEST) Received: (qmail 1775 invoked by uid 550); 28 Aug 2024 20:32: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 1743 invoked from network); 28 Aug 2024 20:32:11 -0000 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.ispras.ru A5B8F40AC4FC DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ispras.ru; s=default; t=1724877123; bh=5XSyvEpnW44vg89Y6K14YLLhK1pQVZHyaBgdGDzDOYA=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=pCLuknzl31hykt54fiqQGNd8Xs/3UTb4Tb+HoVfzadYEp+uYXH8R2Npim3IoUY07M EKdG8lbmIb1xnO21H11UASrHjTySgMOQj6LTuDCWOGsDU/Nsx/nTrpcNtKcwgW8bOG B6cMmeuYlY9Ms0t8Q6Ogld+wwc8cuEG6bK6Z+4H4= Date: Wed, 28 Aug 2024 23:32:03 +0300 (MSK) From: Alexander Monakov To: musl@lists.openwall.com cc: =?ISO-8859-15?Q?Alex_R=F8nne_Petersen?= In-Reply-To: <20240828201514.GH10433@brightrain.aerifal.cx> Message-ID: <2f89009e-4290-90d7-d625-09dbf879340a@ispras.ru> References: <20240828152826.826990-1-alex@alexrp.com> <20240828201514.GH10433@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Subject: Re: [musl] [PATCH] configure: prevent compilers from turning a * b + c into fma(a, b, c) On Wed, 28 Aug 2024, Rich Felker wrote: > With that said, I don't see how the compiler could ever generate calls > to fma(), since we're -ffreestanding, but I think it could generate > inline fma instructions on targets where they're available, and this > is generally undesirable (see above). For gcc, I think -std=c99 > already has that covered, but I'm not sure what clang does. Modern Clang implements the FP_CONTRACT pragma, with default state "on". Of course, the -ffp-contract= command-line switch is also available. Alexander