This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/24978] ICE in gfc_assign_data_value_range
- From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 29 Oct 2006 05:16:45 -0000
- Subject: [Bug fortran/24978] ICE in gfc_assign_data_value_range
- References: <bug-24978-8649@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from jvdelisle at gcc dot gnu dot org 2006-10-29 05:16 -------
Should we simply avoid the ice, perhaps accepting the invalid code or do we
want to search for duplicates in the DATA statements and generate an error?
Also,
Is this valid?:
real :: a(5,5)
DATA a(1,1), a(3,1), a(1,2), a(3,3) /2*1.0, 2*2.0/
DATA a(2,1) /2.5/
In other words, no overlap in the DATA statements. It is a big difference if
we have to search element by element. I suspect this is why this is not a
constraint on the compiler, but is a restriction on the programmer, so to
speak.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24978