public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-94586-4-5Ja4bRBC6Y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94586-4@http.gcc.gnu.org/bugzilla/>

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

--- 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 
>
> 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 
> or both.
Why?  It's what HP did?

On ia64, libm contains a full quad implementation with q suffix.  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  the same 64-bit
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.

  parent reply	other threads:[~2020-04-22 17:10 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 21:22 [Bug libfortran/94586] New: " danglin at gcc dot gnu.org
2020-04-14  3:02 ` [Bug libfortran/94586] " kargl at gcc dot gnu.org
2020-04-14  7:23 ` rguenth at gcc dot gnu.org
2020-04-14  7:51 ` sgk at troutmask dot apl.washington.edu
2020-04-14 12:55 ` dave.anglin at bell dot net
2020-04-14 15:40 ` sgk at troutmask dot apl.washington.edu
2020-04-14 17:24 ` dave.anglin at bell dot net
2020-04-14 18:12 ` sgk at troutmask dot apl.washington.edu
2020-04-14 20:48 ` dave.anglin at bell dot net
2020-04-14 22:08 ` sgk at troutmask dot apl.washington.edu
2020-04-14 23:46 ` dave.anglin at bell dot net
2020-04-15 15:02 ` sgk at troutmask dot apl.washington.edu
2020-04-15 15:28 ` dave.anglin at bell dot net
2020-04-15 18:04 ` dave.anglin at bell dot net
2020-04-15 18:14 ` sgk at troutmask dot apl.washington.edu
2020-04-15 18:32 ` sgk at troutmask dot apl.washington.edu
2020-04-15 19:10 ` dave.anglin at bell dot net
2020-04-15 19:26 ` dave.anglin at bell dot net
2020-04-16  1:10 ` dave.anglin at bell dot net
2020-04-16  1:15 ` dave.anglin at bell dot net
2020-04-16  2:10 ` sgk at troutmask dot apl.washington.edu
2020-04-16 20:06 ` danglin at gcc dot gnu.org
2020-04-16 21:07 ` sgk at troutmask dot apl.washington.edu
2020-04-16 21:32 ` dave.anglin at bell dot net
2020-04-17  0:58 ` sgk at troutmask dot apl.washington.edu
2020-04-21 17:03 ` jakub at gcc dot gnu.org
2020-04-21 17:29 ` danglin at gcc dot gnu.org
2020-04-21 17:36 ` danglin at gcc dot gnu.org
2020-04-21 20:17 ` danglin at gcc dot gnu.org
2020-04-22 14:54 ` foreese at gcc dot gnu.org
2020-04-22 15:12 ` danglin at gcc dot gnu.org
2020-04-22 15:33 ` dave.anglin at bell dot net
2020-04-22 15:47 ` danglin at gcc dot gnu.org
2020-04-22 16:02 ` dave.anglin at bell dot net
2020-04-22 16:27 ` sgk at troutmask dot apl.washington.edu
2020-04-22 17:10 ` dave.anglin at bell dot net [this message]
2020-04-22 19:34 ` cvs-commit at gcc dot gnu.org
2020-04-22 19:44 ` danglin at gcc dot gnu.org
2020-04-22 19:58 ` danglin at gcc dot gnu.org
2020-04-22 21:41 ` danglin at gcc dot gnu.org
2020-04-23 14:12 ` cvs-commit at gcc dot gnu.org
2020-04-23 14:38 ` jakub at gcc dot gnu.org
2020-04-24 11:35 ` rguenth at gcc dot gnu.org
2020-04-24 11:37 ` jakub at gcc dot gnu.org
2020-04-24 11:58 ` danglin at gcc dot gnu.org
2020-07-20 10:18 ` dominiq at lps dot ens.fr
2020-07-20 19:53 ` danglin at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-94586-4-5Ja4bRBC6Y@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).