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/57305] [OOP] ICE when calling SIZEOF on an unlimited polymorphic variable
Date: Wed, 21 Aug 2013 18:03:00 -0000	[thread overview]
Message-ID: <bug-57305-4-cUrJPM2dQ7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57305-4@http.gcc.gnu.org/bugzilla/>

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

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at gcc dot gnu.org      |janus at gcc dot gnu.org

--- Comment #9 from janus at gcc dot gnu.org ---
And of course the changed behavior should be reflected in the documentation:


Index: gcc/fortran/intrinsic.texi
===================================================================
--- gcc/fortran/intrinsic.texi    (revision 201896)
+++ gcc/fortran/intrinsic.texi    (working copy)
@@ -11546,7 +11546,7 @@ number of bytes occupied by the argument.  If the
 to is returned.  If the argument is of a derived type with @code{POINTER}
 or @code{ALLOCATABLE} components, the return value does not account for
 the sizes of the data pointed to by these components. If the argument is
-polymorphic, the size according to the declared type is returned. The argument
+polymorphic, the size according to the dynamic type is returned. The argument
 may not be a procedure or procedure pointer.

 @item @emph{Example}:


  parent reply	other threads:[~2013-08-21 18:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16 18:39 [Bug fortran/57305] New: ICE with warnings and unlimited polymorphic (incorrect code) vladimir.fuka at gmail dot com
2013-05-16 19:02 ` [Bug fortran/57305] " vladimir.fuka at gmail dot com
2013-05-16 19:02 ` vladimir.fuka at gmail dot com
2013-06-11 15:51 ` [Bug fortran/57305] ICE with warnings and unlimited polymorphic dominiq at lps dot ens.fr
2013-08-21 13:18 ` [Bug fortran/57305] [OOP] ICE when calling SIZEOF on an unlimited polymorphic variable janus at gcc dot gnu.org
2013-08-21 13:53 ` janus at gcc dot gnu.org
2013-08-21 14:37 ` janus at gcc dot gnu.org
2013-08-21 15:47 ` janus at gcc dot gnu.org
2013-08-21 18:03 ` janus at gcc dot gnu.org [this message]
2014-03-15 14:17 ` dominiq at lps dot ens.fr
2014-03-15 17:18 ` janus at gcc dot gnu.org
2014-03-15 20:17 ` dominiq at lps dot ens.fr
2014-07-26 12:40 ` dominiq at lps dot ens.fr
2014-07-26 17:50 ` burnus at gcc dot gnu.org
2014-07-26 17:57 ` burnus at gcc dot gnu.org
2014-07-26 18:00 ` burnus at gcc dot gnu.org
2014-09-03  6:42 ` burnus 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-57305-4-cUrJPM2dQ7@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).