This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/46182] Run time check for invalid use of unallocated allocatable variables
- From: "mikael at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 26 Oct 2010 14:29:25 +0000
- Subject: [Bug libfortran/46182] Run time check for invalid use of unallocated allocatable variables
- Auto-submitted: auto-generated
- References: <bug-46182-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46182
Mikael Morin <mikael at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2010.10.26 14:29:15
CC| |mikael at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #2 from Mikael Morin <mikael at gcc dot gnu.org> 2010-10-26 14:29:15 UTC ---
(In reply to comment #1)
> Well! You can say the same thing for -fcheck=bounds if writing outside array
> bounds gives you a segmentation fault! Nevertheless nobody will argue that this
> check is useless: it can save you hours of debugging to locate the line(s) in
> which you do it.
Well, my point was that an out of bound access doesn't necessarily faults
whereas a NULL pointer access always does.
Anyway, it can't do any harm. Confirmed.