Bug 46783 - [OOP] TRANSFER with polymorphic MOLD=
Summary: [OOP] TRANSFER with polymorphic MOLD=
Status: RESOLVED WONTFIX
Alias: None
Product: gcc
Classification: Unclassified
Component: fortran (show other bugs)
Version: 4.6.0
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks: 31237
  Show dependency treegraph
 
Reported: 2010-12-03 14:16 UTC by Tobias Burnus
Modified: 2018-06-09 00:46 UTC (History)
5 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2013-06-20 00:00:00


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Burnus 2010-12-03 14:16:15 UTC
Cf. http://j3-fortran.org/pipermail/j3/2010-December/004026.html

Currently, the declared type is used for MOLD= in TRANSFER. It seems as if the effective type should be used instead.


This is a tracker bug as the standard is a bit ambiguous about it; I assume that there will be an IR (interpretation request) about it.


Currently, F2008 just has:

MOLD shall be a scalar or array of any type. If it is a variable, it need not be defined.

Result Characteristics. The result is of the same type and type parameters as MOLD.
Comment 1 Dominique d'Humieres 2013-06-20 18:44:23 UTC
This link

Cf. http://j3-fortran.org/pipermail/j3/2010-December/004026.html

is broken.
Comment 2 Dominique d'Humieres 2015-10-09 08:53:37 UTC
> This link
>
> Cf. http://j3-fortran.org/pipermail/j3/2010-December/004026.html
>
> is broken.

Updated link

http://mailman.j3-fortran.org/pipermail/j3/2010-December/004026.html
Comment 3 Dominique d'Humieres 2018-02-27 09:42:48 UTC
> Updated link
>
> http://mailman.j3-fortran.org/pipermail/j3/2010-December/004026.html

Broken again!-(

And I cannot find anything relevant in

https://mailman.j3-fortran.org/doc/year/10

AFAICT the situation has not changed in F2018.

What should we do with this PR?
Comment 4 kargl 2018-06-09 00:46:53 UTC
(In reply to Dominique d'Humieres from comment #3)
> > Updated link
> >
> > http://mailman.j3-fortran.org/pipermail/j3/2010-December/004026.html
> 
> Broken again!-(
> 
> And I cannot find anything relevant in
> 
> https://mailman.j3-fortran.org/doc/year/10
> 
> AFAICT the situation has not changed in F2018.
> 
> What should we do with this PR?

All of the URLs are broken in this PR.

Without a testcase that demonstrates the bug, 
this PR is useless.  Closing.