public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/49043] [OpenMP & C++0x]: Compiler error when lambda-function within OpenMP loop
Date: Thu, 19 May 2011 09:16:00 -0000 [thread overview]
Message-ID: <bug-49043-4-qoBAKITjqc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49043-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49043
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2011.05.19 08:55:08
AssignedTo|unassigned at gcc dot |jakub at gcc dot gnu.org
|gnu.org |
Ever Confirmed|0 |1
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-05-19 08:55:08 UTC ---
Created attachment 24287
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24287
gcc46-pr49043.patch
Untested fix.
That said, I'd advise not to use lambdas in OpenMP regions, because the OpenMP
standard doesn't say anything about the data environment of those and how it
should behave. Even the upcoming OpenMP 3.1 doesn't cover C++0x, I hope OpenMP
4.0 will.
next prev parent reply other threads:[~2011-05-19 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 13:48 [Bug c++/49043] New: Returns from lambda functions incorrectly detected as "exits" from OpenMP loops in surrounding code bisqwit at iki dot fi
2011-05-19 8:30 ` [Bug c++/49043] [OpenMP & C++0x]: Compiler error when lambda-function within OpenMP loop bisqwit at iki dot fi
2011-05-19 9:03 ` bisqwit at iki dot fi
2011-05-19 9:16 ` jakub at gcc dot gnu.org [this message]
2011-05-19 13:30 ` jakub at gcc dot gnu.org
2011-05-19 14:10 ` jakub at gcc dot gnu.org
2011-05-19 14:29 ` jakub at gcc dot gnu.org
2011-07-25 9:54 ` jakub at gcc dot gnu.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-49043-4-qoBAKITjqc@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).