public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zeccav at gmail dot com" <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:46:00 -0000	[thread overview]
Message-ID: <bug-59065-4-lc25Ji9bxd@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 #2 from Vittorio Zecca <zeccav at gmail dot com> ---
g95: complains about deallocated array passed to LBOUND
Intel ifort:
           1           0           0
           1           0           0
           1           0           0
           1           0           0
NAG nagfor:
 -220021792 -220021793 0
 1 0 0
 1 0 0
 1 0 0
Lahey Fujitsu lfc:
 0 0 0
 0 0 0
 1 0 0
 1 0 0
All of them put SIZE to zero that looks to me better than one as gfortran does.
But best behavior is g95's that detects the bug, and displays the
correct line number
as in the following:

rm a.out ; g95 gfbug109.f -ftrace=full -g; ./a.out
At line 8 of file gfbug109.f (Unit 6)
Traceback: not available, compile with -ftrace=frame or -ftrace=full
Fortran runtime error: Deallocated array passed to LBOUND

So it would be an enhancement to sensibly handle
unallocated/unassociated arrays.


  parent reply	other threads:[~2013-11-10 19:46 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 [this message]
2013-11-10 19:57 ` sgk at troutmask dot apl.washington.edu
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-lc25Ji9bxd@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).