From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18941 invoked by alias); 21 Dec 2010 16:22:10 -0000 Received: (qmail 18930 invoked by uid 22791); 21 Dec 2010 16:22:08 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,TW_BG X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 21 Dec 2010 16:22:04 +0000 From: "dje at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/47032] New: libgfortran references complex long double functions missing on AIX X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libfortran X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dje at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Tue, 21 Dec 2010 16:22:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-12/txt/msg02443.txt.bz2 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.