egcs-1.0.1 on Solaris, HP, and OSF/1

dave madden dhm@paradigm.webvision.com
Wed Feb 4 17:46:00 GMT 1998


Hi.

I've recently upgraded to gcc-2.8.0 and egcs-1.0.1 on my various
systems, but a large project I've been maintaining with gcc-2.7.2.2 no
longer compiles except on Solaris.  (HP-UX 10.20 and OSF/1 4.0B
complain in similar -- or perhaps identical -- areas; I'm still trying
to figure out what's going on.)

Anyway, I'm getting warnings detected in stl_list.h, stl_alloc.h,
stl_construct.h, and stl_tree.h about variables that might be used
uninitialized, or clobbered by vfork or longjmp:

    /usr/local/packages/egcs-1.0.1/include/g++/stl_list.h:155: warning: `struct __list_node<const char *> * p' might be used uninitialized in this function

I notice __STL_TRY() and __STL_UNWIND() macros (I presume) near many
of the warnings, and I'm guessing that the warnings are related to
exception handling being implemented differently/not-at-all on HP and
OSF/1.

Would this guess be close to the truth?  Is there a way to get lowest-
common-denominator behavior out of gcc-2.8.0 & egcs-1.0.1 so that my
code will compile & work the same on all my platforms?  (I haven't
used exceptions in my code yet because GCC hasn't supported them until
recently, but I do use STL containers & etc quite a bit.)

Regards,
d.



More information about the Gcc mailing list