[Bug fortran/89925] [10/11/12/13 Regression] Wrong array bounds from ALLOCATE with SOURCE or MOLD
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89925 Richard Biener changed: What|Removed |Added Target Milestone|9.5 |10.4 --- Comment #7 from Richard Biener --- GCC 9 branch is being closed
[Bug fortran/89925] [10/11/12/13 Regression] Wrong array bounds from ALLOCATE with SOURCE or MOLD
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89925 Jakub Jelinek changed: What|Removed |Added Target Milestone|10.4|10.5 --- Comment #8 from Jakub Jelinek --- GCC 10.4 is being released, retargeting bugs to GCC 10.5.
[Bug fortran/89925] [10/11/12/13 Regression] Wrong array bounds from ALLOCATE with SOURCE or MOLD
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89925 Vladimir Fuka changed: What|Removed |Added CC||vladimir.fuka at gmail dot com --- Comment #9 from Vladimir Fuka --- Was this bug fixed? It seems to work correctly in 12.2.1 but incorrectly in 11.3.0 (OpenSUSE builds). It is a major problem and the fix would very much be worth backporting to maintained versions.
[Bug fortran/89925] [10/11/12/13 Regression] Wrong array bounds from ALLOCATE with SOURCE or MOLD
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89925 --- Comment #10 from Tobias Burnus --- I think that could be the commit r12-5767-g6262e3a22b3d86afc116480bc59a7bb30b0cfd40 "fortran: Fix setting of array lower bound for named arrays" but I have not checked more deeply.
[Bug fortran/89925] [10/11/12/13 Regression] Wrong array bounds from ALLOCATE with SOURCE or MOLD
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89925 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org --- Comment #11 from kargl at gcc dot gnu.org --- (In reply to Tobias Burnus from comment #10) > I think that could be the commit > r12-5767-g6262e3a22b3d86afc116480bc59a7bb30b0cfd40 > "fortran: Fix setting of array lower bound for named arrays" > > but I have not checked more deeply. I can confirm that your patch in r12-5767-yada-yada fixed this bug. Your patch included two testcases. Do you think that Neil's code should be converted to a new testcase or do your testcases cover this issue. Neil, sorry it took so long to get a fix.
