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/47716] libgfortran quadmath_weak.h not found on NetBSD 5.1
Date: Tue, 15 Feb 2011 23:20:00 -0000 [thread overview]
Message-ID: <bug-47716-4-5tFlHM0vfK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47716-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47716
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
--- Comment #7 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-02-15 23:17:41 UTC ---
(In reply to comment #6)
> warning: warning: reference to compatibility cabsf()
That seems to be a warning generated by NetBSD's libm, cf.
http://mirror.leaseweb.com/NetBSD/NetBSD-release-5-0/src/lib/libm/compat/compat_cabsf.c
That file contains:
float cabsf __P((struct complex));
__warn_references(cabsf, "warning: reference to compatibility cabsf()");
float
cabsf(struct complex z)
{
return hypotf(z.x, z.y);
}
Which causes the warning. The __warn_references is defined in <sys/cdefs.h>.
Thus, you could also try to silence the warning. hypot(f) should be give an
equivalent result to cabs(f) - thus I do not understand why there is a warning
at the first place. (Depending, of course, on the quality of the hypot(f)
implementation.)
As the warning is due to NetBSD itself and as the quadmath_weak.h issue is
solved, I close this PR.
It would be nice if one could silence the warning - and again build with
Fortran support.
next prev parent reply other threads:[~2011-02-15 23:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 9:45 [Bug libfortran/47716] New: " laurent at guerby dot net
2011-02-13 9:49 ` [Bug libfortran/47716] " burnus at gcc dot gnu.org
2011-02-13 21:15 ` laurent at guerby dot net
2011-02-14 21:04 ` burnus at gcc dot gnu.org
2011-02-15 14:22 ` laurent at guerby dot net
2011-02-15 21:51 ` burnus at gcc dot gnu.org
2011-02-15 22:58 ` laurent at guerby dot net
2011-02-15 23:20 ` burnus at gcc dot gnu.org [this message]
2011-02-16 7:04 ` laurent at guerby dot net
2013-12-09 10:03 ` fxcoudert 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-47716-4-5tFlHM0vfK@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).