public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <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: Mon, 20 Jul 2020 19:53:19 +0000 [thread overview] Message-ID: <bug-94586-4-n826WXh5vP@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 John David Anglin <danglin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #48357|0 |1 is obsolete| | --- Comment #45 from John David Anglin <danglin at gcc dot gnu.org> --- Created attachment 48901 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48901&action=edit Patch to use libquadmath with gfortran on hpux This patch enables the use of libquadmath with gfortran on hpux. There is no system support for long double (or __flat128) math, so it would be nice if we could use the libquadmath support for __float128. The attached patch works with both 32 and 64-bit hpux targets. There are a couple of testsuite fails that I haven't had time to investigate yet. But mostly it works.
prev parent reply other threads:[~2020-07-20 19:53 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 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 [this message]
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-n826WXh5vP@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: linkBe 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).