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 17:16:00 -0000 [thread overview] Message-ID: <20090423171633.7618.qmail@sourceware.org> (raw) In-Reply-To: <bug-39491-11764@http.gcc.gnu.org/bugzilla/> ------- Comment #23 from bkoz at gcc dot gnu dot org 2009-04-23 17:16 ------- So: * Original submitter is incorrect, there has never been a __signbitl@GLIBCXX_3.4 symbol, and there should not be one now? Right. This should have manifested as an abi-check FAIL starting in gcc-4.2, as a new symbol was added with the original version label. So gcc-4.2/4.3 had a regression from gcc-4.1 that gcc-4.4 fixed. That regression is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32666 >From that first log: http://gcc.gnu.org/bugzilla/attachment.cgi?id=13863&action=view You see: 65 __signbitl version status: incompatible GLIBCXX_3.4 type: function status: added >From this I conclude that the libstdc++ abi checking was working, but ignored for 4.2 and the 4.3 release on this platform. That's ok, everybody was busy and there were some issues, but for 4.4 we are back on it. Of course, on the meta level, libstdc++ doing this math library hacking is just wrong and prone to failure: we want the C99 math library assumed and underneath us in either gcc support libs or at the libc level. That's why gcc-4.4/trunk tries to flee from this area after attempting to burn the remains of libmath. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39491
next prev parent reply other threads:[~2009-04-23 17:16 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 2009-04-23 17:16 ` bkoz at gcc dot gnu dot org [this message] 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=20090423171633.7618.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).