public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/52052] New: [Coarray] Properly handle coarray components of derived types
@ 2012-01-30 14:26 burnus at gcc dot gnu.org
  2013-07-22 17:29 ` [Bug fortran/52052] " 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-30 14:26 UTC (permalink / raw)
  To: gcc-bugs

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

             Bug #: 52052
           Summary: [Coarray] Properly handle coarray components of
                    derived types
    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


Special care needs to be taken with coarrays - and in particular coarray
components; they may only be collectively allocated and deallocated.

In particular:

Intrinsic assignment: Contrary to normal allocatable components,
no reallocation is allowed. The programmer guarantees that the shape and
type parameters are suitable.

Caveat: Be aware of allocatable components nested within coarray components -
and issues with polymorphism.

Please also check that:
- Calling caf_register is done with ALLOCATE, also with SOURCE=
- Calling of caf_deregister when leaving the scope/calling DEALLOCATE
- Special handling of polymorphic coarray components
- Whether there are issues regarding _def_init and _copy; cf. PR 51947.
Consider whether a simple INTENT_INOUT for _copy would be more appropriate.
- Check that there is indeed no realloc on assignment for coarray variables.


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

* [Bug fortran/52052] [Coarray] Properly handle coarray components of derived types
  2012-01-30 14:26 [Bug fortran/52052] New: [Coarray] Properly handle coarray components of derived types burnus at gcc dot gnu.org
@ 2013-07-22 17:29 ` burnus at gcc dot gnu.org
  2013-07-22 17:31 ` burnus at gcc dot gnu.org
  2015-10-20 16:20 ` dominiq at lps dot ens.fr
  2 siblings, 0 replies; 4+ messages in thread
From: burnus at gcc dot gnu.org @ 2013-07-22 17:29 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #0)
> Intrinsic assignment: Contrary to normal allocatable components,
> no reallocation is allowed. The programmer guarantees that the shape and
> type parameters are suitable.

Patches:
- http://gcc.gnu.org/ml/fortran/2013-06/msg00137.html (committed)
- http://gcc.gnu.org/ml/fortran/2013-07/msg00041.html (committed)


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

* [Bug fortran/52052] [Coarray] Properly handle coarray components of derived types
  2012-01-30 14:26 [Bug fortran/52052] New: [Coarray] Properly handle coarray components of derived types burnus at gcc dot gnu.org
  2013-07-22 17:29 ` [Bug fortran/52052] " burnus at gcc dot gnu.org
@ 2013-07-22 17:31 ` burnus at gcc dot gnu.org
  2015-10-20 16:20 ` dominiq at lps dot ens.fr
  2 siblings, 0 replies; 4+ messages in thread
From: burnus at gcc dot gnu.org @ 2013-07-22 17:31 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Mon Jul 22 17:28:56 2013
New Revision: 201140

URL: http://gcc.gnu.org/viewcvs?rev=201140&root=gcc&view=rev
Log:
2013-07-22  Tobias Burnus  <burnus@net-b.de>

        PR fortran/57906
        PR fortran/52052
        * class.c (gfc_build_class_symbol): Set coarray_comp.
        * trans-array.c (structure_alloc_comps): For coarrays,
        directly use the data pointer address.

2013-07-22  Tobias Burnus  <burnus@net-b.de>

        PR fortran/57906
        PR fortran/52052
        * coarray/lib_realloc_1.f90: Permit optimization.
        * gfortran.dg/coarray_31.f90: New.


Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/class.c
    trunk/gcc/fortran/trans-array.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/gfortran.dg/coarray/lib_realloc_1.f90


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

* [Bug fortran/52052] [Coarray] Properly handle coarray components of derived types
  2012-01-30 14:26 [Bug fortran/52052] New: [Coarray] Properly handle coarray components of derived types burnus at gcc dot gnu.org
  2013-07-22 17:29 ` [Bug fortran/52052] " burnus at gcc dot gnu.org
  2013-07-22 17:31 ` burnus at gcc dot gnu.org
@ 2015-10-20 16:20 ` dominiq at lps dot ens.fr
  2 siblings, 0 replies; 4+ messages in thread
From: dominiq at lps dot ens.fr @ 2015-10-20 16:20 UTC (permalink / raw)
  To: gcc-bugs

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2015-10-20
     Ever confirmed|0                           |1

--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Patch committed more than two years ago. Any reason to keep this PR opened?


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

end of thread, other threads:[~2015-10-20 16:20 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-01-30 14:26 [Bug fortran/52052] New: [Coarray] Properly handle coarray components of derived types burnus at gcc dot gnu.org
2013-07-22 17:29 ` [Bug fortran/52052] " burnus at gcc dot gnu.org
2013-07-22 17:31 ` burnus at gcc dot gnu.org
2015-10-20 16:20 ` dominiq at lps dot ens.fr

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