public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fwi at inducks dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/50937] STAT option with ALLOCATE statement on large arrays
Date: Mon, 31 Oct 2011 20:18:00 -0000	[thread overview]
Message-ID: <bug-50937-4-rDr24SGGVe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50937-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from fwi at inducks dot org 2011-10-31 20:17:51 UTC ---
I do not(In reply to comment #7)
> On Mon, Oct 31, 2011 at 07:25:38PM +0000, fwi at inducks dot org wrote:
> Yes, the problem of integer overflow that Janne mentioned has
> been corrected.

Great.

I indeed do not know everything about the OS and what it does when I "allocate"
an array. But that's exactly the purpose of a programming language like
Fortran, an abstraction that should be "good enough" for programing without
having to know everything about the OS.
Secondly, users are sometimes better than programmers at telling them if
something is really useful or not. In that case, the question is: what is the
purpose of the STAT flag in an allocate STATEMENT if it won't give you any
reasonable indication if the array you have can be used or not.


  parent reply	other threads:[~2011-10-31 20:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 17:21 [Bug fortran/50937] New: " fwi at inducks dot org
2011-10-31 18:06 ` [Bug fortran/50937] " kargl at gcc dot gnu.org
2011-10-31 18:16 ` fwi at inducks dot org
2011-10-31 18:25 ` jb at gcc dot gnu.org
2011-10-31 18:29 ` fwi at inducks dot org
2011-10-31 19:02 ` jb at gcc dot gnu.org
2011-10-31 19:26 ` fwi at inducks dot org
2011-10-31 19:51 ` sgk at troutmask dot apl.washington.edu
2011-10-31 20:18 ` fwi at inducks dot org [this message]
2011-10-31 21:03 ` sgk at troutmask dot apl.washington.edu
2011-11-01  7:55 ` jb at gcc dot gnu.org
2011-11-01 12:01 ` fwi at inducks 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-50937-4-rDr24SGGVe@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).