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 target/47032] libgfortran references complex long double functions missing on AIX Date: Sat, 12 Feb 2011 15:08:00 -0000 [thread overview] Message-ID: <bug-47032-4-kyOahbnfKE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47032-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47032 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #12 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-02-12 15:04:48 UTC --- (In reply to comment #11) > While this is absolutely true, the major problem here is that gcc should not > have switched to 128bit long double at all with AIX 6.1 (bug#46481). Cf. http://gcc.gnu.org/ml/gcc/2011-02/msg00109.html and http://gcc.gnu.org/ml/gcc/2011-02/msg00159.html * * * For the libgfortran side: Seems as if one should add a "#include <math.h>"-based link test (cf. comment 8 and 10). libgfortran currently only uses the functions if available (configure check). The effect, if the are not, is the following: (In reply to comment #0) > ld: 0711-317 ERROR: Undefined symbol: .__copysignl128 > ld: 0711-317 ERROR: Undefined symbol: .__nextafterl128 Used by Fortran's NEAREST intrinsic (if available; no fall back if not) - thus, it will fail if a user calls this function but should otherwise be OK. > ld: 0711-317 ERROR: Undefined symbol: .__scalbnl128 Used for the intrinsics RRSPACING, SPACING and SET_EXPONENT. > ld: 0711-317 ERROR: Undefined symbol: .__truncl128 Used for Fortran's ERFC_SCALED intrinsic. > ld: 0711-317 ERROR: Undefined symbol: .__cabsl128 > ld: 0711-317 ERROR: Undefined symbol: .__cargl128 gfortran offers a replacement function in intrinsics/c99_functions.c, if configure believes that those are not available. I think most codes/users do not need either of NEAREST, ERFC_SCALED, RRSPACING, SPACING and SET_EXPONENT. (I do not know whether other math functions are effected, whose calls are directly generated via the front end.)
prev parent reply other threads:[~2011-02-12 15:05 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-21 16:22 [Bug libfortran/47032] New: " dje at gcc dot gnu.org 2010-12-21 16:42 ` [Bug target/47032] " kargl at gcc dot gnu.org 2010-12-21 17:08 ` dje at gcc dot gnu.org 2010-12-21 18:37 ` sgk at troutmask dot apl.washington.edu 2010-12-28 16:10 ` rguenth at gcc dot gnu.org 2011-01-06 19:15 ` dje at gcc dot gnu.org 2011-01-25 20:34 ` michael.haubenwallner at salomon dot at 2011-02-04 5:16 ` rwild at gcc dot gnu.org 2011-02-08 20:49 ` pogma at gcc dot gnu.org 2011-02-08 20:55 ` sgk at troutmask dot apl.washington.edu 2011-02-08 21:04 ` pogma at gcc dot gnu.org 2011-02-08 22:24 ` michael.haubenwallner at salomon dot at 2011-02-12 15:08 ` burnus 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-47032-4-kyOahbnfKE@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).