public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/51977] New: [OOP] MOVE_ALLOC: Bogus "must have the same rank 0/1" for same-rank arrays
@ 2012-01-24  8:57 burnus at gcc dot gnu.org
  2012-01-24 16:41 ` [Bug fortran/51977] " burnus at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: burnus at gcc dot gnu.org @ 2012-01-24  8:57 UTC (permalink / raw)
  To: gcc-bugs

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

             Bug #: 51977
           Summary: [OOP] MOVE_ALLOC: Bogus "must have the same rank 0/1"
                    for same-rank arrays
    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


Split off from PR 51948.

The following fails at move_alloc with a bogus error:

  Error: the 'from' and 'to' arguments of 'move_alloc'  intrinsic at (1)
         must have the same rank 0/1


type t
end type t

contains
  function func(x)
    class(t), allocatable :: x(:), func(:)
    call move_alloc (x, func)
  end function
end


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug fortran/51977] [OOP] MOVE_ALLOC: Bogus "must have the same rank 0/1" for same-rank arrays
  2012-01-24  8:57 [Bug fortran/51977] New: [OOP] MOVE_ALLOC: Bogus "must have the same rank 0/1" for same-rank arrays burnus at gcc dot gnu.org
@ 2012-01-24 16:41 ` burnus at gcc dot gnu.org
  2012-01-27 13:23 ` burnus at gcc dot gnu.org
  2012-01-27 13:36 ` burnus at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: burnus at gcc dot gnu.org @ 2012-01-24 16:41 UTC (permalink / raw)
  To: gcc-bugs

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-01-24 15:29:02 UTC ---
See also PR 51970, which has a similar issue - and contains a fix for the
follow-up issue (trans-intrinsic.c's conv_intrinsic_move_alloc).


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug fortran/51977] [OOP] MOVE_ALLOC: Bogus "must have the same rank 0/1" for same-rank arrays
  2012-01-24  8:57 [Bug fortran/51977] New: [OOP] MOVE_ALLOC: Bogus "must have the same rank 0/1" for same-rank arrays burnus at gcc dot gnu.org
  2012-01-24 16:41 ` [Bug fortran/51977] " burnus at gcc dot gnu.org
@ 2012-01-27 13:23 ` burnus at gcc dot gnu.org
  2012-01-27 13:36 ` burnus at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: burnus at gcc dot gnu.org @ 2012-01-27 13:23 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-01-27 13:08:58 UTC ---
Author: burnus
Date: Fri Jan 27 13:08:52 2012
New Revision: 183622

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=183622
Log:
2012-01-27  Tobias Burnus  <burnus@net-b.de>

        PR fortran/51970
        PR fortran/51977
        * primary.c (gfc_match_varspec. gfc_match_rvalue): Set
        handle array spec for BT_CLASS.
        * expr.c (gfc_get_variable_expr, gfc_lval_expr_from_sym)
        * frontend-passes.c (create_var): Ditto.
        * resolve.c (resolve_actual_arglist, resolve_assoc_var): Ditto.
        * trans-decl.c (gfc_trans_deferred_vars): Use class_pointer
        instead of attr.pointer.
        (gfc_generate_function_code): Use CLASS_DATA (sym) for BT_CLASS.
        * trans-intrinsic.c (conv_intrinsic_move_alloc): Move assert.
        * trans-stmt.c (trans_associate_var): Ask for the descriptor.

2012-01-27  Tobias Burnus  <burnus@net-b.de>

        PR fortran/51970
        PR fortran/51977
        * gfortran.dg/move_alloc_13.f90: New.


Added:
    trunk/gcc/testsuite/gfortran.dg/move_alloc_13.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/expr.c
    trunk/gcc/fortran/frontend-passes.c
    trunk/gcc/fortran/primary.c
    trunk/gcc/fortran/resolve.c
    trunk/gcc/fortran/trans-decl.c
    trunk/gcc/fortran/trans-intrinsic.c
    trunk/gcc/fortran/trans-stmt.c
    trunk/gcc/testsuite/ChangeLog


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug fortran/51977] [OOP] MOVE_ALLOC: Bogus "must have the same rank 0/1" for same-rank arrays
  2012-01-24  8:57 [Bug fortran/51977] New: [OOP] MOVE_ALLOC: Bogus "must have the same rank 0/1" for same-rank arrays burnus at gcc dot gnu.org
  2012-01-24 16:41 ` [Bug fortran/51977] " burnus at gcc dot gnu.org
  2012-01-27 13:23 ` burnus at gcc dot gnu.org
@ 2012-01-27 13:36 ` burnus at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: burnus at gcc dot gnu.org @ 2012-01-27 13:36 UTC (permalink / raw)
  To: gcc-bugs

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED

--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-01-27 13:10:00 UTC ---
FIXED on the trunk (4.7).


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2012-01-27 13:10 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-01-24  8:57 [Bug fortran/51977] New: [OOP] MOVE_ALLOC: Bogus "must have the same rank 0/1" for same-rank arrays burnus at gcc dot gnu.org
2012-01-24 16:41 ` [Bug fortran/51977] " burnus at gcc dot gnu.org
2012-01-27 13:23 ` burnus at gcc dot gnu.org
2012-01-27 13:36 ` burnus at gcc dot gnu.org

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).