From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 82015 invoked by alias); 4 Aug 2017 00:12:40 -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 82004 invoked by uid 89); 4 Aug 2017 00:12:39 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy= X-HELO: relay1.mentorg.com Date: Fri, 04 Aug 2017 00:12:00 -0000 From: Joseph Myers To: Wilco Dijkstra CC: "Ellcey, Steve" , nd , "libc-alpha@sourceware.org" Subject: Re: [PATCH 3/4] Add ILP32 support to aarch64 In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2017-08/txt/msg00139.txt.bz2 On Thu, 3 Aug 2017, Wilco Dijkstra wrote: > The generic implementation may well be faster... I'm not sure where the > requirement of not raising inexact comes from (I don't see it in the definition > of lrint, and we generally don't care since inexact is set by almost every FP > calculation), but if it is absolutely required you'd special case values larger > than LONG_MAX. The requirement comes from lrint being bound to IEEE 754 conversion operations, so only raising inexact under the conditions specified and no spurious inexact. -- Joseph S. Myers joseph@codesourcery.com