public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howisjw at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/94578] Incorrect assignment of RESHAPE() result to a Fortran pointer
Date: Fri, 17 Apr 2020 07:02:35 +0000	[thread overview]
Message-ID: <bug-94578-4-u5oBphZjxK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94578-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94578

--- Comment #7 from Jan-Willem Blokland <howisjw at hotmail dot com> ---
Thanks for verifying my case. Your test makes me wonder which intrinsics are
effected in this and other versions of gfortran. Furthermore, I assume it also
happens when you pass the pointer to subroutine or function (see example
below). This would be more difficult to debug. Fortunately, for my case the
pointer assignment and the usage of the intrinsic where in the same
function/subroutine.

program main
  implicit none
  type foo
     integer :: x, y
  end type foo
  integer :: i
  integer, dimension (2,2) :: array2d
  integer, dimension(:), pointer :: array1d
  type(foo), dimension(2*2), target :: solution
  data array2d /1,3,2,4/
  array1d => solution%x
  array1d = reshape (source=array2d, shape=shape(array1d))
  print *,maxval(array2d)
  call printMaxval(array1d)
end program main

subroutine printMaxval(array1d)
  implicit none
  integer, dimension(:), intent(in) :: array1d

  print*,maxval(array1d)
end subroutine

  parent reply	other threads:[~2020-04-17  7:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 13:46 [Bug fortran/94578] New: " howisjw at hotmail dot com
2020-04-13 13:53 ` [Bug fortran/94578] " howisjw at hotmail dot com
2020-04-13 13:56 ` howisjw at hotmail dot com
2020-04-14 15:05 ` tkoenig at gcc dot gnu.org
2020-04-14 15:08 ` tkoenig at gcc dot gnu.org
2020-04-16 14:21 ` tkoenig at gcc dot gnu.org
2020-04-16 14:24 ` tkoenig at gcc dot gnu.org
2020-04-17  7:02 ` howisjw at hotmail dot com [this message]
2020-04-17 14:16 ` tkoenig at gcc dot gnu.org
2020-04-17 15:17 ` tkoenig at gcc dot gnu.org
2020-04-25 10:29 ` cvs-commit at gcc dot gnu.org
2020-04-27  9:42 ` howisjw at hotmail dot com
2020-04-27 16:57 ` tkoenig 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-94578-4-u5oBphZjxK@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).