symbol incompatibility

Thread View: gnu.g++

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Rich Johns Tue, 01 Aug 1989 21:57

#75

Author: Rich Johns
Date: Tue, 01 Aug 1989 21:57

26 lines
1291 bytes

I have just upgraded from g++ 1.32 to g++ 1.35.1. I was hoping only to
have to recompile my application. It turns out g++ 1.32 generates the
following symbol for a method involving a boolean arg:

   _DoInsert_PSWorld_PSInteractor_Eboolean_SI_SI

whereas g++ 1.35.1 generates the followiwng for the same method:

   _DoInsert_PSWorld_PSInteractor_E$_0_SI_SI

This means that all libraries, previously compiled with g++ 1.32
that my application(s) links with, must also be recompiled, otherwise
I get a lot of undefined symbols :-(

Just out of curiosity, how much benefit is derived from switching the
way booleans are represented?





I have just discovered that I must recompile all the libraries
originally compiled with g++ 1.32
Rich Johns, MCC CAD Program | 3500 W. Balcones Center Dr., Austin, TX 78759
ARPA: johns@mcc.com         | Phone: [512] 338-3714
UUCP: {uunet,harvard,gatech,pyramid}!cs.utexas.edu!milano!cadillac!johns

symbol incompatibility

#78

Author: Michael Tiemann
Date: Wed, 02 Aug 1989 17:50

14 lines
918 bytes

    I have just upgraded from g++ 1.32 to g++ 1.35.1. I was hoping only to
    have to recompile my application. It turns out g++ 1.32 generates the
    following symbol for a method involving a boolean arg:

       _DoInsert_PSWorld_PSInteractor_Eboolean_SI_SI

    whereas g++ 1.35.1 generates the followiwng for the same method:

       _DoInsert_PSWorld_PSInteractor_E$_0_SI_SI

This is a bug.  It will be fixed in 1.36.0.

Michael

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads