public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/94672] [10/11 Regression] gfortran/OpenMP chokes on PRESENT(array) despite of SHARED(array): Error: ‘array’ not specified in enclosing ‘parallel’
Date: Mon, 11 May 2020 14:40:37 +0000 [thread overview]
Message-ID: <bug-94672-4-CvkDZjNUvo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94672-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94672
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>:
https://gcc.gnu.org/g:892c7427ee234c04852e90d9ce32913a429adf9d
commit r11-271-g892c7427ee234c04852e90d9ce32913a429adf9d
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Mon May 11 16:39:20 2020 +0200
[Fortran] Fix/modify present() handling for assumed-shape optional (PR
94672)
gcc/fortran/
2020-05-07 Tobias Burnus <tobias@codesourcery.com>
PR fortran/94672
* trans.h (gfc_conv_expr_present): Add use_saved_decl=false
argument.
* trans-expr.c (gfc_conv_expr_present): Likewise; use DECL directly
and only if use_saved_decl is true, use the actual PARAM_DECL arg
(saved
descriptor).
* trans-array.c (gfc_trans_dummy_array_bias): Set local 'arg.0'
variable to NULL if 'arg' is not present.
* trans-openmp.c (gfc_omp_check_optional_argument): Simplify by
checking
'arg.0' instead of the true PARM_DECL.
(gfc_omp_finish_clause): Remove setting 'arg.0' to NULL.
gcc/testsuite/
2020-05-07 Jakub Jelinek <jakub@redhat.com>
Tobias Burnus <tobias@codesourcery.com>
PR fortran/94672
* gfortran.dg/gomp/pr94672.f90: New.
* gfortran.dg/missing_optional_dummy_6a.f90: Update scan-tree.
next prev parent reply other threads:[~2020-05-11 14:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 14:04 [Bug fortran/94672] New: " gcc at abeckmann dot de
2020-04-20 14:34 ` [Bug fortran/94672] [10 Regression] " jakub at gcc dot gnu.org
2020-04-20 14:54 ` jakub at gcc dot gnu.org
2020-04-20 15:12 ` jakub at gcc dot gnu.org
2020-04-21 11:55 ` jakub at gcc dot gnu.org
2020-04-21 12:36 ` jakub at gcc dot gnu.org
2020-05-07 10:04 ` [Bug fortran/94672] [10/11 " tschwinge at gcc dot gnu.org
2020-05-07 11:56 ` jakub at gcc dot gnu.org
2020-05-11 14:40 ` cvs-commit at gcc dot gnu.org [this message]
2020-05-12 10:08 ` cvs-commit at gcc dot gnu.org
2020-05-12 10:09 ` burnus at gcc dot gnu.org
2020-07-22 6:58 ` jakub at gcc dot gnu.org
2020-08-26 11:06 ` trnka at scm dot com
2020-08-28 11:54 ` cvs-commit at gcc dot gnu.org
2020-08-31 6:17 ` cvs-commit at gcc dot gnu.org
2020-08-31 6:50 ` burnus 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-94672-4-CvkDZjNUvo@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).