public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59065] questionable bounds for unassociated allocatable/pointer arrays?
Date: Sun, 10 Nov 2013 19:57:00 -0000	[thread overview]
Message-ID: <bug-59065-4-IAoJy5XVWL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59065-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Sun, Nov 10, 2013 at 07:46:55PM +0000, zeccav at gmail dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59065
> 
> --- Comment #2 from Vittorio Zecca <zeccav at gmail dot com> ---

(compiler results deleted to keep this short).

Thanks for checking other compilers.

> All of them put SIZE to zero that looks to me better
> than one as gfortran does.

So, how does one distinguish bewteen a valid and an invalid
program?

program foo
  integer, allocatable :: i(:)
  allocate(i(0))
  print *, size(i)
end

This has a valid zero sized array, whereas this doesn't

program foo
  integer, allocatable :: i(:)
  print *, size(i)
end

> But best behavior is g95's that detects the bug, and displays the
> correct line number

Agreed.  Detecting bugs is better.  But, the best behavior 
would be for the programmer not to write invalid code. :-)


  parent reply	other threads:[~2013-11-10 19:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-10 10:29 [Bug fortran/59065] New: " zeccav at gmail dot com
2013-11-10 16:44 ` [Bug fortran/59065] " kargl at gcc dot gnu.org
2013-11-10 19:46 ` zeccav at gmail dot com
2013-11-10 19:57 ` sgk at troutmask dot apl.washington.edu [this message]
2013-11-10 20:36 ` dominiq at lps dot ens.fr
2013-11-11  9:14 ` zeccav at gmail dot com
2013-11-11 19:10 ` anlauf at gmx dot de
2013-11-12  8:13 ` zeccav at gmail dot com
2013-11-12 14:20 ` sgk at troutmask dot apl.washington.edu
2013-11-12 15:52 ` zeccav at gmail dot com
2021-02-21  7:43 ` zeccav at gmail dot com
2021-02-21  9:41 ` 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-59065-4-IAoJy5XVWL@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).