public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/39491] [4.4/4.5 regression] symbol __signbitl@GLIBCXX_3.4 in libstdc++ not exported anymore Date: Thu, 23 Apr 2009 16:55:00 -0000 [thread overview] Message-ID: <20090423165507.17842.qmail@sourceware.org> (raw) In-Reply-To: <bug-39491-11764@http.gcc.gnu.org/bugzilla/> ------- Comment #22 from bkoz at gcc dot gnu dot org 2009-04-23 16:55 ------- >The hppa port sets long-double-fcts = no in glibc > and this causes all the aliases to be created, otherwise you'd never > be able to link anything that used `l' ending math functions. Defining > __NO_LONG_DOUBLE_MATH is just another step in the right direction to > avoid using long double functions, and use the double functions instead. It seems to me like setting long-double-fcts = no in glibc should automatically define __NO_LONG_DOUBLE_MATH.... right? Anyway. >From the .so range listed in #18 it looks like this was a regression in 4.2/4.3, perhaps related to C library changes. There was a __signbitl export in gnu.ver. gcc-3.4.6 __signbitl in GLIBCXX_3.4 gcc-4.1.2 __signbitl in GLIBCXX_3.4 gcc-4.2.4 __signbitl in GLIBCXX_3.4 gcc-4.3 __signbitl in GLIBCXX_3.4 So that's how it leaked out of libstdc++ so's. However, this symbol was never actually defined, exported and placed in the abi baseline for hppa-linux-gnu, inclusive gcc-3.4 to trunk. Or any other platform. Thus, why it was removed from gnu.ver, mistakenly as it turns out. . It would be my inclination to fix glibc and then alias as per Jakub's #13 comment for hppa-linux only. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39491
next prev parent reply other threads:[~2009-04-23 16:55 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-03-18 10:25 [Bug target/39491] New: [4.4 " doko at ubuntu dot com 2009-03-31 15:59 ` [Bug target/39491] [4.4/4.5 " jsm28 at gcc dot gnu dot org 2009-04-01 8:49 ` jakub at gcc dot gnu dot org 2009-04-16 22:12 ` [Bug libstdc++/39491] " bkoz at gcc dot gnu dot org 2009-04-16 22:38 ` bkoz at gcc dot gnu dot org 2009-04-16 23:09 ` bkoz at gcc dot gnu dot org 2009-04-17 0:21 ` dave at hiauly1 dot hia dot nrc dot ca 2009-04-17 0:56 ` danglin at gcc dot gnu dot org 2009-04-21 3:05 ` bkoz at gcc dot gnu dot org 2009-04-21 14:36 ` doko at ubuntu dot com 2009-04-21 15:57 ` jakub at gcc dot gnu dot org 2009-04-21 17:28 ` dave at hiauly1 dot hia dot nrc dot ca 2009-04-21 19:49 ` danglin at gcc dot gnu dot org 2009-04-21 20:16 ` carlos at codesourcery dot com 2009-04-21 21:02 ` dave at hiauly1 dot hia dot nrc dot ca 2009-04-22 9:13 ` jakub at gcc dot gnu dot org 2009-04-22 13:45 ` dave at hiauly1 dot hia dot nrc dot ca 2009-04-22 14:34 ` jakub at gcc dot gnu dot org 2009-04-22 18:34 ` carlos at codesourcery dot com 2009-04-22 19:33 ` dave at hiauly1 dot hia dot nrc dot ca 2009-04-22 22:42 ` carlos at codesourcery dot com 2009-04-22 23:06 ` dave at hiauly1 dot hia dot nrc dot ca 2009-04-22 23:34 ` joseph at codesourcery dot com 2009-04-23 6:28 ` jakub at gcc dot gnu dot org 2009-04-23 16:55 ` bkoz at gcc dot gnu dot org [this message] 2009-04-23 17:16 ` bkoz at gcc dot gnu dot org 2009-04-23 19:01 ` joseph at codesourcery dot com 2009-04-24 20:32 ` carlos at codesourcery dot com 2009-04-24 20:41 ` carlos at codesourcery dot com 2009-04-27 22:47 ` [Bug libstdc++/39491] [4.2/4.3 regression] symbol __signbitl@GLIBCXX_3.4 in libstdc++ exported bkoz at gcc dot gnu dot org 2009-04-28 20:57 ` carlos at codesourcery dot com 2009-04-28 23:57 ` jakub at gcc dot gnu dot org 2009-04-28 23:59 ` jakub at gcc dot gnu dot org 2009-04-29 1:03 ` dave at hiauly1 dot hia dot nrc dot ca 2009-04-29 15:07 ` carlos at codesourcery dot com 2009-04-29 19:41 ` bkoz at gcc dot gnu dot org 2009-05-06 9:19 ` [Bug libstdc++/39491] [4.3 " paolo dot carlini at oracle dot com 2009-05-12 22:43 ` bkoz at gcc dot gnu dot 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=20090423165507.17842.qmail@sourceware.org \ --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).