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 fortran/49792] OpenMP workshare: Wrong result with array assignment Date: Fri, 19 Aug 2011 13:32:00 -0000 [thread overview] Message-ID: <bug-49792-4-NlbjJt0oMt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49792-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49792 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-08-19 13:26:54 UTC --- Author: jakub Date: Fri Aug 19 13:26:50 2011 New Revision: 177900 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=177900 Log: PR fortran/49792 * trans-expr.c (gfc_trans_assignment_1): Set OMPWS_SCALARIZER_WS bit in ompws_flags only if loop.temp_ss is NULL, and clear it if lhs needs reallocation. * trans-openmp.c (gfc_trans_omp_workshare): Don't return early if code is NULL, emit a barrier if workshare emitted no code at all and NOWAIT clause isn't present. * testsuite/libgomp.fortran/pr49792-1.f90: New test. * testsuite/libgomp.fortran/pr49792-2.f90: New test. Added: branches/gcc-4_6-branch/libgomp/testsuite/libgomp.fortran/pr49792-1.f90 branches/gcc-4_6-branch/libgomp/testsuite/libgomp.fortran/pr49792-2.f90 Modified: branches/gcc-4_6-branch/gcc/fortran/ChangeLog branches/gcc-4_6-branch/gcc/fortran/trans-expr.c branches/gcc-4_6-branch/gcc/fortran/trans-openmp.c branches/gcc-4_6-branch/libgomp/ChangeLog
next prev parent reply other threads:[~2011-08-19 13:27 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-20 9:50 [Bug fortran/49792] New: " burnus at gcc dot gnu.org 2011-08-19 13:27 ` [Bug fortran/49792] " jakub at gcc dot gnu.org 2011-08-19 13:32 ` jakub at gcc dot gnu.org [this message] 2011-08-19 13:37 ` jakub at gcc dot gnu.org 2015-10-29 14:47 ` dominiq at lps dot ens.fr
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-49792-4-NlbjJt0oMt@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).