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 libgomp/59467] copyprivate in the fortran testsuite Date: Thu, 12 Dec 2013 08:57:00 -0000 [thread overview] Message-ID: <bug-59467-4-wsEf7VGbh8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59467-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59467 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Author: jakub Date: Thu Dec 12 08:57:22 2013 New Revision: 205923 URL: http://gcc.gnu.org/viewcvs?rev=205923&root=gcc&view=rev Log: PR libgomp/59467 * gimplify.c (omp_check_private): Add copyprivate argument, if it is true, don't check omp_privatize_by_reference. (gimplify_scan_omp_clauses): For OMP_CLAUSE_COPYPRIVATE verify decl is private in outer context. Adjust omp_check_private caller. * gfortran.dg/gomp/pr59467.f90: New test. * c-c++-common/gomp/pr59467.c: New test. * testsuite/libgomp.fortran/crayptr2.f90: Add private (d) clause to !$omp parallel. Added: branches/gcc-4_8-branch/gcc/testsuite/c-c++-common/gomp/pr59467.c branches/gcc-4_8-branch/gcc/testsuite/gfortran.dg/gomp/pr59467.f90 Modified: branches/gcc-4_8-branch/gcc/ChangeLog branches/gcc-4_8-branch/gcc/gimplify.c branches/gcc-4_8-branch/gcc/testsuite/ChangeLog branches/gcc-4_8-branch/libgomp/ChangeLog branches/gcc-4_8-branch/libgomp/testsuite/libgomp.fortran/crayptr2.f90
next prev parent reply other threads:[~2013-12-12 8:57 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-11 10:24 [Bug libgomp/59467] New: " valeryweber at hotmail dot com 2013-12-12 8:52 ` [Bug libgomp/59467] " jakub at gcc dot gnu.org 2013-12-12 8:57 ` jakub at gcc dot gnu.org [this message] 2013-12-12 10:11 ` 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-59467-4-wsEf7VGbh8@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).