public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <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: Thu, 25 Nov 2021 23:19:53 +0000	[thread overview]
Message-ID: <bug-103418-4-AvnN3mjp3q@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 #8 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Thu, Nov 25, 2021 at 02:18:46PM -0800, Steve Kargl wrote:
> On Thu, Nov 25, 2021 at 10:10:32PM +0000, anlauf at gcc dot gnu.org wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103418
> > 
> > --- Comment #6 from anlauf at gcc dot gnu.org ---
> > Unfortunately the patch in comment#5 does not work for me. :-(
> > 
> > Interestingly, the Intel compiler fails on the testcase, too.
> > 
> 
> Hmmm.  I did have a number of other patches in my tree.  I
> wonder if one of those helped.  Unfortunately, I updated
> my git repository, where I cleared out all patch, and it
> takes a long time to rebuild gcc on my laptop.
> 

For the record, 

module test
   implicit none
   contains
   subroutine change_pointer_target(ptr)
      real, pointer, intent(in) :: ptr(:)
      call random_number(ptr)
      ptr(:) = ptr + 1.0
   end subroutine change_pointer_target
end module test

program foo
   use test
   implicit none
   real, pointer :: a(:), b
   allocate(a(4), b)
   call random_number(b)
   call random_number(a)
   print '(5F8.5)', b, a
end program foo

% gfcx -o z a.f90 && ./z
 0.65287 0.82614 0.77541 0.61923 0.52961

  parent reply	other threads:[~2021-11-25 23:19 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 [this message]
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
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-AvnN3mjp3q@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).