public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/53357] New: Add -fcheck=bounds for character type-spec in ALLOCATE
Date: Tue, 15 May 2012 09:41:00 -0000	[thread overview]
Message-ID: <bug-53357-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 53357
           Summary: Add -fcheck=bounds for character type-spec in ALLOCATE
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Keywords: diagnostic
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: burnus@gcc.gnu.org


Example: The following is invalid as the length does not match:

integer :: i
i = 5
block
  character(len=i), allocatable :: str
  allocate (character(len=3) :: str)
end block
end

 * * *

That's already correctly detected for compile-time constants:
  character(len=5), allocatable :: str
  allocate (character(len=3) :: str)
  end

Error: Allocating str at (1) with type-spec requires the same character-length
parameter as in the declaration


However, the compile-time version could also print the bounds.


             reply	other threads:[~2012-05-15  9:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15  9:41 burnus at gcc dot gnu.org [this message]
2014-07-20  8:57 ` [Bug fortran/53357] " dominiq at lps dot ens.fr
2015-10-10  9:08 ` dominiq at lps dot ens.fr

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-53357-4@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).