From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 2A967385DC00; Wed, 22 Apr 2020 17:10:59 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2A967385DC00
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1587575459;
 bh=UwfJW33NrH/eJG7jM/5kDPTNDyl8oSpWnMMCOjRzEXk=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=jLQfwvV7IJixKCZnxaH3GV54C7DnP4gr7uC7ZtlmPZQ4YWcwVPjUb2CGvQeLD9L+9
 /1Dn7+jsdWsbqs9btm5yi+GK9Beko+0v1+3OxfpewgbxUuLNIUiFhvn//91SA+wsny
 eMP9cABrKXujC1ymmEKU7xw6oUrKVrTFKUCjXaoE=
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/94586] trigd_lib.inc:84:28: error: implicit
 declaration of function 'fmaf'
Date: Wed, 22 Apr 2020 17:10:58 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dave.anglin at bell dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-94586-4-5Ja4bRBC6Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-94586-4@http.gcc.gnu.org/bugzilla/>
References: <bug-94586-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2020 17:10:59 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94586

--- Comment #35 from dave.anglin at bell dot net ---
On 2020-04-22 12:27 p.m., sgk at troutmask dot apl.washington.edu wrote:
> I suspect that having HPUX map=20
>
> REAL(4)  <--> float       ! f suffix
> REAL(8)  <--> double      ! no suffix
> REAL(16) <--> __float128  ! q suffix
>
> may cause issues with either ISO C binding or IEEE 754 module=20
> or both.
Why?=C2=A0 It's what HP did?

On ia64, libm contains a full quad implementation with q suffix.=C2=A0 Both=
 l and w
sufixes are used
with 80-bit floating types (long double and double extended).

Many targets have double and long double both mapped to=C2=A0 the same 64-b=
it
floating type.

So, I don't see why long double and __float128 can't be mapped to the same
128-bit floating type.
It's been that way for years.=