From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 112469 invoked by alias); 2 Dec 2019 21:00:38 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 112458 invoked by uid 89); 2 Dec 2019 21:00:38 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=H*MI:sk:1575297, HX-Languages-Length:528 X-HELO: esa4.mentor.iphmx.com IronPort-SDR: mK0244sbTXFLo3Y4CyXtFoqM3yX8K/EYsOSPEg1uuYUXya6714QRSBz5Fh039wLmRahP5tEXQQ g9Bb115Gd6FmfxlIw6Fs6LVhuWRwhyKcEQDbThK4FHOOktGsUVIgZc7B/wbZ3nOc3itaBC0rIn AfQlbCIgeB4llF0pB9ytv5X3GqbMSKPaGpqc463X3Pjp2VsyqAnX6HFi4VgZ2/dEi+NW9BjuOe xXeCGoY1A6S2tu/3Eg3rsjhXVrn0L5NbyohuaSkdI2GQKn7JQKvtvLUVXwUtdGGhPgjM6IKLwf 2Nk= IronPort-SDR: MsF6LISXnN/K0j3jwtaI1SGtLyya5xtypX7AEnI+H4N8DCcx/eu8KyMY6JdZwd3TLbS+j2kDj7 tFaEgMaYRD+fclVADflGQdyI/LdA3C2VDk6e6L5LnRZip+nyWdd9KL9OOXRez+VTAcyTX8WgB/ e+t6MxsTyfbdmG3Z8XM4CRJCPgk3cY2gv8BTUvqyzqcZ4g0jorDaC6igvYzbP4Sdfi2Gd9s5Qs 3Wp8vkpWscFGWakfYP4o7KVDsUJR0L56ft+1HHcKbbTayyHAaCNXfVRfyUcAra4ID4y2cFYCaL wuw= Date: Mon, 02 Dec 2019 21:00:00 -0000 From: Joseph Myers To: Stefan Liebler CC: Subject: Re: [PATCH 13/13] Use GCC builtins for copysign functions if desired. In-Reply-To: <1575297977-2589-14-git-send-email-stli@linux.ibm.com> Message-ID: References: <1575297977-2589-1-git-send-email-stli@linux.ibm.com> <1575297977-2589-14-git-send-email-stli@linux.ibm.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Return-Path: joseph@codesourcery.com X-SW-Source: 2019-12/txt/msg00068.txt.bz2 On Mon, 2 Dec 2019, Stefan Liebler wrote: > This patch is using the corresponding GCC builtin for copysignf, copysign, > copysignl and copysignf128 if the USE_FUNCTION_BUILTIN macros are defined to one > in math-use-builtins.h. I believe this is always safe for these implementations (the only case where GCC might not expand copysign functions inline is copysignl for IBM long double, in the soft-float case). -- Joseph S. Myers joseph@codesourcery.com