c++/7682: bug on hp making the gcc dump undefined type info name for a class

helmut.haigermoser@windriver.com helmut.haigermoser@windriver.com
Thu Aug 22 09:46:00 GMT 2002


>Number:         7682
>Category:       c++
>Synopsis:       bug on hp making the gcc dump undefined type info name for a class
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Aug 22 08:06:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Helmut J. Haigermoser
>Release:        3.2
>Organization:
>Environment:
HP-UX angband B.11.00 A 9000/782 2012115469
>Description:
The attached example triggers a bug in gcc making it dump the type info name as an undefined symbol into the resulting object file.


In the example the class X shall be compiled and 


the type info and type info name should be in the object-file X.o. 


Gcc fails to create the type info name, however.


After some tests two workarounds could be found:


* comment the "pragma interface" line in Y.h


* comment the member using "vector" of class Y





The attached example also includes the .ii-file which is said to be useful to you...





a complete output of gcc -v reads as follows:





Reading specs from /opt/gcc/3.2/usr/local/bin/../lib/gcc-lib/hppa2.0n-hp-hpux11.00/3.2/specs


Thread model: posix


gcc version 3.2





>How-To-Repeat:
-extract the tarball


-use build.sh to generate X.o andto  check the type info symbols


-I figured that HP-UX-gcc's have problems with type info


 but this is the first test case I could minimize to that level


>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the Gcc-prs mailing list