public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Al Niessner <Al_Niessner@bigfoot.com>
To: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: gcc symbol names
Date: Sun, 27 Feb 2000 12:17:00 -0000	[thread overview]
Message-ID: <38B98706.F7E6C0B@bigfoot.com> (raw)
In-Reply-To: <200002271918.UAA01018@loewis.home.cs.tu-berlin.de>

Target is the powerpc-wrs-vxworks.

Original names were generated using the VxWorks cross compiler (Tornado II)
on the Sun Solaris platform. The new names are being generated using egcs
1.1.2 cross compiler built for VxWorks on the Linux platform.

On Solaris platform:
> gcc --version
    cygnus-2.7.2-960126 egcs-971225 tornado 2.0

On Linux platform:
> gcc --version
    egcs-2.91.66

There are literally hundreds of these names that could be substituted for
'blahblahblah', I was just trying to reduce the scope, but here are a few
samples if you want real names (they were obtained by doing a diff on the nm
output from the .a files generated by compiling then using ar -- < is Linux
and > is Solaris):

< _._10tRTCObject
< _._11tBaseObject
< _._15TAO_ServantBase
< _._23TAO_RefCountServantBase
< _._23tDmc1308ControllerBoard
< _._5tPing
< _._Q211POA_RTCCore9RTCObject
< _._Q214POA_PingModule10PingObject
< _._Q215POA_RTCHardware5Board
< _._Q217POA_Dmc1308Module17Dmc1308Controller
---
> _$_10tRTCObject
> _$_11tBaseObject
> _$_15TAO_ServantBase
> _$_23TAO_RefCountServantBase
> _$_23tDmc1308ControllerBoard
> _$_5tPing
> _$_Q211POA_RTCCore9RTCObject
> _$_Q214POA_PingModule10PingObject
> _$_Q215POA_RTCHardware5Board
> _$_Q217POA_Dmc1308Module17Dmc1308Controller

and some more

1750,1762c384,396
< _vt.13CORBA_MARSHAL
< _vt.13CORBA_UNKNOWN
< _vt.16TAO_Object_Field
< _vt.26TAO_GIOP_Twoway_Invocation
< _vt.Q210PingModule10PingObject
< _vt.Q210PingModule10PingObject.12CORBA_Object
< _vt.Q211RTCHardware5Board
< _vt.Q211RTCHardware5Board.12CORBA_Object
< _vt.Q213Dmc1308Module17Dmc1308Controller
< _vt.Q213Dmc1308Module17Dmc1308Controller.12CORBA_Object
< _vt.Q27RTCCore9RTCObject
< _vt.Q27RTCCore9RTCObject.12CORBA_Object
<
_vt.t18TAO_Object_Field_T2ZQ213Dmc1308Module17Dmc1308ControllerZQ213Dmc1308Module21Dmc1308Controller_var

---
> _vt$13CORBA_MARSHAL
> _vt$13CORBA_UNKNOWN
> _vt$16TAO_Object_Field
> _vt$26TAO_GIOP_Twoway_Invocation
> _vt$Q210PingModule10PingObject
> _vt$Q210PingModule10PingObject$12CORBA_Object
> _vt$Q211RTCHardware5Board
> _vt$Q211RTCHardware5Board$12CORBA_Object
> _vt$Q213Dmc1308Module17Dmc1308Controller
> _vt$Q213Dmc1308Module17Dmc1308Controller$12CORBA_Object
> _vt$Q27RTCCore9RTCObject
> _vt$Q27RTCCore9RTCObject$12CORBA_Object
>
_vt$t18TAO_Object_Field_T2ZQ213Dmc1308Module17Dmc1308ControllerZQ213Dmc1308Module21Dmc1308Controller_var




It really does reduce to a '.' for '$' substitution.

All and any help is appreciated.

Al Niessner

"Martin v. Loewis" wrote:

> > I built the egcs 1.1.2 compiler and am now having symbol name problems.
> > I have some old libraries that use a different naming scheme and I would
> > ike to know how to make the new gcc match the old gcc names.  The
> > difference is quite simple.  Using nm:
> >
> > old name: _$_blahblahblah
> > new name: _._blahblahblah
> >
> > How do I get the gcc I compiled to use '$' instead of '.'?
> >
> > Any and all help is appreciated.
>
> You'll have to give us some more details that that. What target system
> are you using? What is the exact spelling of the symbol? I very much
> doubt that it is '_._blahblahblah', because it looks like a C++
> destructor name, but that it would have to be '_._12blahblahblah'.
> There might be a very good reason for the change in the mangling; or
> it might be configuration problem.
>
> Regards,
> Martin

WARNING: multiple messages have this Message-ID
From: Al Niessner <Al_Niessner@bigfoot.com>
To: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: gcc symbol names
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <38B98706.F7E6C0B@bigfoot.com> (raw)
Message-ID: <20000401000000.eGa8eWL9wVtucH2u3lrUkImAeOPTuh1EHYaPL7MbOSw@z> (raw)
In-Reply-To: <200002271918.UAA01018@loewis.home.cs.tu-berlin.de>

Target is the powerpc-wrs-vxworks.

Original names were generated using the VxWorks cross compiler (Tornado II)
on the Sun Solaris platform. The new names are being generated using egcs
1.1.2 cross compiler built for VxWorks on the Linux platform.

On Solaris platform:
> gcc --version
    cygnus-2.7.2-960126 egcs-971225 tornado 2.0

On Linux platform:
> gcc --version
    egcs-2.91.66

There are literally hundreds of these names that could be substituted for
'blahblahblah', I was just trying to reduce the scope, but here are a few
samples if you want real names (they were obtained by doing a diff on the nm
output from the .a files generated by compiling then using ar -- < is Linux
and > is Solaris):

< _._10tRTCObject
< _._11tBaseObject
< _._15TAO_ServantBase
< _._23TAO_RefCountServantBase
< _._23tDmc1308ControllerBoard
< _._5tPing
< _._Q211POA_RTCCore9RTCObject
< _._Q214POA_PingModule10PingObject
< _._Q215POA_RTCHardware5Board
< _._Q217POA_Dmc1308Module17Dmc1308Controller
---
> _$_10tRTCObject
> _$_11tBaseObject
> _$_15TAO_ServantBase
> _$_23TAO_RefCountServantBase
> _$_23tDmc1308ControllerBoard
> _$_5tPing
> _$_Q211POA_RTCCore9RTCObject
> _$_Q214POA_PingModule10PingObject
> _$_Q215POA_RTCHardware5Board
> _$_Q217POA_Dmc1308Module17Dmc1308Controller

and some more

1750,1762c384,396
< _vt.13CORBA_MARSHAL
< _vt.13CORBA_UNKNOWN
< _vt.16TAO_Object_Field
< _vt.26TAO_GIOP_Twoway_Invocation
< _vt.Q210PingModule10PingObject
< _vt.Q210PingModule10PingObject.12CORBA_Object
< _vt.Q211RTCHardware5Board
< _vt.Q211RTCHardware5Board.12CORBA_Object
< _vt.Q213Dmc1308Module17Dmc1308Controller
< _vt.Q213Dmc1308Module17Dmc1308Controller.12CORBA_Object
< _vt.Q27RTCCore9RTCObject
< _vt.Q27RTCCore9RTCObject.12CORBA_Object
<
_vt.t18TAO_Object_Field_T2ZQ213Dmc1308Module17Dmc1308ControllerZQ213Dmc1308Module21Dmc1308Controller_var

---
> _vt$13CORBA_MARSHAL
> _vt$13CORBA_UNKNOWN
> _vt$16TAO_Object_Field
> _vt$26TAO_GIOP_Twoway_Invocation
> _vt$Q210PingModule10PingObject
> _vt$Q210PingModule10PingObject$12CORBA_Object
> _vt$Q211RTCHardware5Board
> _vt$Q211RTCHardware5Board$12CORBA_Object
> _vt$Q213Dmc1308Module17Dmc1308Controller
> _vt$Q213Dmc1308Module17Dmc1308Controller$12CORBA_Object
> _vt$Q27RTCCore9RTCObject
> _vt$Q27RTCCore9RTCObject$12CORBA_Object
>
_vt$t18TAO_Object_Field_T2ZQ213Dmc1308Module17Dmc1308ControllerZQ213Dmc1308Module21Dmc1308Controller_var




It really does reduce to a '.' for '$' substitution.

All and any help is appreciated.

Al Niessner

"Martin v. Loewis" wrote:

> > I built the egcs 1.1.2 compiler and am now having symbol name problems.
> > I have some old libraries that use a different naming scheme and I would
> > ike to know how to make the new gcc match the old gcc names.  The
> > difference is quite simple.  Using nm:
> >
> > old name: _$_blahblahblah
> > new name: _._blahblahblah
> >
> > How do I get the gcc I compiled to use '$' instead of '.'?
> >
> > Any and all help is appreciated.
>
> You'll have to give us some more details that that. What target system
> are you using? What is the exact spelling of the symbol? I very much
> doubt that it is '_._blahblahblah', because it looks like a C++
> destructor name, but that it would have to be '_._12blahblahblah'.
> There might be a very good reason for the change in the mangling; or
> it might be configuration problem.
>
> Regards,
> Martin

  reply	other threads:[~2000-02-27 12:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-26 20:29 Al Niessner
2000-02-27 11:21 ` Martin v. Loewis
2000-02-27 12:17   ` Al Niessner [this message]
2000-02-27 12:58     ` Martin v. Loewis
2000-02-27 18:51       ` Al Niessner
2000-02-28  1:32         ` Martin v. Loewis
2000-04-01  0:00           ` Martin v. Loewis
2000-04-01  0:00         ` Al Niessner
2000-04-01  0:00       ` Martin v. Loewis
2000-04-01  0:00     ` Al Niessner
2000-04-01  0:00   ` Martin v. Loewis
2000-04-01  0:00 ` Al Niessner
2000-02-29 20:05 Al Niessner
2000-03-01  1:18 ` Martin v. Loewis
2000-03-01 19:26   ` Al Niessner
2000-03-02  1:18     ` Martin v. Loewis
2000-04-01  0:00       ` Martin v. Loewis
2000-04-01  0:00     ` Al Niessner
2000-04-01  0:00   ` Martin v. Loewis
2000-04-01  0:00 ` Al Niessner

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=38B98706.F7E6C0B@bigfoot.com \
    --to=al_niessner@bigfoot.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=martin@loewis.home.cs.tu-berlin.de \
    /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).