g++-mike-eh8-C test failure

Jason Merrill jason@cygnus.com
Tue May 2 18:44:00 GMT 2000

>>>>> John David Anglin <dave@hiauly1.hia.nrc.ca> writes:

 > But if the shared library is complete, we may end up with duplicate code
 > for __muldi3 and lose anyway.  The HP linker is apparently too dumb to
 > detect this duplication and I have to wonder if shl_load would do much
 > better.

Yes, that's why we want to make libgcc its own shared library, so that
there's only one copy.

 > Do we really need libstdc++ to work with dlopen/shl_load?

Yes.  The folks that initially paid us to make shared libraries work rely
on that functionality.

 >> 4. Build a shared libgcc and have it referenced by either the main
 >> program or the library.  Which is precisely what we're discussing in
 >> another thread.

 > Building a shared libgcc is a good idea on its own.  However, it might
 > not resolve this problem.  There still might be duplication of procedures
 > and problems with libraries that don't have a shared implementation.

Why would there be duplication?


More information about the Gcc-bugs mailing list