public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/46416] libquadmath: missing functions Date: Thu, 06 Jan 2011 13:18:00 -0000 [thread overview] Message-ID: <bug-46416-4-gdPI0qNwJs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46416-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46416 --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-01-06 11:40:38 UTC --- There is no __real128, just __float128. Also, I think either it should use some extern inlinish quadmath.h specific macro (and it needs to care about g++ vs. gcc difference and which gcc versions support gnu_inline attribute). And also even if you have those extern inlines in the header, you still have to provide an out of line definition for them, i.e. in libquadmath sources, not headers. I'll take care of it.
next prev parent reply other threads:[~2011-01-06 11:40 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-10 16:49 [Bug fortran/46416] New: libquadmath: Complex inverse hyperbolic/trigonometric function missing: casinhq etc burnus at gcc dot gnu.org 2010-12-27 23:54 ` [Bug fortran/46416] libquadmath: missing functions dfranke at gcc dot gnu.org 2010-12-27 23:54 ` dfranke at gcc dot gnu.org 2011-01-05 18:00 ` burnus at gcc dot gnu.org 2011-01-05 22:31 ` jakub at gcc dot gnu.org 2011-01-06 11:40 ` burnus at gcc dot gnu.org 2011-01-06 13:18 ` jakub at gcc dot gnu.org [this message] 2011-01-16 16:55 ` jakub at gcc dot gnu.org 2011-01-16 17:15 ` jakub at gcc dot gnu.org 2011-01-17 9:15 ` jakub 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-46416-4-gdPI0qNwJs@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).