From: Martin Lambers <marlam@marlam.de>
To: pthreads-win32@sourceware.org, ross.johnson@homemail.com.au
Subject: Pthreads-win32 and static linking
Date: Mon, 10 May 2010 19:50:00 -0000 [thread overview]
Message-ID: <20100510195037.GA7348@lambers.home> (raw)
Hello!
The Mingw-cross-env project provides a MinGW cross-compiling environment
for POSIX systems. For various reasons, all included libraries are
static, including the pthreads-win32 library.
This means that all pthreads users need to call
pthread_win32_thread_attach_np() and pthread_win32_thread_detach_np() in
each thread function.
We would like to avoid patching all libraries that use pthread, and
instead change pthreads-win32: instead of using a thread main function
given to pthread_create() directly, pthreads-win32 could use an internal
wrapper that calls the thread main function and also calls the
attach/detach functions if necessary.
To avoid the pthread_win32_process_attach() function, pthreads-win32
could check on each function call whether the library was initialized,
and if not, call pthread_win32_process_attach() itself.
This would induce some overhead, but would allow us to use a large
number of existing libraries unchanged.
Before we start to work on a patch, we would like to know if this
approach has a chance to work. Do you know any technical reasons why
this might fail?
Best regards,
Martin
next reply other threads:[~2010-05-10 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 19:50 Martin Lambers [this message]
2010-05-10 20:03 ` Ramiro Polla
2010-06-20 5:15 ` Ross Johnson
2010-07-23 12:09 ` John E. Bossom
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=20100510195037.GA7348@lambers.home \
--to=marlam@marlam.de \
--cc=pthreads-win32@sourceware.org \
--cc=ross.johnson@homemail.com.au \
/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).