public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/46584] FAIL: gfortran.dg/quad_1.f90 -O (test for excess errors) Date: Sat, 04 Dec 2010 13:14:00 -0000 [thread overview] Message-ID: <bug-46584-4-vJ0oWdgZwb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46584-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46584 --- Comment #8 from Tobias Burnus <burnus at gcc dot gnu.org> 2010-12-04 13:13:51 UTC --- The committed patch removed the complex math functions from the quad_1.f90 test. I think the PR can be closed after confirmation that the failure is gone. Regarding hppa64-hp-hpux: I think one could (e.g. with weak alias) consider building a libquadmath which provides also "long double" names on platforms where the libm does not provide the required functionality and where __float128 and long double are the same data type. However, I think that's an unrelated issue, which I want to leave to the maintainers of the relevant platforms (seemingly only: HPUX on ia64).
next prev parent reply other threads:[~2010-12-04 13:14 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-21 0:22 [Bug libfortran/46584] New: " danglin at gcc dot gnu.org 2010-11-26 1:41 ` [Bug libfortran/46584] " danglin at gcc dot gnu.org 2010-11-26 8:44 ` burnus at gcc dot gnu.org 2010-11-26 9:36 ` ebotcazou at gcc dot gnu.org 2010-11-26 14:03 ` burnus at gcc dot gnu.org 2010-11-26 20:58 ` dave at hiauly1 dot hia.nrc.ca 2010-11-26 21:53 ` joseph at codesourcery dot com 2010-12-04 13:08 ` burnus at gcc dot gnu.org 2010-12-04 13:14 ` burnus at gcc dot gnu.org [this message] 2010-12-06 20:10 ` ebotcazou at gcc dot gnu.org 2010-12-07 10:10 ` burnus 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-46584-4-vJ0oWdgZwb@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).