public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlos at codesourcery dot com" <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: Wed, 22 Apr 2009 22:42:00 -0000 [thread overview] Message-ID: <20090422224217.19226.qmail@sourceware.org> (raw) In-Reply-To: <bug-39491-11764@http.gcc.gnu.org/bugzilla/> ------- Comment #18 from carlos at codesourcery dot com 2009-04-22 22:42 ------- Subject: Re: [4.4/4.5 regression] symbol __signbitl@GLIBCXX_3.4 in libstdc++ not exported anymore >> * Original submitter is incorrect, there has never been a >> __signbitl@GLIBCXX_3.4 symbol, and there should not be one now? > > The symbol is present in libstdc++.so.6.0.9 and libstdc++.so.6.0.10, > but not in libstdc++.so.6.0.8 or libstdc++.so.6.0.11. If that's the case, then libstdc++ is to blame, and Benjamin's hackish patch should be reviewed and checked in. >> * I have changed the glibc hppa-linux-gnu port to define __NO_LONG_DOUBLE_MATH, >> and therefore the signbit macro, even in the abscense of optimization, will >> always return a valid signbit function based on the type size. > > I'm not convinced this is a good idea at this point. As far as I know, > it is ok to have the same size for double and long double. However, > they are distinct types. Perhaps I wasn't as clear as I should have been. The glibc port for hppa has always been configured never to build any long double code, and has always assumed that long double is not a distinct type. From glibc's perspective there is no such thing as having double and long double with the same size, there is only a configuration where double exists and all the long double functions alias to their double equivalents. 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. The upside is that, if and when, long double on hppa becomes the 128-bit quad long double, we can just follow the tried-and-tested procedure to migrate the glibc math routines. Cheers, Carlos. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39491
next prev parent reply other threads:[~2009-04-22 22:42 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 [this message] 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 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=20090422224217.19226.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).