From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-200050-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 63620 invoked by alias); 2 Sep 2019 03:19:06 -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 63612 invoked by uid 89); 2 Sep 2019 03:19:06 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-6.8 required=5.0 tests=AWL,BAYES_40,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.1 spammy=HX-Spam-Relays-External:sk:mail-ed, H*RU:sk:mail-ed, HX-HELO:sk:mail-ed, H*r:sk:mail-ed
X-HELO: mail-ed1-f50.google.com
Received: from mail-ed1-f50.google.com (HELO mail-ed1-f50.google.com) (209.85.208.50) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 02 Sep 2019 03:19:05 +0000
Received: by mail-ed1-f50.google.com with SMTP id s49so14348242edb.1        for <gcc@gcc.gnu.org>; Sun, 01 Sep 2019 20:19:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:references:in-reply-to:from:date:message-id:subject:to         :cc;        bh=Y6uDNV7lit7ljOzOm5a9cgI6/hPs9vGhZz4TwR7NLEA=;        b=C5n377+FCtGpmqFJANJMByMTo23djdmbaM+ay4Y1nwCJbs2PD1YyfVxEHUOEiFSee9         YBk3PLSDYNeRL625qbjXJzZzrPEZEGPAK48sqLQgWY7KajHnFXtFjRPq1n2AjwAZ5vj3         76Q3/JIDb6Rbq63b9DjNmS1AIfyVDdkUU5ak4TWVI5BjW7DlIK41nBQYQy9vE4ILITS8         pXnA6nxZ9JjotLpa4dKQ1vXUY2MS09rLokbLRQtPTxOl3ZN8+2PIpfzCDyN14qWCBXl1         AgCBNS4+Jyl8KGwxNAfOLrx/e0EghpMz+rdmD8Nu0tZA/ptdVOlObClHZsiHtYiZ3WSH         1AmQ==
MIME-Version: 1.0
References: <20190822062503.GI31406@gate.crashing.org> <CACMrGjD9oR6jJrN+XJZYsEW+Oheo4uV2JRxm35KX326A07ayrQ@mail.gmail.com> <20190822095620.GK31406@gate.crashing.org> <ri6h867dcok.fsf@suse.cz> <mptimqmvqit.fsf@arm.com> <CACMrGjCeaPFVHh-chy+aFBHxYJOO0Q_fhkAZ52yUPFL4zLaSBQ@mail.gmail.com> <20190825164717.GO31406@gate.crashing.org> <CACMrGjAsrFSZQgbuaEVqBEnjrL2ANV1bHJwLRz4fKTSfWZETOw@mail.gmail.com> <20190826074211.GQ31406@gate.crashing.org> <CACMrGjBN-Un1-qMLdzdzaR3YRo05ukLm9cpyNzdm4vu346g6Gg@mail.gmail.com> <20190830203525.GS31406@gate.crashing.org>
In-Reply-To: <20190830203525.GS31406@gate.crashing.org>
From: Tejas Joshi <tejasjoshi9673@gmail.com>
Date: Mon, 02 Sep 2019 03:19:00 -0000
Message-ID: <CACMrGjDTQWnagXkEUbjRP5rwKH6Oh-AHcZ0Vii67BPVzB7XDmQ@mail.gmail.com>
Subject: Re: Expansion of narrowing math built-ins into power instructions
To: gcc@gcc.gnu.org
Cc: Martin Jambor <mjambor@suse.cz>, hubicka@ucw.cz, segher@kernel.crashing.org, 	joseph@codesourcery.com
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes
X-SW-Source: 2019-09/txt/msg00002.txt.bz2

On Sat, 31 Aug 2019 at 02:05, Segher Boessenkool
<segher@kernel.crashing.org> wrote:
>
> > > > > [ Please don't top-post ]
>
> (I delete everything under your signature, without looking, assuming you
> just forgot to).

Oh sorry, I didn't know the reply button does evil things. :-)

> If long double is double, faddl is the same as fadd, and daddl is just
> normal addition.
>
> If long double is double-double, faddl can be done as fadd on the first
> double precision component of both args, and daddl is just normal addition
> of those.
>
> If long double is IEEE QP, then it is more interesting :-)

On what conditions does the mapping of long double to double/
double-double or IEEE QP changes or depends, so that I can test it.

Thanks,
Tejas