public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub 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: Wed, 22 Apr 2009 09:13:00 -0000	[thread overview]
Message-ID: <20090422091253.21014.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39491-11764@http.gcc.gnu.org/bugzilla/>



------- Comment #13 from jakub at gcc dot gnu dot org  2009-04-22 09:12 -------
If hppa-linux has long double the same as double (which raises the question why
it hasn't switched over to 128-bit long double together with
powerpc*/sparc*/s390*/alpha back in 2006), then __NO_LONG_DOUBLE_MATH should be
defined and therefore no code will ever reference __signbitl from signbit macro
(and __signbitl isn't a supported API, so nothing should really care).

If we really want to change libstdc++ (which I'm not sure about, can you find a
single shared library or binary that references __signbitl from libstdc++.so?),
then the patch should actually handle __signbitl by calling __signbit and also
should be through .symver directive turned into @ symbol instead of @@ to make
sure nothing newly linked can reference it from libstdc++.so.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39491


  parent reply	other threads:[~2009-04-22  9:13 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 [this message]
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
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=20090422091253.21014.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: link
Be 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).