public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bisqwit at iki dot fi" <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 08:30:00 -0000 [thread overview] Message-ID: <bug-49043-4-z1jevHw3LW@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 --- Comment #2 from Joel Yliluoma <bisqwit at iki dot fi> 2011-05-19 08:10:06 UTC --- Even if the lambda function is not called, it happens. Merely defining the function causes it. Interestingly though, it does not happen if a method body is defined within the loop. The code below does not cause the error. So it is restricted to lambda function bodies. It also does not happen when calling lambda functions that are defined outside the loop. int main() { #pragma omp parallel for for(int a=0; a<10; ++a) { struct tmp { static int test() { return 0; } }; } }
next prev parent reply other threads:[~2011-05-19 8:25 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 ` bisqwit at iki dot fi [this message] 2011-05-19 9:03 ` [Bug c++/49043] [OpenMP & C++0x]: Compiler error when lambda-function within OpenMP loop bisqwit at iki dot fi 2011-05-19 9:16 ` jakub at gcc dot gnu.org 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-z1jevHw3LW@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: 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).