Bug 45417 - DEALLOCATE: No error when deallocating a target
Summary: DEALLOCATE: No error when deallocating a target
Status: NEW
Alias: None
Product: gcc
Classification: Unclassified
Component: fortran (show other bugs)
Version: 4.6.0
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords: wrong-code
Depends on: 37577
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-26 13:13 UTC by Tobias Burnus
Modified: 2013-06-29 15:27 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2013-06-29 00:00:00


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Burnus 2010-08-26 13:13:35 UTC
See thread starting at http://j3-fortran.org/pipermail/j3/2010-August/003747.html

The first example is valid (state == 0), the second valid (state /= 0), and the third one is invalid.

gfortran produces, http://j3-fortran.org/pipermail/j3/2010-August/003753.html, 0 <crash> <crash>.

Expected: The second example produces state /= 0.


Variant (works, should be state == 0):
  http://j3-fortran.org/pipermail/j3/2010-August/003754.html

The problem is that our array descriptor does not save whether a variable has been allocated or just associated with a named target. For the TR descriptor, mentioned in the last link, cf. http://j3-fortran.org/pipermail/interop-tr/2010-August/000163.html
Comment 1 Dominique d'Humieres 2013-06-29 15:27:30 UTC
Still present at revision 200557.