public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/27388] New: omp_is_private issues Date: Tue, 02 May 2006 14:19:00 -0000 [thread overview] Message-ID: <bug-27388-87@http.gcc.gnu.org/bugzilla/> (raw) void foo (void) { int i; i = 0; #pragma omp parallel shared (i) { #pragma omp master i++; #pragma omp parallel for for (i = 0; i < 10; i++) ; } } results in very weird omplower dump: 1) #pragma omp parallel shared(iD.1922) private(iD.1922) for the outer parallel (surely we don't want i being shared and private at the same time, just shared here) 2) #pragma omp parallel shared(iD.1922) for the inner parallel - in this case i certainly ought to be private, not shared I think 1) is caused by n->value = GOVD_PRIVATE; messing up outer context, while 2) probably because omp_is_private shouldn't recurse over is_parallel contexts. -- Summary: omp_is_private issues Product: gcc Version: 4.2.0 Status: UNCONFIRMED Keywords: openmp Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jakub at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27388
next reply other threads:[~2006-05-02 14:19 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-02 14:19 jakub at gcc dot gnu dot org [this message] 2006-05-02 14:38 ` [Bug middle-end/27388] " jakub at gcc dot gnu dot org 2006-05-02 22:43 ` rth at gcc dot gnu dot org 2006-05-03 1:45 ` rth at gcc dot gnu dot org 2006-05-04 6:34 ` jakub at gcc dot gnu dot org 2006-05-04 9:34 ` jakub 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-27388-87@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).