public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hainque at adacore dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug boehm-gc/34544] pthread_default_stacksize_np failed.
Date: Fri, 13 Aug 2010 10:14:00 -0000	[thread overview]
Message-ID: <20100813101443.8286.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34544-276@http.gcc.gnu.org/bugzilla/>



------- Comment #16 from hainque at adacore dot com  2010-08-13 10:14 -------
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".

 That's probably settled by now :)

 We're discussing the options internally. Thanks much for your
 feedback.

 Olivier





-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34544


  parent reply	other threads:[~2010-08-13 10:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21  2:54 [Bug boehm-gc/34544] New: " danglin at gcc dot gnu dot org
2009-04-30 19:47 ` [Bug boehm-gc/34544] " danglin at gcc dot gnu dot org
2010-07-27 21:56 ` danglin at gcc dot gnu dot org
2010-08-08 15:05 ` danglin at gcc dot gnu dot org
2010-08-08 15:08 ` danglin at gcc dot gnu dot org
2010-08-08 15:11 ` danglin at gcc dot gnu dot org
2010-08-08 15:17 ` danglin at gcc dot gnu dot org
2010-08-10 15:24 ` danglin at gcc dot gnu dot org
2010-08-12  9:42 ` hainque at gcc dot gnu dot org
2010-08-12 13:38 ` dave at hiauly1 dot hia dot nrc dot ca
2010-08-12 14:05 ` dave at hiauly1 dot hia dot nrc dot ca
2010-08-12 14:14 ` hainque at adacore dot com
2010-08-12 14:18 ` hainque at adacore dot com
2010-08-12 14:24 ` hainque at adacore dot com
2010-08-12 15:04 ` dave at hiauly1 dot hia dot nrc dot ca
2010-08-12 23:26 ` dave at hiauly1 dot hia dot nrc dot ca
2010-08-13 10:14 ` hainque at adacore dot com [this message]
2010-08-13 13:19 ` dave at hiauly1 dot hia dot nrc dot ca
2010-08-14 14:37 ` danglin at gcc dot gnu dot org
2010-08-14 14:43 ` danglin at gcc dot gnu dot org
2010-08-14 14:45 ` danglin at gcc dot gnu dot org
2010-08-16  7:43 ` hainque at adacore dot com
2010-08-22 16:24 ` danglin at gcc dot gnu dot org
     [not found] <bug-34544-4@http.gcc.gnu.org/bugzilla/>
2011-01-29 22:16 ` danglin at gcc dot gnu.org
2011-02-11  6:20 ` danglin at gcc dot gnu.org
2011-02-27  8:13 ` danglin at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100813101443.8286.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).