public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/103434] New: Pointer subobject does not show to correct memory location
@ 2021-11-26 7:29 baradi09 at gmail dot com
2021-11-26 11:03 ` [Bug fortran/103434] " dominiq at lps dot ens.fr
0 siblings, 1 reply; 2+ messages in thread
From: baradi09 at gmail dot com @ 2021-11-26 7:29 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103434
Bug ID: 103434
Summary: Pointer subobject does not show to correct memory
location
Product: gcc
Version: 10.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: baradi09 at gmail dot com
Target Milestone: ---
Based on the discussion on FD
(https://fortran-lang.discourse.group/t/is-the-section-of-a-pointer-to-an-array-a-valid-pointer/2331),
I'd assume, that the following code is standard conforming. However, the result
with gfortran seems to be incorrect.
*** Code:
module test
implicit none
type :: pointer_wrapper
real, pointer :: ptr(:) => null()
end type pointer_wrapper
contains
subroutine store_pointer(wrapper, ptr)
type(pointer_wrapper), intent(out) :: wrapper
real, pointer, intent(in) :: ptr(:)
wrapper%ptr => ptr
end subroutine store_pointer
subroutine use_pointer(wrapper)
type(pointer_wrapper), intent(inout) :: wrapper
wrapper%ptr(:) = wrapper%ptr + 1.0
end subroutine use_pointer
end module test
program testprog
use test
implicit none
real, allocatable, target :: data(:,:)
real, pointer :: ptr(:,:)
type(pointer_wrapper) :: wrapper
integer :: ii
allocate(data(4, 2))
ptr => data(:,:)
data(:,:) = 0.0
do ii = 1, size(data, dim=2)
print *, "#", ii
print *, "BEFORE ", ii, maxval(ptr(:,ii))
call store_pointer(wrapper, ptr(:,ii))
print *, "BETWEEN", ii, maxval(ptr(:,ii))
call use_pointer(wrapper)
print *, "AFTER ", ii, maxval(ptr(:,ii))
end do
end program testprog
*** Output:
# 1
BEFORE 1 0.00000000
BETWEEN 1 0.00000000
AFTER 1 1.00000000
# 2
BEFORE 2 1.00000000
BETWEEN 2 1.00000000
AFTER 2 1.00000000
*** Expected output:
# 1
BEFORE 1 0.00000000
BETWEEN 1 0.00000000
AFTER 1 1.00000000
# 2
BEFORE 2 0.00000000
BETWEEN 2 0.00000000
AFTER 2 1.00000000
It seems, as if store_pointer would point to a memory location larger as it
should be, so that also data outside of the actual stride is modified. Intel
and NAG deliver the expected output.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug fortran/103434] Pointer subobject does not show to correct memory location
2021-11-26 7:29 [Bug fortran/103434] New: Pointer subobject does not show to correct memory location baradi09 at gmail dot com
@ 2021-11-26 11:03 ` dominiq at lps dot ens.fr
0 siblings, 0 replies; 2+ messages in thread
From: dominiq at lps dot ens.fr @ 2021-11-26 11:03 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103434
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2021-11-26
Status|UNCONFIRMED |WAITING
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
This seems to have been fixed on GCC12 and at least since r11-9157, bur not for
r10-10223.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-11-26 11:03 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-11-26 7:29 [Bug fortran/103434] New: Pointer subobject does not show to correct memory location baradi09 at gmail dot com
2021-11-26 11:03 ` [Bug fortran/103434] " dominiq at lps dot ens.fr
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).