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/51948] New: [OOP] Rejects valid: Polymorphic arguments in MOVE_ALLOC
Date: Sun, 22 Jan 2012 17:55:00 -0000	[thread overview]
Message-ID: <bug-51948-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 51948
           Summary: [OOP] Rejects valid: Polymorphic arguments in
                    MOVE_ALLOC
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Keywords: rejects-valid
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: burnus@gcc.gnu.org


The following fails at move_alloc with bogus errors. The second example is
based on the example from
chapter09/burgers_factory_f2003/periodic_6th_order.F90 in the book
http://www.cambridge.org/rouson

type t
end type t

contains
  function func(x)
    class(t), allocatable :: x(:), func(:)
    call move_alloc (x, func)
! FAILS: Error: the 'from' and 'to' arguments of 'move_alloc' intrinsic at (1)
must have the same rank 0/1
  end function

  function func2(x)
    type(t), allocatable :: x
    class(t), allocatable :: func2
    call move_alloc (x, func)
! FAILS: Error: 'to' argument of 'move_alloc' intrinsic at (1) must be a
variable
  end function
end


             reply	other threads:[~2012-01-22 17:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22 17:55 burnus at gcc dot gnu.org [this message]
2012-01-23 12:00 ` [Bug fortran/51948] [4.6/4.7 Regression][OOP] Rejects valid: Function result value in MOVE_ALLOC, nested in SELECT TYPE burnus at gcc dot gnu.org
2012-01-23 20:57 ` burnus at gcc dot gnu.org
2012-01-23 22:06 ` burnus at gcc dot gnu.org
2012-01-24  9:06 ` burnus at gcc dot gnu.org
2012-01-24  9:07 ` 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-51948-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).