From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26729 invoked by alias); 13 Aug 2010 13:19:05 -0000 Received: (qmail 24592 invoked by alias); 13 Aug 2010 13:18:42 -0000 Date: Fri, 13 Aug 2010 13:19:00 -0000 Message-ID: <20100813131842.24591.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug boehm-gc/34544] pthread_default_stacksize_np failed. In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dave at hiauly1 dot hia dot nrc dot ca" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-08/txt/msg01104.txt.bz2 ------- Comment #17 from dave at hiauly1 dot hia dot nrc dot ca 2010-08-13 13:18 ------- Subject: Re: pthread_default_stacksize_np failed. > dave at hiauly1 dot hia dot nrc dot ca wrote: > > I think the answer is to provide a stub for pthread_default_stacksize_np > > which is linked in last in final executables. I believe the function is > > always present in the pthread libraries, both shared and archive. We > > already do similar things for a number of functions on hppa64-hpux11. > > Hmm, certainly worth an attempt. We were caught by subtle bugs with > similar attempts on other platforms in the past, like "stub added to > lib X, and corner case situation Bla leads to a link order that gets > us the stub instead of the real implementation in multi threaded apps". Same here. libtool isn't perfect and it links libc into shared libraries against the recommendation of HP. So, in applications with many libraries, it is not clear whether the dynamic loader will bind the real pthread functions or the stubs. The search rules are different for 32 and 64-bit hpux. The stub for pthread_default_stacksize_np would be in a archive library. The link option would essentially be the last item in the link command generated by the gcc driver. The stub will only be linked in if the symbol isn't resolved by one of the preceeding libraries. So, the above issue can't happen. > That's probably settled by now :) Well no ... > We're discussing the options internally. Thanks much for your > feedback. Because of these issues, I have decided to revert the change on the branches (probably tomorrow). I will also try to add the stub on the trunk. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34544