[Bug fortran/59065] questionable bounds for unassociated allocatable/pointer arrays?

2021-02-21 Thread dominiq at lps dot ens.fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59065 Dominique d'Humieres changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/59065] questionable bounds for unassociated allocatable/pointer arrays?

2021-02-20 Thread zeccav at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59065 --- Comment #10 from Vittorio Zecca --- This issue seems to have been resolved in the trunk gfortran 11.0.0 gfortran gfbug109.f -fcheck=pointer -g [vitti f95]$./a.out At line 9 of file gfbug109.f Fortran runtime error: Allocatable argument 'a

[Bug fortran/59065] questionable bounds for unassociated allocatable/pointer arrays?

2019-02-02 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59065 Dominique d'Humieres changed: What|Removed |Added Priority|P3 |P5

[Bug fortran/59065] questionable bounds for unassociated allocatable/pointer arrays?

2013-11-12 Thread zeccav at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59065 --- Comment #9 from Vittorio Zecca --- Unfortunately associated() does not allow unassociated array pointers as input so your code works for allocatable arrays but not for array pointers. Yes, a negative value for size() is good. It is a pity ther

[Bug fortran/59065] questionable bounds for unassociated allocatable/pointer arrays?

2013-11-12 Thread sgk at troutmask dot apl.washington.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59065 --- Comment #8 from Steve Kargl --- On Tue, Nov 12, 2013 at 08:13:14AM +, zeccav at gmail dot com wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59065 > > --- Comment #7 from Vittorio Zecca --- > I believe most times a code knows if an

[Bug fortran/59065] questionable bounds for unassociated allocatable/pointer arrays?

2013-11-12 Thread zeccav at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59065 --- Comment #7 from Vittorio Zecca --- I believe most times a code knows if and when the size of an array must be nonzero, so a zerosize array would raise suspicions in those cases. Anyway in my opinion gfortran run time should detect when an unal

[Bug fortran/59065] questionable bounds for unassociated allocatable/pointer arrays?

2013-11-11 Thread anlauf at gmx dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59065 Harald Anlauf changed: What|Removed |Added CC||anlauf at gmx dot de --- Comment #6 from

[Bug fortran/59065] questionable bounds for unassociated allocatable/pointer arrays?

2013-11-11 Thread zeccav at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59065 --- Comment #5 from Vittorio Zecca --- I do not think SIZE should be used to detect an undefined array pointer, but a size of zero warns the code that the array is mostly unusable and that perhaps something is wrong, while a nonzero size is tellin

[Bug fortran/59065] questionable bounds for unassociated allocatable/pointer arrays?

2013-11-10 Thread dominiq at lps dot ens.fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59065 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug fortran/59065] questionable bounds for unassociated allocatable/pointer arrays?

2013-11-10 Thread zeccav at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59065 --- Comment #2 from Vittorio Zecca --- g95: complains about deallocated array passed to LBOUND Intel ifort: 1 0 0 1 0 0 1 0 0 1 0

[Bug fortran/59065] questionable bounds for unassociated allocatable/pointer arrays?

2013-11-10 Thread kargl at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59065 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org