[Bug fortran/19561] [gfortran] wrong code generation for pointers to derived types

--- Additional Comments From tobi at gcc dot gnu dot org 2005-06-21 08:41 --- Works on both the 4.0 branch and the mainline. Testcase forthcoming. -- What|Removed |Added

[Bug fortran/19561] [gfortran] wrong code generation for pointers to derived types

--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-01-22 06:19 --- The problem is in the main program type(objA),target :: oa type(objB),target :: ob call new(oa,1) call new(ob,oa,2) call print(ob) call print(getOa(ob)) !

[Bug fortran/19561] [gfortran] wrong code generation for pointers to derived types

-- What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed||1 Last reconfirmed|-00-00 00:00:00 |2005-01-

[Bug fortran/19561] [gfortran] wrong code generation for pointers to derived types

--- Additional Comments From pbrook at gcc dot gnu dot org 2005-01-21 14:57 --- My bad, this is in fact legal and well defined. -- What|Removed |Added Status|RES

[Bug fortran/19561] [gfortran] wrong code generation for pointers to derived types

--- Additional Comments From pbrook at gcc dot gnu dot org 2005-01-21 14:48 --- Testcase invokes undefined behaviour. http://gcc.gnu.org/ml/fortran/2005-01/msg00234.html -- What|Removed |Added --

[Bug fortran/19561] [gfortran] wrong code generation for pointers to derived types

--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-01-21 13:03 --- Confirmed on Cygwin and RH9 In an attempt to reduce this a bit, I have produced a slightly more startling error: $ cat point.f90 module mpoint type :: mytype integer :: i

[Bug fortran/19561] [gfortran] wrong code generation for pointers to derived types

-- What|Removed |Added Keywords||wrong-code Known to fail||4.0.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=