Bug 28353 - binutils-2.10.91.0.2-1 does not support GCC 3.0 ABI
Summary: binutils-2.10.91.0.2-1 does not support GCC 3.0 ABI
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: binutils
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords: FutureFeature
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-02-19 22:40 UTC by rodrigc
Modified: 2007-04-18 16:31 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2001-02-20 00:29:26 UTC


Attachments (Terms of Use)

Description Red Hat Bugzilla 2001-02-19 22:40:05 UTC
Hi,

binutils-2.10.91.0.2-1 does not support the GCC 3.0 ABI.
Therefore,  nm -C will not correctly demangle symbols
compiled with GCC 3.0.

Comment 1 Red Hat Bugzilla 2001-02-19 23:47:15 UTC
I cannot duplicate the problem. "nm -C" works fine on libstdc++.so downloaded
from

http://www.codesourcery.com/gcc-snapshots/

Please provide a C++ binary to show the problem.

BTW, I am using nm in binutils 2.10.92.0.2 built from
the tar file.

Comment 2 Red Hat Bugzilla 2001-02-20 00:25:09 UTC
OK, I reported the bug wrong.
binutils-2.10.1.0.2, which is in the Fisher beta, does not demangle GCC 3.0
symbols.

However, I checked out:b
ftp://ftp.valinux.com/pub/support/hjl/binutils/binutils-2.10.91.0.2-1.i386.rpm

and this version DOES demangle GCC 3.0 symbols, and it also
demangles "old-style" GCC 2.xx C++ symbols.

Will HJL's version of binutils make it into Redhat 7.1?

Close this bug.


Comment 3 Red Hat Bugzilla 2001-02-20 00:29:22 UTC
binutils-2.10.1.0.2 doesn't support gcc 3.0.
I don't see why binutils-2.10.91.0.2 or newer
won't be in RedHat 7.1.

Comment 4 Red Hat Bugzilla 2001-02-20 08:01:35 UTC
I want to apologize to H.J., seems like I typed nm -C in a wrong window
on a machine which had not binutils upgraded (and then checked CVS binutils
and it worked).
binutils-2.10.91.0.2-1 or newer will be in Red Hat Linux 7.1.


Note You need to log in before you can comment on or make changes to this bug.