public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47024] [OOP] STORAGE_SIZE (for polymorphic types): Segfault at run time
Date: Mon, 20 Dec 2010 15:17:00 -0000	[thread overview]
Message-ID: <bug-47024-4-bQMXwVY4Aa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47024-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from janus at gcc dot gnu.org 2010-12-20 15:16:44 UTC ---
(In reply to comment #0)
> STORAGE_SIZE does not work for unallocated polymorphic types. However, the
> Fortran 2008 standard allows them:
> 
> "A    shall be a scalar or array of any type. If it is polymorphic it shall not
>       be an undefined pointer. If it has any deferred type parameters it shall
>       not be an unallocated allocatable variable or a disassociated or
> undefined
>       pointer." (F2008, 13.7.160)


I don't really understand this. Why should one allow it for unallocated
allocatables, but not for undefined pointers?

Also, it's not exactly clear to me which value to expect for such a case. From
the standard's description of STORAGE_SIZE:

"The result value is the size expressed in bits for an element of an array that
has the dynamic type and type parameters of A."

However, if A is unallocated, it does not have a dynamic type!


  parent reply	other threads:[~2010-12-20 15:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20  9:35 [Bug fortran/47024] New: " burnus at gcc dot gnu.org
2010-12-20  9:47 ` [Bug fortran/47024] " burnus at gcc dot gnu.org
2010-12-20 15:17 ` janus at gcc dot gnu.org [this message]
2010-12-20 16:48 ` burnus at gcc dot gnu.org
2011-01-04 13:39 ` janus at gcc dot gnu.org
2011-01-04 13:49 ` janus at gcc dot gnu.org
2011-01-04 18:58 ` janus at gcc dot gnu.org
2011-01-05  9:05 ` janus at gcc dot gnu.org
2011-01-05  9:17 ` janus at gcc dot gnu.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-47024-4-bQMXwVY4Aa@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).