public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "P dot Schaffnit at access dot rwth-aachen dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34159]  New: Checkbound could warn about unallocated arrays
Date: Tue, 20 Nov 2007 08:49:00 -0000	[thread overview]
Message-ID: <bug-34159-10601@http.gcc.gnu.org/bugzilla/> (raw)

Hi!

I don't seem to get gfortran to warn when assigning to an unallocated array
(I've tried '-g -fbounds-check -Wall -pedantic', which I take it should cover
it all), it only segfaults at run-time...

While this is obviously menial stuff, the Lahey compiler for one nicely warns
both at compile- and run-time.

Just for the record...

Thanks!

Philippe

PS: a reduced example:
!
PROGRAM Test
!
INTEGER, ALLOCATABLE :: Array(:)
!
Array = 256
!
END PROGRAM Test
!

PPS: I've tried with
GNU Fortran (GCC) 4.3.0 20071119 (experimental) [trunk revision 130286]


-- 
           Summary: Checkbound could warn about unallocated arrays
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: P dot Schaffnit at access dot rwth-aachen dot de


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


             reply	other threads:[~2007-11-20  8:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20  8:49 P dot Schaffnit at access dot rwth-aachen dot de [this message]
2007-11-20 13:11 ` [Bug fortran/34159] " fxcoudert at gcc dot gnu dot org
2010-05-09 18:34 ` dfranke at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-34159-10601@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).