[Bug fortran/58861] Realloc on assignment: Bogus "Array bound mismatch" error with -fcheck=bounds

[tkoenig at gcc dot gnu.org]

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

Thomas Koenig  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||tkoenig at gcc dot gnu.org
 Resolution|--- |DUPLICATE

--- Comment #7 from Thomas Koenig  ---
This bug goes away with the patch in

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52162#c8

Resolving as duplicate.

*** This bug has been marked as a duplicate of bug 52162 ***

[Bug fortran/58861] Realloc on assignment: Bogus "Array bound mismatch" error with -fcheck=bounds

[vladimir.fuka at gmail dot com]

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

--- Comment #6 from Vladimir Fuka  ---
Still present in GCC 7.1.1.

Cab bug70231 be related?

[Bug fortran/58861] Realloc on assignment: Bogus "Array bound mismatch" error with -fcheck=bounds

[adam at aphirst dot karoo.co.uk]

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

--- Comment #5 from Adam Hirst  ---
It's been over a year, and I can confirm that this bug is present for all 3
examples in this thread, in the following version:

gcc (GCC) 6.2.1 20160830

[Bug fortran/58861] Realloc on assignment: Bogus Array bound mismatch error with -fcheck=bounds

[elrond1111 at yahoo dot com]

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

Kyle Horne elrond at yahoo dot com changed:

   What|Removed |Added

 CC||elrond at yahoo dot com

--- Comment #4 from Kyle Horne elrond at yahoo dot com ---
Created attachment 35874
  -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=35874action=edit
Minimal case

Another minimal use case that triggers erroneous bounds check errors

[Bug fortran/58861] Realloc on assignment: Bogus Array bound mismatch error with -fcheck=bounds

[adam at aphirst dot karoo.co.uk]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58861

Adam Hirst adam at aphirst dot karoo.co.uk changed:

   What|Removed |Added

 CC||adam at aphirst dot karoo.co.uk

--- Comment #3 from Adam Hirst adam at aphirst dot karoo.co.uk ---
Created attachment 32154
  -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=32154action=edit
Failed realloc with -fcheck

Here's another realloc-on-assign case which fails with -fcheck, but works
without. I was going to submit a new bug report, but thankfully I found this
existing one instead.

[Bug fortran/58861] Realloc on assignment: Bogus Array bound mismatch error with -fcheck=bounds

[dominiq at lps dot ens.fr]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58861

Dominique d'Humieres dominiq at lps dot ens.fr changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2013-12-21
 Ever confirmed|0   |1

--- Comment #2 from Dominique d'Humieres dominiq at lps dot ens.fr ---
Still present at r206155.

[Bug fortran/58861] Realloc on assignment: Bogus Array bound mismatch error with -fcheck=bounds

[burnus at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58861

Tobias Burnus burnus at gcc dot gnu.org changed:

   What|Removed |Added

   Keywords||wrong-code
 CC||burnus at gcc dot gnu.org
Summary|No reallocation assignment  |Realloc on assignment:
   |performed (due to different |Bogus Array bound
   |kinds?) |mismatch error with
   ||-fcheck=bounds

--- Comment #1 from Tobias Burnus burnus at gcc dot gnu.org ---
I can confirm the error message. However, the array seems to be properly
allocated. Only -fcheck=bounds seems to mishandle this case. (There might be
other PRs about this issue.)

Thus, as work around: Don't compile that file with -fcheck=bounds.