public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/5780] OpenMP program linked with static libraries gets a runtime memory fault Date: Thu, 06 Sep 2012 23:26:00 -0000 [thread overview] Message-ID: <bug-5780-131-NYJHg9IAaq@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-5780-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=5780 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|DUPLICATE | --- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> 2012-09-06 23:25:45 UTC --- The issue is GCC uses 1. Mark pthread_foo as weak. 2. Use a weak pthread_xxxx to check if thread is active. 3. It does if (pthread_xxxx) pthread_foo (); With libpthread.a, there is no guarantee that linking in archive member for pthread_xxxx will also include archive member for pthread_foo. When it happens, static executable crashes when calling pthread_foo. We can add if (pthread_foo) pthread_foo (); But it may lead to bad static executable hehavior. The list of pthread_foo is pthread_attr_init pthread_attr_setdetachstate pthread_cond_broadcast pthread_cond_destroy pthread_cond_init pthread_cond_signal pthread_cond_wait pthread_create pthread_detach pthread_exit pthread_getschedparam pthread_getspecific pthread_join pthread_key_create pthread_key_delete pthread_mutex_destroy pthread_mutex_init pthread_mutex_lock pthread_mutex_trylock pthread_mutex_unlock pthread_once pthread_self pthread_setschedparam pthread_setspecific pthread_sigmask __pthread_key_create -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next parent reply other threads:[~2012-09-06 23:26 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-5780-131@http.sourceware.org/bugzilla/> 2012-09-06 23:26 ` hjl.tools at gmail dot com [this message] 2012-09-07 0:00 ` hjl.tools at gmail dot com 2014-02-16 18:29 ` jackie.rosen at hushmail dot com 2014-05-28 19:46 ` schwab at sourceware dot org 2014-07-02 7:21 ` fweimer at redhat dot com 2008-02-21 0:04 [Bug nptl/5780] New: " geir at cray dot com 2008-02-21 14:12 ` [Bug nptl/5780] " carlos at codesourcery dot com
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=bug-5780-131-NYJHg9IAaq@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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: linkBe 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).