public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51284] New: [OOP] CLASS and VALUE attribute: No copy to temporary done
Date: Wed, 23 Nov 2011 16:44:00 -0000	[thread overview]
Message-ID: <bug-51284-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 51284
           Summary: [OOP] CLASS and VALUE attribute: No copy to temporary
                    done
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: burnus@gcc.gnu.org
                CC: janus@gcc.gnu.org


The following program fails in several ways. As written, the program fails as
"test" modifies the value of a%i - but it shouldn't:

"A present dummy argument with the VALUE attribute becomes argument associated
with a definable anonymous data object whose initial value is the value of the
actual argument." (12.5.2.3 Argument association).

If one uncomments "test2", it fails with:
  Error: VALUE attribute conflicts with DIMENSION attribute at (1)
However, in Fortran 2008 this restriction is not present:

C557 An entity with the VALUE attribute shall be a dummy data object
     that is not an assumed-size array or a coarray, and does not have
     a coarray ultimate component.
C558 An entity with the VALUE attribute shall not have the ALLOCATABLE,
     INTENT (INOUT), INTENT (OUT), POINTER, or VOLATILE attributes.

Additionally, with the current polymorphic array draft patch the
  b(:)%i  (in "b(:)%i = 8" and "any(b(:)%i /= 8")
causes an ICE (segfault). Doing a "do i=1,8; b(i)%i = 8; done" had a similar
problem.

Finally, I think polymorphic arrays suffer from the same issue as scalar
polymorphic arrays.


Note: A deep copy has to be done, which takes the allocatable components into
account.


module m
  type t
    integer :: i
  end type t
contains
  subroutine test(x)
    class(t), VALUE :: x
    x%i = 5
  end subroutine test
!  subroutine test2(x)
!    class(t), VALUE :: x(:)
!    x(:)%i = 99
!  end subroutine test2
end module m

use m
class(t), allocatable :: a, b(:)
allocate ( t :: a, b(5))
a%i = 2
!b(:)%i = 8
call test(a)
!call test2(b)
if (a%i /= 2) call abort ()
!if (any(b(:)%i /= 8)) call abort ()
end


             reply	other threads:[~2011-11-23 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 16:44 burnus at gcc dot gnu.org [this message]
2011-11-23 16:47 ` [Bug fortran/51284] " burnus at gcc dot gnu.org
2011-12-09 21:27 ` burnus at gcc dot gnu.org
2011-12-11 13:31 ` burnus at gcc dot gnu.org
2015-10-09 21:43 ` 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-51284-4@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).