From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 50249 invoked by alias); 16 Nov 2018 16:50:09 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 50239 invoked by uid 89); 16 Nov 2018 16:50:09 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=About, convert.c, case_flt_fn, GSOC X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 16 Nov 2018 16:50:07 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=SVR-IES-MBX-03.mgc.mentorg.com) by relay1.mentorg.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-SHA384:256) id 1gNhJj-0003M8-GH from joseph_myers@mentor.com ; Fri, 16 Nov 2018 08:50:03 -0800 Received: from digraph.polyomino.org.uk (137.202.0.90) by SVR-IES-MBX-03.mgc.mentorg.com (139.181.222.3) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 16 Nov 2018 16:50:00 +0000 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.90_1) (envelope-from ) id 1gNhJf-0003ap-HC; Fri, 16 Nov 2018 16:49:59 +0000 Date: Fri, 16 Nov 2018 19:00:00 -0000 From: Joseph Myers To: Tejas Joshi CC: Subject: Re: About GSOC. In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2018-11/txt/msg00088.txt.bz2 On Fri, 16 Nov 2018, Tejas Joshi wrote: > About roundeven, there might be need to add case to > expand_builtin_int_roundingfn similar to > ceil, for expansion. > But how is round() expanded since there's no > entry for it in expand_builtin_int_roundingfn ? Please see the comment above expand_builtin_int_roundingfn, and that above expand_builtin_int_roundingfn_2, which handle different sets of functions. Those functions are of no relevance to adding support for built-in roundeven. (They might be of relevance to support for built-in fromfp functions, depending on whether the detailed semantics allows casts-to-integer of calls to other functions to be converted into calls to the fromfp functions. But I don't think inventing __builtin_lroundeven would be appropriate.) > Also, is it right to have an added case for roundeven in convert.c > along CASE_FLT_FN (BUILT_IN_ROUND) > in convert_to_integer_1? Not until doing things with fromfp functions. There is no lroundeven (for example) in TS 18661-1. -- Joseph S. Myers joseph@codesourcery.com