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] [gomp] firstprivate + lastprivate uses inefficient barrier Date: Mon, 14 Sep 2009 20:39:00 -0000 [thread overview] Message-ID: <20090914203912.24827.qmail@sourceware.org> (raw) In-Reply-To: <bug-26943-119@http.gcc.gnu.org/bugzilla/> -- rth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|rth at gcc dot gnu dot org |unassigned at gcc dot gnu | |dot org Status|ASSIGNED |NEW http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26943
prev parent reply other threads:[~2009-09-14 20:39 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-03-30 15:55 [Bug c++/26943] New: [gomp] firstprivate not working properly with non-POD rth at gcc dot gnu dot org 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 [this message]
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=20090914203912.24827.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: 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).