public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/26943] New: [gomp] firstprivate not working properly with non-POD
Date: Thu, 30 Mar 2006 15:55:00 -0000 [thread overview]
Message-ID: <bug-26943-119@http.gcc.gnu.org/bugzilla/> (raw)
Two problems here. The first was trying to show that we don't necessarily
honor
the requirement that all firstprivate copies are executed before the
lastprivate
assignment happens. The second is that we're not properly substituting for the
global X here within the scope of the privatization.
--
Summary: [gomp] firstprivate not working properly with non-POD
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Keywords: wrong-code, openmp
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rth at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26943
next reply other threads:[~2006-03-30 15:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 15:55 rth at gcc dot gnu dot org [this message]
2006-03-30 15:56 ` [Bug c++/26943] " rth at gcc dot gnu dot org
2006-04-28 15:07 ` jakub at gcc dot gnu dot org
2006-04-29 4:55 ` dnovillo at gcc dot gnu dot org
2006-05-01 12:39 ` dnovillo at gcc dot gnu dot org
2006-05-01 15:15 ` dnovillo at gcc dot gnu dot org
2006-05-01 16:08 ` jakub at gcc dot gnu dot org
2006-05-01 16:11 ` dnovillo at redhat dot com
2006-05-01 17:58 ` rth at gcc dot gnu dot org
2006-05-02 20:03 ` jakub at gcc dot gnu dot org
2006-05-03 12:23 ` jakub at gcc dot gnu dot org
2006-05-03 12:31 ` jakub at gcc dot gnu dot org
2006-12-05 2:07 ` bergner at vnet dot ibm dot com
2006-12-11 0:37 ` pinskia at gcc dot gnu dot org
2007-03-21 15:43 ` [Bug c++/26943] [gomp] firstprivate + lastprivate uses inefficient barrier rth at gcc dot gnu dot org
2009-09-14 20:39 ` rth 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-26943-119@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).