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 fortran/51616] [4.7 Regression] gfortran.dg/quad_2.f90 fails on hppa*-*-hpux*
Date: Thu, 12 Jan 2012 07:58:00 -0000 [thread overview]
Message-ID: <bug-51616-4-8YMLfwVDgJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51616-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51616
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #9 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-01-12 07:57:53 UTC ---
Please confirm that it no longer fails.
There is now a dg-effective-target check which does not run the test case if
for the highest available floating-point data type (here: REAL(16)) no sqrt
function is available.
Thus, the test case will no longer fail as it is not run.
(In reply to comment #7)
> There was some discussion last year about adding support
> to provide `l' aliases to the `q' routines in libquadmath.
I think one could add - for HPUX - a configure test whether (a) libquadmath can
be build, (b) whether "long double" and __float128 are the same, and (c)
whether "sqrtl" is not available. If this is fulfilled, one could provide the
symbols in libquadmath. But that's a different issue and should be started by
someone who has access to such a system.
next prev parent reply other threads:[~2012-01-12 7:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 0:28 [Bug fortran/51616] New: " danglin at gcc dot gnu.org
2011-12-19 1:04 ` [Bug fortran/51616] " kargl at gcc dot gnu.org
2011-12-19 1:29 ` dave.anglin at bell dot net
2011-12-19 1:45 ` sgk at troutmask dot apl.washington.edu
2011-12-19 1:49 ` danglin at gcc dot gnu.org
2011-12-19 2:24 ` sgk at troutmask dot apl.washington.edu
2011-12-19 9:23 ` rguenth at gcc dot gnu.org
2011-12-19 13:13 ` dave.anglin at bell dot net
2011-12-30 15:49 ` danglin at gcc dot gnu.org
2012-01-12 6:56 ` burnus at gcc dot gnu.org
2012-01-12 7:58 ` burnus at gcc dot gnu.org [this message]
2012-01-13 18:55 ` steven at gcc dot gnu.org
2012-01-15 20:26 ` 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-51616-4-8YMLfwVDgJ@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).