[Bug fortran/30374] unpacking intent(IN) arguments

2009-05-21 Thread jv244 at cam dot ac dot uk 


--- Comment #6 from jv244 at cam dot ac dot uk  2009-05-21 08:45 ---
fixed


-- 

jv244 at cam dot ac dot uk changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED


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

[Bug fortran/30374] unpacking intent(IN) arguments

2009-05-21 Thread jv244 at cam dot ac dot uk 


--- Comment #5 from jv244 at cam dot ac dot uk  2009-05-21 08:40 ---
(In reply to comment #4)
> Paul, 2 years ago you had a (one liner?) patch for this one, but gfortran 
> still
> seem to unpack for intent(IN) data:

ugh... no. I tested with 4.3 instead of 4.5. Instead we can close this, as this
seems solved.


-- 

jv244 at cam dot ac dot uk changed:

   What|Removed |Added

  Known to fail|4.5.0   |
  Known to work||4.5.0


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

[Bug fortran/30374] unpacking intent(IN) arguments

2009-05-21 Thread jv244 at cam dot ac dot uk 


--- Comment #4 from jv244 at cam dot ac dot uk  2009-05-21 08:34 ---
Paul, 2 years ago you had a (one liner?) patch for this one, but gfortran still
seem to unpack for intent(IN) data:

MODULE M1
CONTAINS
  SUBROUTINE S1(I)
   INTEGER, DIMENSION(3), INTENT(IN) :: I
  END SUBROUTINE
END MODULE

USE M1
INTEGER, TARGET, DIMENSION(9) :: I
INTEGER, DIMENSION(:), POINTER :: IP
IP=>I(1:9:3)
CALL S1(IP)
END


-- 

jv244 at cam dot ac dot uk changed:

   What|Removed |Added

  Known to fail||4.5.0
   Last reconfirmed|2007-10-26 07:25:36 |2009-05-21 08:34:53
   date||
Summary|aliasing amoung dummy   |unpacking intent(IN)
   |arguments: possibly missing |arguments
   |optimization|


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