public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/47032] New: libgfortran references complex long double functions missing on AIX Date: Tue, 21 Dec 2010 16:22:00 -0000 [thread overview] Message-ID: <bug-47032-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47032 Summary: libgfortran references complex long double functions missing on AIX Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: dje@gcc.gnu.org ld: 0711-317 ERROR: Undefined symbol: .__copysignl128 ld: 0711-317 ERROR: Undefined symbol: .__nextafterl128 ld: 0711-317 ERROR: Undefined symbol: .__scalbnl128 ld: 0711-317 ERROR: Undefined symbol: .__cabsl128 ld: 0711-317 ERROR: Undefined symbol: .__cargl128 ld: 0711-317 ERROR: Undefined symbol: .__truncl128 /* * There are two forms of long double on AIX. The default * form of long double is the same as a double - 64 bits. There * is a 128-bit form available with some compilers. If that compiler * defines __LONGDOUBLE128, then long doubles are 128-bit instead of * 64-bit. Since the same library routine cannot be used for 128-bit * and 64-bit values, the 128-bit routines are renamed and macros are * used to manage the name spaces. It is not necessarily the case that * all of the 128-bit versions are available, but the macros are defined * intentionally since the 64-bit versions can provide incorrect results * when long double values were expected. If 64-bit versions are required * in 128-bit mode, then the code needs to invoke the double routines a * rather than the long double routines. */ As the comment mentions, not all functions are available(!), but the functions are redefined to prevent wrong results.
next reply other threads:[~2010-12-21 16:22 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-21 16:22 dje at gcc dot gnu.org [this message] 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
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@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).