🚀 go-pugleaf

The following output of 'nm' may shed some light on a problem I've had
with static constructors inside libraries which I posted earlier.  The
class "dummy_class" has a constructor which computes 
pi = 4 * arctan(1), and "dummy_initialize" is a static object of type
"dummy_class".  Any source module which uses pi includes a header
file containing the line

extern dummy_class dummy_initialize

----------------

dummy.o (g++/Sun):
00000040 T __GLOBAL_$I$dummy_initialize
00000000 T ___14dummy_class
         U _atan
00000060 D _dummy_initialize
00000008 C _pi
00000000 t gcc2_compiled.

dummy.o (g++/DECstation):
00000000 N $L1
00000000 N $L2
00000000 N $L3
00000064 T _GLOBAL_$I$dummy_initialize
00000000 T __14dummy_class
         U atan
00000000 N gcc2_compiled.
000000a0 G dummy_initialize
00000008 C pi

If dummy.o is linked directly to other modules, then the constructor
is called at run time and pi gets its correct value.  If dummy.o is
instead linked in from a library, then the DEC executable calls the
constructor, but the Sun executable does not, leaving pi=0.  Is
"dummy_initialize" for the Sun being put in the wrong segment?

Brad Keister
Department of Physics
Carnegie Mellon University
Pittsburgh, PA 15213
(412) 268-2772 (office)
(412) 681-0648 (FAX)

internet:	keister@poincare.phys.cmu.edu
BITNET:		keister%poincare.phys.cmu.edu@CARNEGIE