[Bug fortran/29785] Fortran 2003: POINTER Rank Remapping

2010-08-19 Thread domob at gcc dot gnu dot org
--- Comment #11 from domob at gcc dot gnu dot org 2010-08-19 16:06 --- Fixed (with an extended version of the patch attached above). -- domob at gcc dot gnu dot org changed: What|Removed |Added --

[Bug fortran/29785] Fortran 2003: POINTER Rank Remapping

2010-08-19 Thread domob at gcc dot gnu dot org
--- Comment #10 from domob at gcc dot gnu dot org 2010-08-19 16:02 --- Subject: Bug 29785 Author: domob Date: Thu Aug 19 16:02:30 2010 New Revision: 163377 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=163377 Log: 2010-08-19 Daniel Kraft PR fortran/29785 PR

[Bug fortran/29785] Fortran 2003: POINTER Rank Remapping

2010-08-18 Thread domob at gcc dot gnu dot org
--- Comment #9 from domob at gcc dot gnu dot org 2010-08-18 19:34 --- Created an attachment (id=21514) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21514&action=view) Partial patch. This implements rank remapping and also bounds remapping as for PR 45016. Tests seem to be succes

[Bug fortran/29785] Fortran 2003: POINTER Rank Remapping

2010-08-17 Thread mikael at gcc dot gnu dot org
--- Comment #8 from mikael at gcc dot gnu dot org 2010-08-17 18:21 --- (In reply to comment #7) > Tobias (and all): Do you think we should check for "the size of data-target > shall not be less than the size of data-pointer-object" at runtime when > -fcheck=bounds is given? > Yes. The

[Bug fortran/29785] Fortran 2003: POINTER Rank Remapping

2010-08-17 Thread domob at gcc dot gnu dot org
--- Comment #7 from domob at gcc dot gnu dot org 2010-08-17 17:38 --- Tobias (and all): Do you think we should check for "the size of data-target shall not be less than the size of data-pointer-object" at runtime when -fcheck=bounds is given? -- http://gcc.gnu.org/bugzilla/show_bug

[Bug fortran/29785] Fortran 2003: POINTER Rank Remapping

2010-07-21 Thread burnus at gcc dot gnu dot org
--- Comment #6 from burnus at gcc dot gnu dot org 2010-07-21 10:14 --- See also PR 45016, which is not about bounds remapping but about setting the correct bounds in an array assignment. (Wrong-code F95 bug + missing F2003 feature). Maybe all three (remapping, fix bounds, F2003 lower bo

[Bug fortran/29785] Fortran 2003: POINTER Rank Remapping

2010-07-21 Thread domob at gcc dot gnu dot org
--- Comment #5 from domob at gcc dot gnu dot org 2010-07-21 09:06 --- I'll work on this. -- domob at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|u

[Bug fortran/29785] Fortran 2003: POINTER Rank Remapping

2010-07-21 Thread burnus at gcc dot gnu dot org
--- Comment #4 from burnus at gcc dot gnu dot org 2010-07-21 09:03 --- Fortran 2008 has the following, which I missed to quote: "If bounds-remapping-list is specified, the pointer target shall be simply contiguous (6.5.4) or of rank one. It shall not be a disassociated or undefined poin

[Bug fortran/29785] Fortran 2003: POINTER Rank Remapping

2009-08-07 Thread jv244 at cam dot ac dot uk
--- Comment #3 from jv244 at cam dot ac dot uk 2009-08-07 07:35 --- still missing 4.5.0, this seems a particularly useful F03 feature ;-) For an expert, should be 'easy' to add (ignoring the F2008 variant) ? -- jv244 at cam dot ac dot uk changed: What|Removed

[Bug fortran/29785] Fortran 2003: POINTER Rank Remapping

2008-07-03 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2008-07-03 16:09 --- In Fortran 2008 the rank-one constraint is gone: "C720 If bounds-remapping-list is not specified, the ranks of data-pointer-object and data-target shall be the same." -- http://gcc.gnu.org/bugzilla/show_bug.cgi?

[Bug fortran/29785] Fortran 2003: POINTER Rank Remapping

2007-04-12 Thread burnus at gcc dot gnu dot org
--- Comment #1 from burnus at gcc dot gnu dot org 2007-04-12 09:19 --- Cf. http://gcc.gnu.org/ml/fortran/2007-04/msg00120.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29785

[Bug fortran/29785] Fortran 2003: POINTER Rank Remapping

2006-11-09 Thread burnus at gcc dot gnu dot org
-- burnus at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfir