public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adconrad at 0c3 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65670] [5 Regression] missing libstdc++ symbols on powerpc64le-linux-gnu and arm-linux-gnueabi
Date: Tue, 07 Apr 2015 04:03:00 -0000 [thread overview]
Message-ID: <bug-65670-4-P6jDKp06Qh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65670-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65670
Adam Conrad <adconrad at 0c3 dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adconrad at 0c3 dot net
--- Comment #9 from Adam Conrad <adconrad at 0c3 dot net> ---
Testing in an Ubuntu 15.04 chroot with the latest distro 4.9 and the latest 5.0
from Matthias's PPA, I see this:
(vivid-ppc64el)adconrad@kelsey01:~$ objdump -T
/usr/lib/powerpc64le-linux-gnu/libstdc++.so.6.0.20 | grep 17bad_function_call
000000000014f268 w DO .data.rel.ro 0000000000000028 GLIBCXX_3.4.15
_ZTVSt17bad_function_call
00000000000f7ff0 g DF .text 0000000000000050 GLIBCXX_3.4.15 0x60
_ZNSt17bad_function_callD0Ev
00000000000f7f80 g DF .text 0000000000000020 GLIBCXX_3.4.18 0x60
_ZNKSt17bad_function_call4whatEv
00000000000f7fa0 g DF .text 0000000000000044 GLIBCXX_3.4.15 0x60
_ZNSt17bad_function_callD1Ev
000000000014f250 w DO .data.rel.ro 0000000000000018 GLIBCXX_3.4.15
_ZTISt17bad_function_call
00000000000f7fa0 g DF .text 0000000000000044 GLIBCXX_3.4.15 0x60
_ZNSt17bad_function_callD2Ev
(vivid-ppc64el)adconrad@kelsey01:~$ objdump -T
whee/usr/lib/powerpc64le-linux-gnu/libstdc++.so.6.0.21 | grep
17bad_function_call
00000000000e1e70 g DF .text 0000000000000050 GLIBCXX_3.4.15 0x60
_ZNSt17bad_function_callD0Ev
00000000000e1e20 g DF .text 0000000000000044 GLIBCXX_3.4.15 0x60
_ZNSt17bad_function_callD2Ev
00000000000e1e00 g DF .text 0000000000000020 GLIBCXX_3.4.18 0x60
_ZNKSt17bad_function_call4whatEv
00000000001ea988 w DO .data.rel.ro 0000000000000028 GLIBCXX_3.4.15
_ZTVSt17bad_function_call
00000000001ea970 w DO .data.rel.ro 0000000000000018 GLIBCXX_3.4.15
_ZTISt17bad_function_call
00000000000e1e20 g DF .text 0000000000000044 GLIBCXX_3.4.15 0x60
_ZNSt17bad_function_callD1Ev
In other words, it all looks fine to me, so I'm not entirely sure where he's
seeing the regression.
next prev parent reply other threads:[~2015-04-07 4:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 22:17 [Bug target/65670] New: [5 Regression] missing libstdc++ symbols on powerpc64le-linux-gnu doko at gcc dot gnu.org
2015-04-06 8:54 ` [Bug target/65670] [5 Regression] missing libstdc++ symbols on powerpc64le-linux-gnu and arm-linux-gnueabi mkuvyrkov at gcc dot gnu.org
2015-04-06 9:10 ` doko at gcc dot gnu.org
2015-04-06 9:43 ` schwab@linux-m68k.org
2015-04-06 9:48 ` mkuvyrkov at gcc dot gnu.org
2015-04-06 9:51 ` doko at gcc dot gnu.org
2015-04-06 22:21 ` wschmidt at gcc dot gnu.org
2015-04-07 4:03 ` adconrad at 0c3 dot net [this message]
2015-04-07 8:47 ` rguenth at gcc dot gnu.org
2015-04-07 13:56 ` wschmidt at gcc dot gnu.org
2015-04-09 7:53 ` jakub at gcc dot gnu.org
2015-04-09 15:31 ` wschmidt at gcc dot gnu.org
2015-04-09 15:42 ` jakub at gcc dot gnu.org
2015-04-09 16:08 ` wschmidt at gcc dot gnu.org
2015-04-10 13:43 ` wschmidt at gcc dot gnu.org
2015-04-14 19:07 ` [Bug target/65670] " doko at gcc dot gnu.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=bug-65670-4-P6jDKp06Qh@http.gcc.gnu.org/bugzilla/ \
--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).