public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andrew at boldfriend dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67430] reallocate lhs with overloaded assignment operators causes memory error and wrong size
Date: Wed, 02 Sep 2015 20:27:00 -0000	[thread overview]
Message-ID: <bug-67430-4-L2kFUQ1RXn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67430-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67430

--- Comment #2 from Andrew Baldwin <andrew at boldfriend dot org> ---
In 7.2.1.4 of my copy of the standard it states:

"A subroutine defines the defined assignment x1 = x2 if"

...

"(5) either
    (a) the ranks of x1 and x2 match those of d1 and d2 or
    (b) the subroutine is elemental, x1 and x2 are conformable, and there is no
other subroutine that defines the assignment."

Since x1 and x2 are not conformable in this instance the defined assignment
(overloaded assignment) my reading is that it should not occur.

However, assigning two elements to an allocatable array allocated to four
elements is not invalid for intrinsic assignment.  Note 7.38 in my copy of the
standard states:

"If C is an allocatable array of rank 1, then

C = PACK(ARRAY,ARRAY>0)

will cause C to contain all the positive elements of ARRAY in array element
order; if C is not allocated or is allocated with the wrong size, it will be
re-allocated to be of the correct size to hold the result of PACK."

This behavior is observed when the overloaded assignment operator is not
provided.  The output in that case is:

 SIZE(A)           2 A:           7           7

It is also observed when the defined assignment does not meet the requirement
(5a).  I.e. replacing the defined assignment with

        SUBROUTINE ASGN_A (A, B)
          CLASS (A_TYPE), INTENT (OUT) :: A(:)
          CLASS (A_TYPE), INTENT (IN) :: B
!
          A(:)%INT = 45
        END SUBROUTINE

and changing the generic binding to a generic interface.  The output in that
case is also:

 SIZE(A)           2 A:           7           7


  parent reply	other threads:[~2015-09-02 20:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02  5:37 [Bug fortran/67430] New: " alipasha.celeris at gmail dot com
2015-09-02  6:07 ` [Bug fortran/67430] " kargl at gcc dot gnu.org
2015-09-02  8:51 ` dominiq at lps dot ens.fr
2015-09-02 20:27 ` andrew at boldfriend dot org [this message]
2015-09-02 21:51 ` anlauf at gmx dot de
2015-09-04  9:39 ` dominiq at lps dot ens.fr
2015-09-05 21:05 ` dominiq at lps dot ens.fr
2021-01-23 12:13 ` tkoenig 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-67430-4-L2kFUQ1RXn@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).