From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeffrey A Law To: Marc Girod Cc: egcs@egcs.cygnus.com Subject: Re: egcs 1.1.2 vs. HP/UX 10.20 Date: Sun, 23 May 1999 23:36:00 -0000 Message-id: <13348.927527478@upchuck.cygnus.com> References: <1yvheq5uwc.fsf@mahtan.ntc.nokia.com> X-SW-Source: 1999-05/msg00655.html In message <1yvheq5uwc.fsf@mahtan.ntc.nokia.com>you write: > >>>>> "JL" == Jeffrey A Law writes: > > JL> Yes. They are referenced by the MT thread safe exception handling > JL> code. > > Er... There are 2 versions of libgcc.a in the build directory: one in > the gcc directory, the other in the gcc/threads one. > > Now, both versions reference the symbols. Is this intended? I do not know. You would have to ask the C++ and Java folks since they are the ones that have libraries that need to be aware of the system's underlying thread model. > If it is intended, then libdce is needed. The question can only be: > "archive or shared library?". > > If one is making an archive libgcc.a, one can extract the symbols from > libdce.a into it in the same way as for the other symbols: > > - make a tmp directory > - extract the symbols from libdce.a > - append the to libgcc.a > - clean up > > The resulting lib will be bigger. Worse, how do you describe these steps in a general manner? How do you deal with cross compilers? Sucking in parts of a system library into libgcc is a bad thing to be doing. jeff From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeffrey A Law To: Marc Girod Cc: egcs@egcs.cygnus.com Subject: Re: egcs 1.1.2 vs. HP/UX 10.20 Date: Mon, 31 May 1999 21:36:00 -0000 Message-ID: <13348.927527478@upchuck.cygnus.com> References: <1yvheq5uwc.fsf@mahtan.ntc.nokia.com> X-SW-Source: 1999-05n/msg00656.html Message-ID: <19990531213600.VauOctJD1tLx-v_GW7Tebc5wmsi_WBsFhSPz_s9wfZc@z> In message <1yvheq5uwc.fsf@mahtan.ntc.nokia.com>you write: > >>>>> "JL" == Jeffrey A Law writes: > > JL> Yes. They are referenced by the MT thread safe exception handling > JL> code. > > Er... There are 2 versions of libgcc.a in the build directory: one in > the gcc directory, the other in the gcc/threads one. > > Now, both versions reference the symbols. Is this intended? I do not know. You would have to ask the C++ and Java folks since they are the ones that have libraries that need to be aware of the system's underlying thread model. > If it is intended, then libdce is needed. The question can only be: > "archive or shared library?". > > If one is making an archive libgcc.a, one can extract the symbols from > libdce.a into it in the same way as for the other symbols: > > - make a tmp directory > - extract the symbols from libdce.a > - append the to libgcc.a > - clean up > > The resulting lib will be bigger. Worse, how do you describe these steps in a general manner? How do you deal with cross compilers? Sucking in parts of a system library into libgcc is a bad thing to be doing. jeff