Re: egcs 1.1.2 vs. HP/UX 10.20

[Jeffrey A Law <law@upchuck.cygnus.com>]

  In message < 1yaevlotru.fsf@anvil.ntc.nokia.com >you write:
  > The dce symbols come (at least) from the object file _eh.o, archived
  > into libgcc2.a (and from there to libgcc.a).
Yes.  This is what I would expect.

  > It is compiled from gcc/libgcc2.c with the command:
  > 
  > ./xgcc -B./ -B/tools/contrib/HP-UX/B.10.20/hppa2.0/packages/egcs/hppa2.0-hp
  > -hpux10.20/bin/ -O2   -DIN_GCC -DHAIFA    -g -W -Wall -I./include  -fPIC -g
  > 1 -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED   -fexceptions 
  > -I. -I. -I./config -I./../include -c \
  >       -DL${name} ./libgcc2.c -o _eh.o
  > 
  > In file included from gthr-default.h:1,
  >                  from gthr.h:98,
  >                  from ./libgcc2.c:3025:
  > gthr-dce.h: In function `__gthread_key_dtor':
  > gthr-dce.h:95: warning: unused parameter `key'
  > gthr-dce.h:95: warning: unused parameter `ptr'
  > gthr-dce.h: In function `__gthread_key_delete':
  > gthr-dce.h:104: warning: implicit declaration of function `pthread_key_dele
  > te'
  > 
  > Indeed, gthr-default.h includes gthr-dce.h, which #defines __GTHREADS
  > and includes pthread.h...
  > 
  > Isn't it so that one would want to define -DHAVE_GTHR_DEFAULT _only_
  > when building gcc/threads/libgcc.a (_not_ when building gcc/libgcc.a)?
Unsure.  The C++ people would have to chime in.  I don't do C++, threads or
exceptions :-)


  > Also, when debugging a file compiled with egcs on HP-UX 10.20, gdb
  > complains of the following:
  > 
  > warning: Unable to find __d_pid symbol in object file.
  > warning: Suggest linking with /opt/langtools/lib/end.o.
  > warning: GDB will be unable to track shl_load/shl_unload calls
What version of gdb?  Whatever it is it pre-dates support for debugging
dynamic objects on hpux10 and is very old (since I fixed this problem at
least 2 years ago).

Linking in end.o on hpux10 is highly undesirable.  If you attempt to do
so you'll find that your program will not link.

jeff