public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jos dot de_laender at telenet dot be" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/42616] New: OMP'ed loop inside pthread leads to crash.
Date: Mon, 04 Jan 2010 19:58:00 -0000 [thread overview]
Message-ID: <bug-42616-18629@http.gcc.gnu.org/bugzilla/> (raw)
A trivial program with an OMP'ed loop *inside* a pthread does crash at
libgomp.h:380 where gomp_thread()->task becomes NULL->task.
mingw32 on xp is (with my installation) an installation where TLS (thread local
storage) is inop. Hence the pthread_get_specific() and family are used. I
suspect there to be a problem.
--
Summary: OMP'ed loop inside pthread leads to crash.
Product: gcc
Version: 4.4.2
Status: UNCONFIRMED
Severity: blocker
Priority: P3
Component: libgomp
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jos dot de_laender at telenet dot be
GCC build triplet: mingw32 on xp
GCC host triplet: mingw32 on xp
GCC target triplet: mingw32 on xp
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42616
next reply other threads:[~2010-01-04 19:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 19:58 jos dot de_laender at telenet dot be [this message]
2010-01-04 20:01 ` [Bug libgomp/42616] " jos dot de_laender at telenet dot be
2010-01-04 20:03 ` jos dot de_laender at telenet dot be
2010-01-20 22:42 ` zlogic at gmail dot com
2010-01-21 20:07 ` zlogic at gmail dot com
2010-01-22 18:24 ` jos dot de_laender at telenet dot be
2010-06-20 14:55 ` zlogic at gmail dot com
2010-06-20 21:25 ` manu 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-42616-18629@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: 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).