public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/57696] Defined assignment for components not used when those are ALLOCATABLE
       [not found] <bug-57696-4@http.gcc.gnu.org/bugzilla/>
@ 2013-06-24 10:23 ` burnus at gcc dot gnu.org
  2013-06-24 10:56 ` dominiq at lps dot ens.fr
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 4+ messages in thread
From: burnus at gcc dot gnu.org @ 2013-06-24 10:23 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
>From Fortran 2008, "7.2.1.3 Interpretation of intrinsic assignments", paragraph
13 (excerpt):

"For a noncoarray allocatable component the following sequence of operations is
applied.
(1) If the component of the variable is allocated, it is deallocated.
(2) If the component of the value of expr is allocated, the corresponding
    component of the variable is allocated with the same dynamic type and type
    parameters as the component of the value of expr. If it is an array, it is
    allocated with the same bounds. The value of the component of the value of
    expr is then assigned to the corresponding component of the variable using
    defined assignment if the declared type of the component has a type-bound
    defined assignment consistent with the component, and intrinsic assignment
    for the dynamic type of that component otherwise."


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

* [Bug fortran/57696] Defined assignment for components not used when those are ALLOCATABLE
       [not found] <bug-57696-4@http.gcc.gnu.org/bugzilla/>
  2013-06-24 10:23 ` [Bug fortran/57696] Defined assignment for components not used when those are ALLOCATABLE burnus at gcc dot gnu.org
@ 2013-06-24 10:56 ` dominiq at lps dot ens.fr
  2013-08-21 12:25 ` [Bug fortran/57696] [F03] " janus at gcc dot gnu.org
  2013-09-15 14:22 ` [Bug fortran/57696] [OOP] " burnus at gcc dot gnu.org
  3 siblings, 0 replies; 4+ messages in thread
From: dominiq at lps dot ens.fr @ 2013-06-24 10:56 UTC (permalink / raw)
  To: gcc-bugs

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-06-24
     Ever confirmed|0                           |1

--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed.


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

* [Bug fortran/57696] [F03] Defined assignment for components not used when those are ALLOCATABLE
       [not found] <bug-57696-4@http.gcc.gnu.org/bugzilla/>
  2013-06-24 10:23 ` [Bug fortran/57696] Defined assignment for components not used when those are ALLOCATABLE burnus at gcc dot gnu.org
  2013-06-24 10:56 ` dominiq at lps dot ens.fr
@ 2013-08-21 12:25 ` janus at gcc dot gnu.org
  2013-09-15 14:22 ` [Bug fortran/57696] [OOP] " burnus at gcc dot gnu.org
  3 siblings, 0 replies; 4+ messages in thread
From: janus at gcc dot gnu.org @ 2013-08-21 12:25 UTC (permalink / raw)
  To: gcc-bugs

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

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |janus at gcc dot gnu.org
            Summary|Defined assignment for      |[F03] Defined assignment
                   |components not used when    |for components not used
                   |those are ALLOCATABLE       |when those are ALLOCATABLE

--- Comment #3 from janus at gcc dot gnu.org ---
Related to PR 46897, I guess. The difference is that we are dealing with
ALLOCATABLE components here.


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

* [Bug fortran/57696] [OOP] Defined assignment for components not used when those are ALLOCATABLE
       [not found] <bug-57696-4@http.gcc.gnu.org/bugzilla/>
                   ` (2 preceding siblings ...)
  2013-08-21 12:25 ` [Bug fortran/57696] [F03] " janus at gcc dot gnu.org
@ 2013-09-15 14:22 ` burnus at gcc dot gnu.org
  3 siblings, 0 replies; 4+ messages in thread
From: burnus at gcc dot gnu.org @ 2013-09-15 14:22 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> ---
See also PR 57697; the a similar needs to be also addressed when fixing this
bug, namely the case that for:
  var.foo.bar
"foo" is NULL/unallocated while "bar" appears in the defined assignment.

See also PR46897 for another missing feature.


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

end of thread, other threads:[~2013-09-15 14:22 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-57696-4@http.gcc.gnu.org/bugzilla/>
2013-06-24 10:23 ` [Bug fortran/57696] Defined assignment for components not used when those are ALLOCATABLE burnus at gcc dot gnu.org
2013-06-24 10:56 ` dominiq at lps dot ens.fr
2013-08-21 12:25 ` [Bug fortran/57696] [F03] " janus at gcc dot gnu.org
2013-09-15 14:22 ` [Bug fortran/57696] [OOP] " 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).