public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug boehm-gc/34544] pthread_default_stacksize_np failed. Date: Fri, 11 Feb 2011 06:20:00 -0000 [thread overview] Message-ID: <bug-34544-4-ne7NsMS2p7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-34544-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34544 --- Comment #24 from John David Anglin <danglin at gcc dot gnu.org> 2011-02-11 03:00:57 UTC --- Author: danglin Date: Fri Feb 11 03:00:53 2011 New Revision: 170042 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=170042 Log: Backport from mainline: 2011-02-07 John David Anglin <dave.anglin@nrc-cnrc.gc.ca> * config/pa/pa64-hpux.h (LIB_SPEC): In static links, link against shared libc if not linking against libpthread. * config/pa/pa-hpux11.h (LIB_SPEC): Likewise. 2010-08-22 John David Anglin <dave.anglin@nrc-cnrc.gc.ca> PR boehm-gc/34544 * gthr-posix.h (__gthread_active_init): Delete. (__gthread_active_p): Do activity check here. Don't include errno.h on hppa-hpux. Update comment. * gthr-posix95.h (__gthread_active_init): Delete. (__gthread_active_p): Do activity check here. Don't include errno.h on hppa-hpux. Update comment. Modified: branches/gcc-4_4-branch/gcc/ChangeLog branches/gcc-4_4-branch/gcc/config/pa/pa-hpux11.h branches/gcc-4_4-branch/gcc/config/pa/pa64-hpux.h branches/gcc-4_4-branch/gcc/gthr-posix.h branches/gcc-4_4-branch/gcc/gthr-posix95.h
next prev parent reply other threads:[~2011-02-11 3:01 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top [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 [this message] 2011-02-27 8:13 ` danglin at gcc dot gnu.org 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 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
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-34544-4-ne7NsMS2p7@http.gcc.gnu.org/bugzilla/ \ --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: 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).