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/103418] random_number() does not accept pointer, intent(in) array argument
Date: Fri, 10 Dec 2021 18:07:26 +0000 [thread overview]
Message-ID: <bug-103418-4-JUig0rIjnF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103418-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103418
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:bb6a1ebb8585b85879735d0d6df9535885fad165
commit r12-5900-gbb6a1ebb8585b85879735d0d6df9535885fad165
Author: Harald Anlauf <anlauf@gmx.de>
Date: Thu Dec 9 22:57:13 2021 +0100
Fortran: fix check for pointer dummy arguments with INTENT(IN)
gcc/fortran/ChangeLog:
PR fortran/103418
* check.c (variable_check): Replace previous check of procedure
dummy arguments with INTENT(IN) attribute when passed to intrinsic
procedures by gfc_check_vardef_context.
* expr.c (gfc_check_vardef_context): Correct check of INTENT(IN)
dummy arguments for the case of sub-components of a CLASS pointer.
gcc/testsuite/ChangeLog:
PR fortran/103418
* gfortran.dg/move_alloc_8.f90: Adjust error messages.
* gfortran.dg/pointer_intent_9.f90: New test.
next prev parent reply other threads:[~2021-12-10 18:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 20:59 [Bug fortran/103418] New: " baradi09 at gmail dot com
2021-11-24 21:41 ` [Bug fortran/103418] " anlauf at gcc dot gnu.org
2021-11-24 22:10 ` anlauf at gcc dot gnu.org
2021-11-24 23:27 ` kargl at gcc dot gnu.org
2021-11-25 21:02 ` anlauf at gcc dot gnu.org
2021-11-25 21:07 ` sgk at troutmask dot apl.washington.edu
2021-11-25 22:10 ` anlauf at gcc dot gnu.org
2021-11-25 22:18 ` sgk at troutmask dot apl.washington.edu
2021-11-25 23:19 ` sgk at troutmask dot apl.washington.edu
2021-11-26 19:27 ` sgk at troutmask dot apl.washington.edu
2021-11-26 20:13 ` anlauf at gcc dot gnu.org
2021-11-26 21:58 ` sgk at troutmask dot apl.washington.edu
2021-12-05 21:55 ` anlauf at gcc dot gnu.org
2021-12-10 18:07 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-19 21:20 ` cvs-commit at gcc dot gnu.org
2021-12-27 20:33 ` cvs-commit at gcc dot gnu.org
2021-12-27 20:35 ` anlauf 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-103418-4-JUig0rIjnF@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).