From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 612F4385800A; Thu, 25 Nov 2021 21:02:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 612F4385800A From: "anlauf at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/103418] random_number() does not accept pointer, intent(in) array argument Date: Thu, 25 Nov 2021 21:02:34 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 10.1.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: anlauf at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2021 21:02:34 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D103418 --- Comment #4 from anlauf at gcc dot gnu.org --- (In reply to kargl from comment #3) > (In reply to anlauf from comment #2) > > The nearly obvious fix: > >=20 > > diff --git a/gcc/fortran/check.c b/gcc/fortran/check.c > > index 837eb0912c0..3859e18c6c3 100644 > > --- a/gcc/fortran/check.c > > +++ b/gcc/fortran/check.c > > @@ -1031,7 +1031,7 @@ variable_check (gfc_expr *e, int n, bool allow_pr= oc) > > break; > > } > >=20=20 > > - if (!ref) > > + if (!ref && !pointer) > > { > > gfc_error ("%qs argument of %qs intrinsic at %L cannot be " > > "INTENT(IN)", gfc_current_intrinsic_arg[n]->name, > >=20 > > regresses for gfortran.dg/move_alloc_8.f90, thus needs additional > > investigation. >=20 > Did you try the patch posted in Fortran Discourse? No. I'm afraid I also missed it on the usual channels where patches for gcc are posted.=