public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/24071] solaris vs. __gthread_active_p
Date: Sun, 02 Oct 2005 21:28:00 -0000 [thread overview]
Message-ID: <20051002212757.13431.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24071-365@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from ebotcazou at gcc dot gnu dot org 2005-10-02 21:27 -------
> Therefore, I'm suggesting I close this, and open a more general enhancement bug.
I'd rather keep it open and recategorize it as a "target" PR, since there is
really a problem with __gthread_active_p on Solaris because of the
Solaris/POSIX threads duality.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24071
next prev parent reply other threads:[~2005-10-02 21:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-24071-365@http.gcc.gnu.org/bugzilla/>
2005-10-02 21:21 ` mark at codesourcery dot com
2005-10-02 21:28 ` ebotcazou at gcc dot gnu dot org [this message]
2005-10-09 17:57 ` [Bug target/24071] __gthread_active_p vs __gthread_once ebotcazou at gcc dot gnu dot org
2005-12-14 11:47 ` neil at fnxweb dot com
2006-10-28 5:36 ` ebotcazou at gcc dot gnu dot org
2006-10-31 9:34 ` bkoz at gcc dot gnu dot org
2006-10-31 17:55 ` ebotcazou at gcc dot gnu dot org
2006-10-31 17:56 ` ebotcazou at gcc dot gnu dot org
2006-10-31 18:03 ` ebotcazou at gcc dot gnu dot org
2006-11-30 1:23 ` chaoyingfu at gcc dot gnu dot org
2005-09-26 23:22 [Bug libstdc++/24071] New: solaris vs. __gthread_active_p bkoz at gcc dot gnu dot org
2005-09-26 23:22 ` [Bug libstdc++/24071] " bkoz at gcc dot gnu dot org
2005-09-26 23:24 ` bkoz at gcc dot gnu dot org
2005-09-27 0:18 ` bkoz at gcc dot gnu dot org
2005-09-27 7:15 ` ebotcazou at gcc dot gnu dot org
2005-10-01 8:53 ` mmitchel at gcc dot gnu dot org
2005-10-01 9:02 ` ebotcazou at gcc dot gnu dot org
2005-10-01 9:17 ` mmitchel at gcc dot gnu dot org
2005-10-01 18:46 ` bkoz at gcc dot gnu dot org
2005-10-01 18:50 ` bkoz at gcc dot gnu dot org
2005-10-01 19:41 ` pinskia 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=20051002212757.13431.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).