[Bug fortran/28590] New: A SEQUENCEd defined type which refers to another defined type generates a spurious complaint about the lack of SEQUENCE attribute in the latter

[ccnelson at itacllc dot com]

We have a code which uses a rather complicated set of defined types.  When
compiling one set of these type definitions (in a module), I get the following
error.  

 In file temp.f90:34

  end type GroupRigidMotion
  1
Error: Component prescribedmotiondata of SEQUENCE type declared at (1) does not
have the SEQUENCE attribute
 In file temp.f90:61

  end type GroupLL
 1
Error: Component groupdefll of SEQUENCE type declared at (1) does not have the
SEQUENCE attribute

I get this with both the latest version and the version that ships with
Ubuntu 6.06 (gfortran 4.0.3).  I will attempt to attach a stripped down version
of the code which duplicates the problem, if I can figure out how to do so.
(And would someone please provide some clarification


-- 
   Summary: A SEQUENCEd defined type which refers to another defined
type generates a spurious complaint about the lack of
SEQUENCE attribute in the latter
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: ccnelson at itacllc dot com
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i386-linux


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

[Bug fortran/28590] A SEQUENCEd defined type which refers to another defined type generates a spurious complaint about the lack of SEQUENCE attribute in the latter

[ccnelson at itacllc dot com]

--- Comment #1 from ccnelson at itacllc dot com  2006-08-03 22:52 ---
Created an attachment (id=12011)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12011&action=view)
Demo file to illustrate the problem

"gfortran -c temp.f90" should illustrate the problem.  As an aside: Lahey,
Intel, and G95 compilers can all handle this without problem.


-- 


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