From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-199922-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 78112 invoked by alias); 15 Aug 2019 18:54:38 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 78103 invoked by uid 89); 15 Aug 2019 18:54:38 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=
X-HELO: gate.crashing.org
Received: from gate.crashing.org (HELO gate.crashing.org) (63.228.1.57) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 15 Aug 2019 18:54:37 +0000
Received: from gate.crashing.org (localhost.localdomain [127.0.0.1])	by gate.crashing.org (8.14.1/8.14.1) with ESMTP id x7FIsWFC004919;	Thu, 15 Aug 2019 13:54:32 -0500
Received: (from segher@localhost)	by gate.crashing.org (8.14.1/8.14.1/Submit) id x7FIsVE0004913;	Thu, 15 Aug 2019 13:54:31 -0500
Date: Thu, 15 Aug 2019 18:54:00 -0000
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Tejas Joshi <tejasjoshi9673@gmail.com>
Cc: gcc@gcc.gnu.org, Martin Jambor <mjambor@suse.cz>, hubicka@ucw.cz,        joseph@codesourcery.com
Subject: Re: Expansion of narrowing math built-ins into power instructions
Message-ID: <20190815185431.GP31406@gate.crashing.org>
References: <20190812175450.GB31406@gate.crashing.org> <alpine.DEB.2.21.1908122118140.18203@digraph.polyomino.org.uk> <20190812215224.GC31406@gate.crashing.org> <CACMrGjDbF8qyaF8_p5ofOT7gFRqMyOTtzxsKRM3r2aXX+8KS+A@mail.gmail.com> <20190814072127.GE31406@gate.crashing.org> <alpine.DEB.2.21.1908141608430.14831@digraph.polyomino.org.uk> <20190814202102.GI31406@gate.crashing.org> <alpine.DEB.2.21.1908142022330.24610@digraph.polyomino.org.uk> <20190814210015.GJ31406@gate.crashing.org> <CACMrGjCcY_b4zDb2MprOCJa1Z3H-_1SdP+2XkCsf0ckeyY5A9w@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACMrGjCcY_b4zDb2MprOCJa1Z3H-_1SdP+2XkCsf0ckeyY5A9w@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
X-IsSubscribed: yes
X-SW-Source: 2019-08/txt/msg00116.txt.bz2

On Thu, Aug 15, 2019 at 03:29:03PM +0530, Tejas Joshi wrote:
> Also, in what manner should float_contract/narrow be different from
> float_truncate as both are trying to do similar things? (truncation
> from DF to SF)

It's just a different name, nothing more, nothing less.  Because it is
a different name it can not be accidentally generated from actual
truncations.


Segher